| 00:30:19 | at0mat_: | at0mat_ is now known as at0mat |
| 01:45:07 | samesong: | samesong is now known as samesong|awy |
| 03:33:34 | dsnrk: | "Using a method very similar to that used in bitmessage. If bitmessage is secure this should be too." |
| 03:37:30 | dsnrk: | Cinnicoin: anonymous encrypted messaging that hinges on address reuse and is maybe secure. |
| 03:44:57 | luke-jr_: | luke-jr_ is now known as Luke-Jr |
| 03:45:51 | gmaxwell: | bitmessage is very obviously insecure, for some definition of insecure. |
| 03:46:33 | dsnrk: | cinnicoin is far far worse. I'm not qualified to say anything about the method of encryption, but DOS vectors abound. |
| 03:47:03 | gmaxwell: | e.g. a network attacker that can watch all the traffic going in and out of your port trivially deanonymizes you w/ bitmessage if you send. (unless you use bitmessage on tor, which couldn't bootstrap last I tried a few months ago) |
| 03:47:43 | gmaxwell: | or a less localized network attacker can winnow down your location in the network (even with tor) by inducing you to send via public key requests, even if you are technically only a reciever. |
| 03:49:05 | dsnrk: | for cinnicoin I'm not even sure you'd have to go that far. there's no rate limiting on messages, so you could bomb a node with encrypted emssages and check the response times. long if the node has to decrypt messages, short if it doesn't and fails the hash header. |
| 07:53:50 | diablito: | diablito is now known as jamesdean |
| 11:20:44 | mr_burde_: | mr_burde_ is now known as mr_burdell |
| 11:38:51 | Pasha: | Pasha is now known as Cory |
| 15:17:46 | jtimon: | ehmm, what is sugarpuff talking about here? https://bitcointalk.org/index.php?topic=88208.msg7490047#msg7490047 |
| 17:28:10 | maaku: | sugarpuff seems to be allergic to actually learning how bitcoin works |
| 17:58:45 | maaku: | maaku is now known as Guest56037 |
| 18:44:37 | midnightmagic_: | midnightmagic_ is now known as midnightmagic |
| 19:12:34 | jtimon: | no, he has answered to that already: he has no alregies ;) |
| 19:13:04 | sipa: | who is sugarpuff? |
| 19:13:54 | jtimon: | the guy explaining what "utxo" would mean to bitcoin in that bitcointalk thread |
| 19:14:47 | jtimon: | well, I think he is trolling the anti-outsource mining thread too |
| 19:40:20 | cracksmurf: | cracksmurf is now known as paavo |
| 19:40:49 | paavo: | paavo is now known as cracksmurf |
| 19:49:23 | Pasha: | Pasha is now known as Cory |
| 20:38:49 | [Tristan]: | [Tristan] is now known as Guest22301 |
| 20:41:35 | NikolaiToryzin: | NikolaiToryzin is now known as stqism |
| 20:41:53 | stqism: | stqism is now known as NikolaiToryzin |
| 20:59:19 | sipa: | ep |
| 22:02:59 | Fistful_of_Coins: | Fistful_of_Coins is now known as sh4rk |
| 22:03:49 | sh4rk: | sh4rk is now known as shark |
| 22:04:02 | shark: | shark is now known as Fistful_of_coins |
| 22:33:32 | eizh_: | eizh_ is now known as eizh |
| 22:44:01 | Guest56037: | Guest56037 has left #bitcoin-wizards |
| 22:44:51 | maaku: | incredibly good news, Sel4 is being open-sourced : http://sel4.systems/ |
| 22:45:46 | tacotime: | nice |
| 22:47:51 | maaku: | I have a long list of projects I would like to have done on Sel4, but never got around to doing because obscure licensed operating systems suck |
| 22:50:15 | gmaxwell: | I know that for the proven l4 stuff the proofs are about 200k lines to prove correct about 8kloc of C... I wonder how big the sel4 proofs are. |
| 22:51:24 | sipa: | thankfully, C source code can always be written on 1 line |
| 22:53:00 | maaku: | sipa: :) |