--- Log opened Sat Oct 25 00:00:28 2014
00:02 -!- koshii_ [~0@node-np.pool-182-52.dynamic.totbb.net] has joined #bitcoin-wizards
00:04 -!- koshii [~0@node-wg8.pool-125-25.dynamic.totbb.net] has quit [Ping timeout: 265 seconds]
00:11 -!- Greed` is now known as Greed
00:28 -!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has quit [Quit: Leaving]
00:30 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds]
00:41 -!- woah [~woah@199-241-202-232.PUBLIC.monkeybrains.net] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
01:05 -!- andy-logbot [~bitcoin--@wpsoftware.net] has joined #bitcoin-wizards
01:05  * andy-logbot is logging
01:09 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-wizards
01:09 -!- NewLiberty [~NewLibert@2602:304:cff8:1580:9ce6:6279:5508:f683] has quit [Ping timeout: 265 seconds]
01:12 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has joined #bitcoin-wizards
01:16 -!- Dr-G is now known as Aquent420
01:21 -!- OX3 [~OX3@gateway-nat.fmrib.ox.ac.uk] has joined #bitcoin-wizards
01:24 -!- Aquent420 is now known as Dr-G
01:37 -!- AlphaBar123 [~AlphaBar@c-71-202-114-230.hsd1.ca.comcast.net] has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
01:46 -!- AlphaBar123 [~AlphaBar@c-71-202-114-230.hsd1.ca.comcast.net] has joined #bitcoin-wizards
01:50 -!- maaku [~quassel@50-0-37-37.dsl.static.fusionbroadband.com] has quit [Remote host closed the connection]
01:51 -!- OX3 [~OX3@gateway-nat.fmrib.ox.ac.uk] has quit [Ping timeout: 265 seconds]
01:52 -!- wallet42 [~wallet42@unaffiliated/wallet42] has joined #bitcoin-wizards
02:01 -!- OX3 [~OX3@gateway-nat.fmrib.ox.ac.uk] has joined #bitcoin-wizards
02:05 -!- machinery [~textual@148.240.141.29] has joined #bitcoin-wizards
02:06 -!- AlphaBar123 [~AlphaBar@c-71-202-114-230.hsd1.ca.comcast.net] has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
02:12 -!- drawingthesun [~drawingth@106-68-157-235.dyn.iinet.net.au] has joined #bitcoin-wizards
02:19 -!- maaku [~quassel@50-0-37-37.dsl.static.fusionbroadband.com] has joined #bitcoin-wizards
02:19 -!- maaku [~quassel@50-0-37-37.dsl.static.fusionbroadband.com] has quit [Read error: Connection reset by peer]
02:21 -!- maaku [~quassel@50-0-37-37.dsl.static.fusionbroadband.com] has joined #bitcoin-wizards
02:21 -!- maaku is now known as Guest44335
02:21 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Remote host closed the connection]
02:25 -!- mapppum [~mappum@c-24-17-76-220.hsd1.wa.comcast.net] has joined #bitcoin-wizards
02:25 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has joined #bitcoin-wizards
02:26 -!- Guest44335 [~quassel@50-0-37-37.dsl.static.fusionbroadband.com] has quit [Remote host closed the connection]
02:29 -!- maaku_ [~quassel@50-0-37-37.dsl.static.fusionbroadband.com] has joined #bitcoin-wizards
02:30 -!- maaku_ [~quassel@50-0-37-37.dsl.static.fusionbroadband.com] has quit [Remote host closed the connection]
02:33 -!- maaku_ [~quassel@50-0-37-37.dsl.static.fusionbroadband.com] has joined #bitcoin-wizards
02:33 -!- pi07r [~pi07r@f212009.upc-f.chello.nl] has quit [Quit: >>>]
02:37 -!- pi07r [~pi07r@f212009.upc-f.chello.nl] has joined #bitcoin-wizards
02:37 -!- mapppum [~mappum@c-24-17-76-220.hsd1.wa.comcast.net] has quit [Remote host closed the connection]
02:38 -!- pi07r [~pi07r@f212009.upc-f.chello.nl] has quit [Client Quit]
02:39 -!- Cory [~Cory@unaffiliated/cory] has quit [Ping timeout: 258 seconds]
02:40 -!- Pasha [~Cory@unaffiliated/cory] has joined #bitcoin-wizards
02:45 -!- pi07r [~pi07r@f212009.upc-f.chello.nl] has joined #bitcoin-wizards
02:47 -!- Pasha is now known as Cory
02:49 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has joined #bitcoin-wizards
02:53 -!- spiftheninja [~miner@173-20-237-20.client.mchsi.com] has quit []
02:55 -!- maaku_ is now known as maaku
03:02 -!- tacotime [~mashkeys@198.52.200.63] has quit [Ping timeout: 260 seconds]
03:03 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds]
03:04 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has joined #bitcoin-wizards
03:10 -!- llllllllll [~lllllllll@53-109.bbned.dsl.internl.net] has joined #bitcoin-wizards
03:16 -!- cbeams [~cbeams@unaffiliated/cbeams] has quit [Read error: Connection reset by peer]
03:16 -!- cbeams [~cbeams@chello084114181075.1.15.vie.surfer.at] has joined #bitcoin-wizards
03:16 -!- cbeams [~cbeams@chello084114181075.1.15.vie.surfer.at] has quit [Changing host]
03:16 -!- cbeams [~cbeams@unaffiliated/cbeams] has joined #bitcoin-wizards
03:30 -!- wallet42 [~wallet42@unaffiliated/wallet42] has quit [Quit: Leaving.]
03:40 -!- cbeams [~cbeams@unaffiliated/cbeams] has quit []
03:41 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has quit [Ping timeout: 250 seconds]
03:43 -!- mkarrer [~mkarrer@122.Red-88-1-121.dynamicIP.rima-tde.net] has joined #bitcoin-wizards
03:58 -!- hashtag [~hashtag@CPE-69-23-221-39.wi.res.rr.com] has joined #bitcoin-wizards
04:02 -!- wallet42 [~wallet42@unaffiliated/wallet42] has joined #bitcoin-wizards
04:04 -!- nessence [~alexl@p5DDC50B1.dip0.t-ipconnect.de] has joined #bitcoin-wizards
04:10 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has quit [Remote host closed the connection]
04:11 -!- NewLiberty [~NewLibert@76-255-129-88.lightspeed.irvnca.sbcglobal.net] has joined #bitcoin-wizards
04:14 -!- crowex_ [~crowex@host-78-147-106-214.as13285.net] has joined #bitcoin-wizards
04:15 -!- pen [~linker@42.118.241.21] has quit [Ping timeout: 265 seconds]
04:16 -!- pen [~linker@42.119.112.255] has joined #bitcoin-wizards
04:16 -!- crowex_ [~crowex@host-78-147-106-214.as13285.net] has quit [Remote host closed the connection]
04:22 -!- pen [~linker@42.119.112.255] has quit [Ping timeout: 265 seconds]
04:22 -!- pen [~linker@42.119.112.255] has joined #bitcoin-wizards
04:33 -!- hashtag [~hashtag@CPE-69-23-221-39.wi.res.rr.com] has quit [Ping timeout: 258 seconds]
04:36 -!- vfor [~Adium@g229087193.adsl.alicedsl.de] has joined #bitcoin-wizards
04:36 -!- gloriusAgain [~gloriusag@g229087193.adsl.alicedsl.de] has joined #bitcoin-wizards
04:36 -!- mortale [~mortale@gateway/tor-sasl/mortale] has quit [Remote host closed the connection]
04:39 -!- mortale [~mortale@gateway/tor-sasl/mortale] has joined #bitcoin-wizards
04:39 -!- tobyai [~toby@113x43x131x34.ap113.ftth.ucom.ne.jp] has joined #bitcoin-wizards
04:41 -!- machinery [~textual@148.240.141.29] has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
04:56 -!- Quanttek [~quassel@2a02:8108:d00:870:cd38:a04a:8125:844b] has joined #bitcoin-wizards
04:57 -!- AaronvanW [~ewout@158pc208.sshunet.nl] has joined #bitcoin-wizards
05:09 -!- gavinandresen [~gavin@unaffiliated/gavinandresen] has quit [Ping timeout: 240 seconds]
05:15 -!- paveljanik [~Pavel@unaffiliated/paveljanik] has joined #bitcoin-wizards
05:16 -!- gavinandresen [~gavin@unaffiliated/gavinandresen] has joined #bitcoin-wizards
05:18 -!- fanquake [~anonymous@unaffiliated/fanquake] has quit [Quit: fanquake]
05:19 -!- paveljanik [~Pavel@unaffiliated/paveljanik] has quit [Client Quit]
05:23 -!- AaronvanW [~ewout@158pc208.sshunet.nl] has quit [Ping timeout: 265 seconds]
05:27 -!- paveljanik [~Pavel@unaffiliated/paveljanik] has joined #bitcoin-wizards
05:27 -!- tobyai [~toby@113x43x131x34.ap113.ftth.ucom.ne.jp] has quit [Quit: Leaving.]
05:33 -!- zooko [~user@c-75-70-204-109.hsd1.co.comcast.net] has joined #bitcoin-wizards
05:36 -!- paveljanik [~Pavel@unaffiliated/paveljanik] has quit [Quit: This computer has gone to sleep]
05:57 -!- nessence [~alexl@p5DDC50B1.dip0.t-ipconnect.de] has quit [Remote host closed the connection]
05:57 -!- nessence [~alexl@p5DDC50B1.dip0.t-ipconnect.de] has joined #bitcoin-wizards
06:02 -!- nessence_ [~alexl@p5DDC50B1.dip0.t-ipconnect.de] has joined #bitcoin-wizards
06:02 -!- nessence [~alexl@p5DDC50B1.dip0.t-ipconnect.de] has quit [Ping timeout: 265 seconds]
06:06 -!- Aquent1 [~Aquent@gateway/tor-sasl/aquent] has quit [Remote host closed the connection]
06:08 -!- Aquent1 [~Aquent@gateway/tor-sasl/aquent] has joined #bitcoin-wizards
06:14 -!- rdponticelli [~quassel@gateway/tor-sasl/rdponticelli] has joined #bitcoin-wizards
06:19 -!- shibe25 [~shibe25@x1-6-00-1e-2a-29-4d-94.cpe.webspeed.dk] has joined #bitcoin-wizards
06:19 < shibe25> I like potatos, and you to should love potatoes
06:19 < shibe25> Potatoes
06:20 -!- shibe25 [~shibe25@x1-6-00-1e-2a-29-4d-94.cpe.webspeed.dk] has left #bitcoin-wizards []
06:20 < fluffypony> wut
06:21 < sipa> s/to/too/
06:25 -!- paveljanik [~Pavel@unaffiliated/paveljanik] has joined #bitcoin-wizards
06:31 -!- nessence_ [~alexl@p5DDC50B1.dip0.t-ipconnect.de] has quit []
06:32 -!- paveljanik [~Pavel@unaffiliated/paveljanik] has quit [Quit: This computer has gone to sleep]
06:48 -!- Dr-G [~Dr-G@gateway/tor-sasl/dr-g] has quit [Remote host closed the connection]
06:48 -!- mkarrer [~mkarrer@122.Red-88-1-121.dynamicIP.rima-tde.net] has quit [Remote host closed the connection]
06:49 -!- Aquent [~Aquent@gateway/tor-sasl/aquent] has quit [Remote host closed the connection]
06:50 -!- Dr-G [~Dr-G@gateway/tor-sasl/dr-g] has joined #bitcoin-wizards
06:50 -!- Aquent [~Aquent@gateway/tor-sasl/aquent] has joined #bitcoin-wizards
06:52 -!- wallet42 [~wallet42@unaffiliated/wallet42] has quit [Quit: Leaving.]
06:55 -!- andy-logbot [~bitcoin--@wpsoftware.net] has quit [Ping timeout: 265 seconds]
06:56 -!- andytoshi [~andytoshi@unaffiliated/andytoshi] has quit [Ping timeout: 255 seconds]
06:56 -!- OneFixt [~OneFixt@unaffiliated/onefixt] has quit [Remote host closed the connection]
06:57 -!- OneFixt [~OneFixt@unaffiliated/onefixt] has joined #bitcoin-wizards
07:00 -!- Aquent1 [~Aquent@gateway/tor-sasl/aquent] has quit [Quit: Leaving]
07:01 -!- Aquent1 [~Aquent@gateway/tor-sasl/aquent] has joined #bitcoin-wizards
07:04 -!- hashtag [~hashtag@CPE-69-23-221-39.wi.res.rr.com] has joined #bitcoin-wizards
07:10 -!- c0rw1n [~c0rw1n@167.84-67-87.adsl-dyn.isp.belgacom.be] has quit [Remote host closed the connection]
07:10 -!- c0rw1n [~c0rw1n@167.84-67-87.adsl-dyn.isp.belgacom.be] has joined #bitcoin-wizards
07:11 -!- Aquent [~Aquent@gateway/tor-sasl/aquent] has quit [Disconnected by services]
07:21 -!- Aquent1 is now known as Aquent
07:30 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has quit [Ping timeout: 256 seconds]
08:05 -!- woah [~woah@199-241-202-232.PUBLIC.monkeybrains.net] has joined #bitcoin-wizards
08:14 -!- artilectinc [~andrzej.l@50-78-244-190-static.hfc.comcastbusiness.net] has quit [Ping timeout: 244 seconds]
08:14 -!- artilectinc [~andrzej.l@50-78-244-190-static.hfc.comcastbusiness.net] has joined #bitcoin-wizards
08:16 -!- profreid [~profreid@a88-115-210-162.elisa-laajakaista.fi] has joined #bitcoin-wizards
08:17 -!- nuke1989 [~nuke@ppp-2-87-135-147.home.otenet.gr] has quit [Read error: No route to host]
08:18 -!- gloriusAgain [~gloriusag@g229087193.adsl.alicedsl.de] has quit [Remote host closed the connection]
08:18 -!- vfor [~Adium@g229087193.adsl.alicedsl.de] has quit [Quit: Leaving.]
08:19 -!- gloriusAgain [~gloriusag@g229087193.adsl.alicedsl.de] has joined #bitcoin-wizards
08:20 -!- nuke1989 [~nuke@ppp-2-87-135-147.home.otenet.gr] has joined #bitcoin-wizards
08:23 -!- gloriusAgain [~gloriusag@g229087193.adsl.alicedsl.de] has quit [Ping timeout: 256 seconds]
08:25 -!- KingCoin [~KingCoin@unaffiliated/kingcoin] has joined #bitcoin-wizards
08:26 -!- Dr-G [~Dr-G@gateway/tor-sasl/dr-g] has quit [Remote host closed the connection]
08:30 -!- Dr-G [~Dr-G@gateway/tor-sasl/dr-g] has joined #bitcoin-wizards
08:48 -!- profreid [~profreid@a88-115-210-162.elisa-laajakaista.fi] has quit [Quit: profreid]
08:50 -!- Burrito [~Burrito@unaffiliated/burrito] has joined #bitcoin-wizards
08:52 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has joined #bitcoin-wizards
09:05 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has quit [Remote host closed the connection]
09:18 -!- jps [~Jud@cpe-74-72-116-143.nyc.res.rr.com] has joined #bitcoin-wizards
09:25 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-wizards
09:26 -!- woah [~woah@199-241-202-232.PUBLIC.monkeybrains.net] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
09:26 -!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has joined #bitcoin-wizards
09:29 -!- gloriusAgain [~gloriusag@g225037024.adsl.alicedsl.de] has joined #bitcoin-wizards
09:30 -!- Sangheili [Elite8385@gateway/shell/elitebnc/x-gljxymdaefibxgya] has quit [Ping timeout: 265 seconds]
09:32 -!- machinery [~textual@148.240.141.29] has joined #bitcoin-wizards
09:34 -!- gloriusAgain [~gloriusag@g225037024.adsl.alicedsl.de] has quit [Ping timeout: 265 seconds]
09:40 -!- waxwing [~waxwing@62.205.214.125] has quit [Quit: Leaving]
09:41 -!- jps [~Jud@cpe-74-72-116-143.nyc.res.rr.com] has quit [Quit: jps]
09:45 -!- mkarrer [~mkarrer@122.Red-88-1-121.dynamicIP.rima-tde.net] has joined #bitcoin-wizards
09:45 -!- Sangheili [Elite8385@gateway/shell/elitebnc/x-dagcgsepocmkiuud] has joined #bitcoin-wizards
09:46 -!- waxwing [~waxwing@62.205.214.125] has joined #bitcoin-wizards
09:48 -!- tacotime [~mashkeys@198.52.200.63] has joined #bitcoin-wizards
09:52 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has joined #bitcoin-wizards
09:54 -!- KingCoin [~KingCoin@unaffiliated/kingcoin] has quit [Quit: KingCoin]
09:57 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has quit [Remote host closed the connection]
09:58 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has joined #bitcoin-wizards
10:00 -!- paveljanik [~Pavel@unaffiliated/paveljanik] has joined #bitcoin-wizards
10:02 -!- vfor [~Adium@g225037024.adsl.alicedsl.de] has joined #bitcoin-wizards
10:02 -!- gloriusAgain [~gloriusag@g225037024.adsl.alicedsl.de] has joined #bitcoin-wizards
10:05 -!- c0rw1n [~c0rw1n@167.84-67-87.adsl-dyn.isp.belgacom.be] has quit [Ping timeout: 245 seconds]
10:05 -!- Apocalyptic [~Apocalypt@unaffiliated/apocalyptic] has quit [Quit: Leaving]
10:05 -!- paveljanik [~Pavel@unaffiliated/paveljanik] has quit [Quit: This computer has gone to sleep]
10:06 -!- hearn [~mike@84-75-198-85.dclient.hispeed.ch] has joined #bitcoin-wizards
10:07 -!- c0rw1n [~c0rw1n@167.84-67-87.adsl-dyn.isp.belgacom.be] has joined #bitcoin-wizards
10:16 -!- machinery [~textual@148.240.141.29] has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
10:17 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has quit [Remote host closed the connection]
10:19 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has joined #bitcoin-wizards
10:21 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has quit [Remote host closed the connection]
10:26 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has joined #bitcoin-wizards
10:27 -!- hashtag [~hashtag@CPE-69-23-221-39.wi.res.rr.com] has quit [Ping timeout: 244 seconds]
10:29 < maaku> amiller: we have opportunistically talked to mining pool and cloud hashing operators, and asic manufacturers at conferences and such trying to get them to support getblocktemplate and other tech like smart property which lets their users control what their equipment is hashing
10:30 < maaku> I can only assume that is what petertodd was referring to
10:31 < amiller> sounds right
10:34 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has joined #bitcoin-wizards
10:34 -!- NewLiberty [~NewLibert@76-255-129-88.lightspeed.irvnca.sbcglobal.net] has quit [Read error: Connection reset by peer]
10:40 -!- apoelstra [18e3de9d@gateway/web/freenode/ip.24.227.222.157] has joined #bitcoin-wizards
10:44 -!- rdponticelli [~quassel@gateway/tor-sasl/rdponticelli] has quit [Remote host closed the connection]
10:44 -!- rdponticelli [~quassel@gateway/tor-sasl/rdponticelli] has joined #bitcoin-wizards
10:45 -!- jps [~Jud@cpe-74-72-116-143.nyc.res.rr.com] has joined #bitcoin-wizards
10:50 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has quit [Remote host closed the connection]
10:55 -!- kyletorpey [~kyle@c-24-131-0-5.hsd1.va.comcast.net] has left #bitcoin-wizards []
10:55 -!- jps [~Jud@cpe-74-72-116-143.nyc.res.rr.com] has quit [Quit: jps]
11:01 -!- Meeh [~meeeeeeh@meeh.sigterm.no] has quit [Quit: No Ping reply in 180 seconds.]
11:02 -!- Meeh [~meeeeeeh@meeh.sigterm.no] has joined #bitcoin-wizards
11:10 -!- Apocalyptic [~Apocalypt@unaffiliated/apocalyptic] has joined #bitcoin-wizards
11:22 -!- jps [~Jud@cpe-74-72-116-143.nyc.res.rr.com] has joined #bitcoin-wizards
11:22 -!- AlphaBar123 [~AlphaBar@c-71-202-114-230.hsd1.ca.comcast.net] has joined #bitcoin-wizards
11:25 -!- Dr-G [~Dr-G@gateway/tor-sasl/dr-g] has quit [Remote host closed the connection]
11:25 -!- Dr-G [~Dr-G@gateway/tor-sasl/dr-g] has joined #bitcoin-wizards
11:33 -!- c0rw1n is now known as c0rw|food
11:34 -!- aburan28 [~ubuntu@static-108-45-93-73.washdc.fios.verizon.net] has quit [Ping timeout: 265 seconds]
11:34 -!- devrandom [~devrandom@gateway/tor-sasl/niftyzero1] has quit [Quit: Lost terminal]
11:43 -!- mortale [~mortale@gateway/tor-sasl/mortale] has quit [Remote host closed the connection]
11:43 -!- Dr-G [~Dr-G@gateway/tor-sasl/dr-g] has quit [Write error: Broken pipe]
11:43 -!- rdponticelli [~quassel@gateway/tor-sasl/rdponticelli] has quit [Remote host closed the connection]
11:43 -!- Aquent [~Aquent@gateway/tor-sasl/aquent] has quit [Remote host closed the connection]
11:43 -!- wiretapped [~wiretappe@gateway/tor-sasl/wiretapped] has quit [Remote host closed the connection]
11:43 -!- rfreeman_w [~rfreeman@gateway/tor-sasl/rfreemanw] has quit [Remote host closed the connection]
11:43 -!- Adlai [~Adlai@gateway/tor-sasl/adlai] has quit [Write error: Broken pipe]
11:46 -!- rdponticelli [~quassel@gateway/tor-sasl/rdponticelli] has joined #bitcoin-wizards
11:47 -!- Graftec [~Graftec@gateway/tor-sasl/graftec] has quit [Ping timeout: 246 seconds]
11:49 -!- wiretapped [~wiretappe@gateway/tor-sasl/wiretapped] has joined #bitcoin-wizards
11:52 -!- eslbaer [~eslbaer@p579E9D63.dip0.t-ipconnect.de] has joined #bitcoin-wizards
11:54 -!- wiretapped [~wiretappe@gateway/tor-sasl/wiretapped] has quit [Ping timeout: 246 seconds]
11:56 -!- woah [~woah@199-241-202-232.PUBLIC.monkeybrains.net] has joined #bitcoin-wizards
11:57 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has joined #bitcoin-wizards
12:02 -!- wiretapped [~wiretappe@gateway/tor-sasl/wiretapped] has joined #bitcoin-wizards
12:03 -!- Graftec [~Graftec@gateway/tor-sasl/graftec] has joined #bitcoin-wizards
12:04 -!- c0rw|food is now known as c0rw1n
12:04 -!- adam3us [~Adium@c31-67.i07-8.onvol.net] has joined #bitcoin-wizards
12:06 -!- wallet42 [~wallet42@unaffiliated/wallet42] has joined #bitcoin-wizards
12:07 -!- Adlai [~Adlai@gateway/tor-sasl/adlai] has joined #bitcoin-wizards
12:10 -!- jps [~Jud@cpe-74-72-116-143.nyc.res.rr.com] has quit [Quit: jps]
12:11 -!- wallet42 [~wallet42@unaffiliated/wallet42] has quit [Quit: Leaving.]
12:16 -!- Aquent [~Aquent@gateway/tor-sasl/aquent] has joined #bitcoin-wizards
12:19 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has quit [Remote host closed the connection]
12:19 -!- hearn [~mike@84-75-198-85.dclient.hispeed.ch] has quit [Quit: Textual IRC Client: www.textualapp.com]
12:22 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-wizards
12:22 -!- mkarrer [~mkarrer@122.Red-88-1-121.dynamicIP.rima-tde.net] has quit [Remote host closed the connection]
12:23 -!- KingCoin [~KingCoin@unaffiliated/kingcoin] has joined #bitcoin-wizards
12:23 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has joined #bitcoin-wizards
12:25 -!- jps [~Jud@cpe-74-72-116-143.nyc.res.rr.com] has joined #bitcoin-wizards
12:35 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has quit [Remote host closed the connection]
12:37 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has joined #bitcoin-wizards
12:45 -!- jps [~Jud@cpe-74-72-116-143.nyc.res.rr.com] has quit [Quit: jps]
12:46 -!- hearn [~mike@84-75-198-85.dclient.hispeed.ch] has joined #bitcoin-wizards
12:47 -!- dansmith- [~dansmith@85.25.117.24] has quit [Read error: Connection reset by peer]
12:53 -!- spiftheninja [~miner@173-20-237-20.client.mchsi.com] has joined #bitcoin-wizards
12:59 -!- profreid [~profreid@a88-115-210-162.elisa-laajakaista.fi] has joined #bitcoin-wizards
13:02 -!- dansmith- [~dansmith@85.25.117.24] has joined #bitcoin-wizards
13:08 < ahmed_> does anyone here know how to get 0x00000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF from CBigNum(~uint256(0) >> 32) ?
13:09 <@gwillen> ahmed_: 'how to get' in what sense? I.e. what are you trying to do?
13:09 < ahmed_> gwillen: essentially just work out how the hex value is obtained from the CBignum value
13:09 < ahmed_> since ive seen a lot of altcoins with varying values for nProofOfWorkLimit so i want to make sure i have the correct diff1
13:10 <@gwillen> ahh, well, start with 256 bits of 0, then flip them all to 256 bits of 1, then shift right by 32 bits (shifting in 32 zeroes), so now you have 32 zeroes and 224 ones
13:10 < ahmed_> gwillen: do u have any code based examples?
13:11 <@gwillen> if you are trying to make an altcoin, you're really asking in the wrong place
13:11 < ahmed_> gwillen: nope definitely not trying to work on an altcoin
13:12 <@gwillen> what are you trying to do? :-)
13:12 < ahmed_> im working on some pool software which i'd like to work with as many altcoins (even some of the shittier altcoins ugh)
13:12 <@gwillen> ahhhh
13:12 <@gwillen> well, what you're asking about is pretty basic bit-math stuff
13:13 < apoelstra> ahmed_: is that the mindiff value?
13:13 < ahmed_> apoelstra: from the wiki yep
13:13 < apoelstra> ahmed_: it should have only 6 F's in it iirc, one sec..
13:14 < ahmed_> i figured once i can work out how it works for BTC, then i can do it myself for all coins
13:14 < apoelstra> no, see alts.pdf, once you have figured out bit manipulation you are not even close to being able to write crypto software
13:14 < ahmed_> apoelstra: im not writing crypto software at all though
13:14 < apoelstra> just reading it?
13:15 < ahmed_> im writing pool software, which works. however im not confident in validating shares for altcoins
13:15 < apoelstra> validating shares is cryptography
13:15 < ahmed_> apoelstra:  yeah in a way. i just need to make sure that im getting the right values so i dont get hit by the same exploit LTC did a year bag
13:15 < amiller> ahmed_, this is more of a #bitcoin-dev question
13:15 < apoelstra> but np, it's not a huge deal because the consequences of screwup are well contained
13:15 < ahmed_> *back
13:16 < tacotime> yeah #bitcoin-dev or #whicheveraltcoin-dev
13:16 < gmaxwell> amiller: more like a "go ask the altcoin you're working on question"
13:16 < gmaxwell> since the behavior in varrious altcoins is basically random.
13:16 < tacotime> yeah
13:16 < ahmed_> gmaxwell: and how can that work when your working on a high number of alts including bitcoin?
13:17 < gmaxwell> E.g. the stratum protocol stuf for ltc just uses a totally bogus handling of difficulty.
13:17 < tacotime> monero's sharediff stuff is different but equally as cryptic as bitcoin's
13:17 -!- AlphaBar123 [~AlphaBar@c-71-202-114-230.hsd1.ca.comcast.net] has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
13:17 < ahmed_> if u want i can send u a PM to show u i have BTC on my pool frontend
13:17 < apoelstra> ahmed_: have you read alts.pdf? we are all burned out providing consulting for free..
13:17 < tacotime> yeah :/
13:17 < apoelstra> ahmed_: i'm only biting because i also think that bit-twiddle is really weird
13:17 < gmaxwell> ahmed_: besides, you cannot handle things that are different generally. You'll only have mixed success.
13:17 < apoelstra> it's at https://github.com/apoelstra/rust-bitcoin/blob/master/src/blockdata/constants.rs#L40-L43 in a readable way, sorry everyone to be OT. i'll stop now
13:17 < tacotime> apoelstra: no more andytoshi?
13:18 < ahmed_> gmaxwell: that is true, just trying to cover my ass wherever possible
13:18 < apoelstra> tacotime: oh, oops :) i'll be andytoshi again when wpsoftware.net comes back online
13:18 < apoelstra> tacotime: three power outages in as many days
13:18 < ahmed_> thanks apoelstra the link on bitcoin.ninja isnt working
13:18 < gmaxwell> ahmed_: they're basically free to do anything, and some have randomly adjusted what they're doing without understanding so are unlikely to behave in any really sane way.
13:18 < apoelstra> tacotime: crazy stormy in vancouver apparently... ...and my IRC screen session is there
13:18 -!- AlphaBar123 [~AlphaBar@c-71-202-114-230.hsd1.ca.comcast.net] has joined #bitcoin-wizards
13:19 < ahmed_> gmaxwell: precisely my issue. theres some that arent too bad. (i tend to try and help those where possible) but some are flat out stupid
13:19 < gmaxwell> (doubly so for straum, which ends up sending some normative data as @#$@ floating point numbers instead of integer targets or decodable "bits" values.)
13:19 -!- AlphaBar123 [~AlphaBar@c-71-202-114-230.hsd1.ca.comcast.net] has quit [Client Quit]
13:20 -!- AnoAnon [~AnoAnon@197.37.73.53] has joined #bitcoin-wizards
13:20 < gmaxwell> (hurray for protocols developed in secret without peer review. :( )
13:20 -!- AnoAnon [~AnoAnon@197.37.73.53] has quit [Max SendQ exceeded]
13:20 < ahmed_> haha, +1 to there. gbt is easier to use too imo
13:21 < tacotime> speaking of non-peer reviewed systems, figured out my entire ticketing/lottery system had a catastrophic bug. thank god for simnet at least, i guess.
13:22 < gmaxwell> tacotime: :(
13:22 < ahmed_> tacotime: the best part is atleast figuring it out though
13:22 < ahmed_> theres some people *cough* who develop something and leave it there for everyone to use when its still shit
13:23 < tacotime> gmaxwell: just gotta patch and hope that works -- thinking about it now it was really naive and it's obvious why it spends more tickets than it generates. it's easy to fix, but there's always going to be a problem where it's possible to run out of tickets and so block validation halts. the more tickets and ticket buckets issued, the less likely, but i need to talk to the math guys and actually work out some kind of probability for that happenin
13:23 < tacotime> g i guess.
13:23  * ahmed_ wishes slush0 was here so he could complain
13:24  * tacotime rubs head.
13:24 < tacotime> before testnet release though i'll feed it all to them in a general overview and audit too, to make sure nothing else is really wrong with it.
13:24 < tacotime> better to lack confidence in regards to cryptocurrencies.
13:28 -!- gloriusAgain [~gloriusag@g225037024.adsl.alicedsl.de] has quit [Remote host closed the connection]
13:28 -!- vfor [~Adium@g225037024.adsl.alicedsl.de] has quit [Quit: Leaving.]
13:29 -!- gloriusAgain [~gloriusag@g225037024.adsl.alicedsl.de] has joined #bitcoin-wizards
13:33 -!- gloriusAgain [~gloriusag@g225037024.adsl.alicedsl.de] has quit [Ping timeout: 272 seconds]
13:42 -!- HaltingState [~HaltingSt@unaffiliated/haltingstate] has quit [Remote host closed the connection]
13:43 -!- KingCoin [~KingCoin@unaffiliated/kingcoin] has quit [Quit: KingCoin]
13:44 -!- KingCoin [~KingCoin@unaffiliated/kingcoin] has joined #bitcoin-wizards
13:59 -!- benten [~benten@unaffiliated/benten] has joined #bitcoin-wizards
14:04 -!- MoALTz [~no@user-164-127-68-184.play-internet.pl] has quit [Ping timeout: 240 seconds]
14:16 -!- teknic111 [~Johnny@ool-4352401e.dyn.optonline.net] has joined #bitcoin-wizards
14:16 -!- JohnnyBitcoin [~Johnny@ool-4352401e.dyn.optonline.net] has quit [Ping timeout: 255 seconds]
14:32 -!- adam3us [~Adium@c31-67.i07-8.onvol.net] has quit [Quit: Leaving.]
14:51 < kanzure> http://diyhpl.us/~bryan/papers2/bitcoin/Private%20key%20recovery%20combination%20attacks:%20On%20extreme%20fragility%20of%20popular%20Bitcoin%20key%20management,%20wallet%20and%20cold%20storage%20solutions%20in%20presence%20of%20poor%20RNG%20events.pdf
14:51 < kanzure> (i haven't read it yet, not an endorsement, etc.)
14:52 < kanzure> although i am not particularly amused by the abstract's observation that cold storage does not need t be compromised to have already been compromised by a poorly implemented rng. that doesn't seem to be worth mentioning?
14:55 -!- profreid [~profreid@a88-115-210-162.elisa-laajakaista.fi] has quit [Quit: profreid]
14:56 < gmaxwell> kanzure: I commented a bit on it at https://bitcointalk.org/index.php?topic=834318.0
14:57 < kanzure> hmm i strange your opinion about the strangeness of it. i'm going to move it into meh/ (for anyone who finds the link broken)
14:58 < gmaxwell> s/strange/share/
14:58 < kanzure> there was also that paper posted on arxiv that had a similar style (pandering to various fears)
14:59 < Luke-Jr> yet more "attacks" that assume poor random
14:59 < kanzure> i'm not prepared to identify what that behavior is but it really seems like some sort of academic attempt at landgrabbing.. which is fine.. but why not just landgrab legitimately useful or novel stuff?
15:00 < nsh> kanzure, i'll but you a pint if you replace every space with an underscore in on your server filesystem
15:00 < nsh> *buy
15:00 < nsh> there's only so many %20 you can see in one line before your eyes hurt
15:00 < gmaxwell> The author has published a number of really crappy complaints about Bitcoin, rehashing known stuff and hyping uninteresting things. I actually thought he was some kook (his first papers were randomly modulating into allcaps and other strange tone which are common online markers of schizophrenia), but apparently he's credentialed.  It's annyoing to wade through his output, eventually he'll probably find something interesting but I'll ...
15:00 < gmaxwell> ... probably ignore it due to the history of uninteresting commentary. :(
15:01  * nsh knows this problem very well
15:01 < nsh> gmaxwell, did you seem my comments about malleability in your simply secure computation scheme?
15:02 < gmaxwell> nsh: no, lemme look.
15:02  * nsh finds logref
15:02 < gmaxwell> kanzure: I have some sympathy there, ... it's really common to find something you think is novel in this space only to find some forum post in 2011 that covers it... or worse, only maybe covers it because the post wasn't expanded enough to be sure.
15:02 -!- moa [~kiwigb@opentransactions/dev/moa] has joined #bitcoin-wizards
15:03 < kanzure> nsh: i'll accept some arguments against my file naming convention but you'll have to actually make some. on the other hand, i might just change it anyway because you've already asked..
15:03 < gmaxwell> I think there is some weird cultural thing where it's considered virtuous to be highly agressive and expansive in claims.... which is annoying, but tolerable when the claims are actually interesting.
15:03 < nsh> .to andytoshi new log layout on https://botbot.me/freenode/bitcoin-wizards/ is kinda neat (with infinite scroll) but linkable anchors to lines is pretty essential
15:03 < yoleaux> nsh: I'll pass your message to andytoshi.
15:03 < kanzure> gmaxwell: but isn't that finding-something pretty typical in academia? or what's going on here.
15:04 < amiller> gmaxwell, that author also has a weird page about AES http://www.cryptosystem.net/aes/
15:04 < nsh> there's an interesting malleability case in your scheme gmaxwell
15:04 < nsh> --
15:04 < nsh> I send the commitments to you.
15:04 < nsh> I then compute the hash of all the commitments.
15:04 < nsh> I use the resulting super-commitment to select a random permutation of the encrypted
15:04 < nsh> gates. E.g. I use that hash to initialize a random shuffle on the gates.
15:04 < kanzure> "highly aggressive and expansive in claims".... almost like in patents (argue everything and see what you get to keep)
15:04 < nsh> -- if you design the circuit so that certain inputs are equivalent, you can grind the supercommitment
15:04 < nsh> i don't know if that would be useful at all
15:04 < nsh> i don't think it matters
15:04 < nsh> but it differentiates between reversible and irreversible circuits which is interesting
15:04 < nsh> (reposted from logs)
15:05 < gmaxwell> kanzure: well normally academic publishing has huge pressure against repetition, to the detriment of the knoweldge of mankind (since slightly improved rehashings and summaries can be some of the most valuable works); but even thats breaking down as more novel venues of publishing crop up (e.g. arxiv) and since most interesting work on Bitcoin has come from 'industry' (e.g. bct) historically.
15:05 < nsh> (because only irreversible circuits allow you to lose information in the circuit about the inputs which would affect the commitment)
15:05 < nsh> (lose so as to not affect the outputs)
15:06 < nsh> thinking about it more, it might matter if the security parameter (how much of the circuit you reveal) is low
15:06 < nsh> but practical applications will be quite conservative
15:07 < gmaxwell> nsh: I'm not following when you'd grind the super-commitment (e.g. what is the input that you're changing to change the super commitment)?
15:08 < Luke-Jr> note: had this been a real attack, we'd be larting him for not disclosing it to be fixed prior to publishing
15:09 < Luke-Jr> so it's probably say he's aware his attack isn't real, and isn't disclosing that in his paper..
15:09 < kanzure> "it's not published, it's an eprint" (kidding)
15:09 < Luke-Jr> safe to say*
15:10 < nsh> if you design a circuit so that some of the inputs are redundant, can't you affect the hash of all the commitments in a way that doesn't affect the operation of the circuit
15:10 < nsh> so that which subset of the gates you reveal can be controlled
15:10 < nsh> --
15:10 < nsh> I use the resulting super-commitment to select a random permutation of the encrypted
15:10 < nsh> gates. E.g. I use that hash to initialize a random shuffle on the gates.
15:10 < nsh> Then I reveal the gates and their encryption keys for the first half of the gates
15:10 < nsh> in the shuffled list.
15:10 < nsh> --
15:11 < nsh> ie, it's not a random shuffle if you can tweak the input
15:13 < gmaxwell> nsh: yes, you can grind it, though grinding it alone does nothing harmful. Now imagine that you add a single corrupted gate to the bag-of-gates: what happens here is that either the 'random' puts it in the revealed half... in which case the gig is up. so you grind it (or get lucky) and it ends up in the used half, in which case it doesn't agree with any of it's duplicates... so again the gig is up.
15:14 < nsh> ah, right
15:14 < gmaxwell> So one bad gate is always detected.  Now, you can put more bad gates in, but the probablity of them all ending up in the same duplication group is low, and the more bad gates you put in the greater the chance that one ends up in the set you reveal.
15:14 < nsh> oh, i see
15:14 < nsh> it's inherently fragile
15:15 < nsh> the harder you try and cheat, the more (exponentially? quadratically?) lucky you need to be to get away with it
15:15 < gmaxwell> e.g. if the duplication group is N, then you put N bad gates in, and grind to try to get them to all land at the same place in the circuit, which is infeasable for sufficient parameters.
15:16 < nsh> is it possible in principle to design a (strong) hash function that's commutative over XOR?
15:17 < nsh> seems this would be a powerful primitive
15:18 < gmaxwell> It's possible in principle... using more cryptographic assumptions.
15:18 < nsh> such as those used for accumulators?
15:20 < nsh> it'd be nice to have a graphical(ly renderable) dependency structure for cryptographic assumptions and primitives
15:21 < gmaxwell> I wasted a bunch of time on a version that used a ECDLP assumption and additive homorphism to achive it a commutative hash, only to later realize that (1) the ability to wrap the group let you cheat (because the group is prime order) and (2) I needed additional assumptions about subgroup testing if instead used in a group with non-prime order which I didn't know how to prove (and didn't even believe were true).  Probably there is a ...
15:21 < gmaxwell> ... way to do it that involves additional range proofs... but it was escaping a level of complexity that I considered acceptable as a toy/teaching cryptosystem at that point.
15:21  * nsh nods
15:22 < gmaxwell> I'm making a (maybe somewhat ill-advised) assumption that if there were a simple way to do this with O(N) scaling that someone would have published it already.
15:24 < nsh> like feynmann said: "there's plenty of room at the bottom"
15:24 < nsh> and it's productive to think about what exactly the quadratic inefficiency represents on some deep level
15:25 < gmaxwell> yea, but also plenty of risk here... lets say I do actually find something that is O(N) and only needs hashing and some basic EC math and only modest constant factors. It would be attractive to actually use such a thing. But the work required to be confident of its security is huge.
15:25 < nsh> any inefficiency where more efficiency is possible represents some previously nondiscerned symmetry or equivalent structure
15:25  * nsh nods
15:26 < gmaxwell> so it's almost not worth trying, when I have so many other things to do ... many of which don't carry the same risks or don't already have people working on them.
15:26  * nsh nods
15:26 < nsh> vita brevis
15:26 < nsh> but it's productive nonetheless, regardless of whether it's optimally productive for you, personally :)
15:26 < nsh> it'd be nice if we have some kind of efficient system for handover of such avenues of investigation where time does not permit
15:27 < nsh> *we had
15:27 < gmaxwell> yea, well thats perhaps true.. or perhaps not. Me publishing a half baked scheme might actually mean someone who wants to put the time working on showing it secure can't actually publish their results in academic fora.
15:27 < nsh> hmm
15:28 < nsh> hard to imagine how the existence of some thought could preclude academic treatment
15:28 < nsh> it might lead research up some garden path, but that's a ubiquitous risk
15:28 < kanzure> "Secure and efficient asynchronous broadcast protocols" (2001) http://diyhpl.us/~bryan/papers2/bitcoin/Secure%20and%20efficient%20asynchronous%20broadcast%20protocols.pdf
15:28 < gmaxwell> (thats in fact part of why my scheme is just a text file that I've not published beyond sharing it with a few people around here; it needs a better section on the statistical implications and if I go publishing this where lots of people see it, I'm less able to ask other people to work on that part)
15:29  * nsh nods
15:32 < kanzure> "As our network is insecure and asynchronous, protocol execution is defined entirely via the adversary. The adversary is a polynomial-time interactive Turing machine that schedules and delivers all messages and corrupts some parties."
15:32 < gmaxwell> kanzure: doesn't work in the dynamic membership model; see 2.3.3 they assume a dealer that keys the participants.
15:32 < kanzure> right, some pki stuff
15:33 < gmaxwell> (I wish it were easier to extract model assumptions for papers; I'm getting pretty good at it now; but it still takes a fair amount of time on some papers)
15:33 < kanzure> oh, they are also assuming that nodes are always online..?
15:34 < gmaxwell> yea, so virtual every consensus anything paper assumes: There is static, identified, key holding, non-sybil (somehow) participants, who all are online if they are considered honest, and who can all reach each other (or if they can't there is some threshold partitioning allowed, but it's directly traded off with jammability).
15:35 < nsh> this is why amiller (et al.) latest is exciting
15:35 < gmaxwell> There is a paper called .. uh.. blue something I linked in here a long time ago for mostly efficient partially ordered broadcast that looked useful, lemme see if I can find it.
15:35 < kanzure> i'll keep those default assumptions in mind
15:36 < gmaxwell> http://matt.singlethink.net/projects/mpotr/oldblue-draft.pdf
15:40 < amiller> i reviewed a paper a couple weeks ago
15:40 < amiller> that presents a new method for some technique
15:40 < amiller> for the security proof, it just reduces to an attacker on an earlier paper
15:40 < amiller> that earlier paper, the security proof is based on a generic construction of a third earlier paper
15:41 < amiller> they made a typo in importing the generic construction
15:42 < gmaxwell> oops.
15:42 < amiller> it took wayyy too much effort to find that proof error (i only looked because another reviewer basically said 'lul this is obviously broken heres a cheeky counter example')
15:42 -!- andy-logbot [~bitcoin--@184.65.107.59] has joined #bitcoin-wizards
15:42  * andy-logbot is logging
15:42 < amiller> and the error amounts to like, an import mismatch
15:43 < gmaxwell> amiller: did andytosh tell you? we found a bug in wolfram alpha while checking the pegged sidechains paper. (Bluematt plugged one of the equations into wolfram alpha; told me "that equation equals zero" and I was thinking "great we've proved a sum of positive powers of e can be zero, lets go collect or fields medal" ...)
15:43 < amiller> lol
15:43 < gmaxwell> haven't had a chance to see if mathmatica is similarly bugged yet.
15:44 < gmaxwell> (basically it claims the reorg sum formula is EXACTLY equal to zero (not a num approx.).  If you remove the 1- from the equation it correctly gives a 0.999(lots)(non9s) answer.
15:44 < gmaxwell> )
15:45 < gmaxwell> s/or fields/our fields/
15:53 < nsh> what was the input to wolfram alpha?
15:54 < gmaxwell> equation at line 576 (page 19) of sidechains.pdf
15:55 < nsh> ah
15:56 < nsh> 10^-196 is a lot like zero to be fair
15:56 < nsh> in engineering terms
15:56 <@gwillen> gmaxwell: it also has a date handling bug we found when writing a date-based mystery hunt puzzle
15:56 <@gwillen> it computes date intervals wrong crossing some historic boundary
15:56 < nsh> a calendar change?
15:56 <@gwillen> in particular it computes them inconsistently depending on how you do it (it's not just that it disagrees with us about the calendar)
15:57  * nsh nods
15:57 <@gwillen> it was some date related to the julian-gregorian change, yes
15:57 <@gwillen> I don't remember the exact details of why that particular date
15:57 <@gwillen> I think it was a february 29
15:57 < nsh> i think some of-- right
15:57 < nsh> some of the leap corrections don't work well with the change of calendar
15:58 <@gwillen> if you landed on it in one direction it would claim you were on feb 29 but if you landed on it in the other direction it would claim you were on mar 1, I think
15:58 < nsh> once a leap second correction over NTP fucked up everyone's debian boxes via a futex(2) deadlock
15:58 < gmaxwell> sept 3rd 1752 perhaps?
15:58 <@gwillen> hah.
15:58 < nsh>  a few years ago
15:58 < nsh> that was fun
15:58 -!- andy-logbot [~bitcoin--@184.65.107.59] has quit [Ping timeout: 260 seconds]
15:58 <@gwillen> gmaxwell: oh, have you run into this
15:58 <@gwillen> I could believe that I'm wrong about it being a feb
15:58 < nsh> .t http://serverfault.com/questions/403732/anyone-else-experiencing-high-rates-of-linux-server-crashes-during-a-leap-second
15:58 < yoleaux> nsh: Sorry, I don't know a timezone by that name.
15:58 < nsh> .title
15:58 < yoleaux> debian - Anyone else experiencing high rates of Linux server crashes during a leap second day? - Server Fault
15:59 < gmaxwell> no, just written date handling code before. :) (also why I know leap year rule trivia)
15:59 < nsh> software \o/
15:59 < gmaxwell> nsh: yea, we're doomed.
15:59 < nsh> if you can exploit strings(1)
15:59 < nsh> nothing is safe
15:59 < nsh> may as well go full luddite
15:59 < sipa> wut?
15:59 < gmaxwell> sipa: strings is exploitable
15:59 < nsh> .title http://lcamtuf.blogspot.co.uk/2014/10/psa-dont-run-strings-on-untrusted-files.html
15:59 < yoleaux> lcamtuf's blog: PSA: don't run 'strings' on untrusted files
15:59 < sipa> how so?
15:59 < nsh> because of a binwalk library
15:59 < nsh> that does 'clever'
15:59 < gmaxwell> (see also: my constant, unending, nagging about never using strings for anything. :P )
16:00 < sipa> hmm, can't remember any such nagging
16:00 < gmaxwell> (strings the data structure, I mean, not the program)
16:00 < nsh> " Interestingly, the problems with the utility aren't exactly new; Tavis spotted the first signs of trouble some nine years ago. "
16:00 < nsh> ( https://bugs.gentoo.org/show_bug.cgi?id=91398 )
16:00 < gmaxwell> sure you do, every time someone wants to add a string to the bitcoin protocol I've whined about it. :)
16:00 < nsh> oh, right
16:01 < sipa> heh, i had no idea it tried to decode binary format
16:01 < nsh> wouldn't have assumed it either
16:02 < sipa> gmaxwell: sorry, i thought you meant "never using the program 'strings' for anything"
16:02 < sipa> i'm aware of your aversion of the data type
16:02 < gmaxwell> yea, no, but there you go, strings does string handling and therefor is likely to be broken. :P
16:02 < gmaxwell> This prejudice has pretty much never failed me.
16:03  * nsh smiles
16:04 < woah> gmaxwell what is the core attribute that makes strings insecure in your opinion?
16:05 < nsh> they tend towards unsafe combinations of interpretation
16:05 < nsh> or muddy thinking thereabouts
16:06 -!- hashtag [~hashtag@CPE-69-23-221-39.wi.res.rr.com] has joined #bitcoin-wizards
16:06 -!- omni [~omni@75-101-96-71.dsl.static.fusionbroadband.com] has joined #bitcoin-wizards
16:06 -!- omni is now known as Guest52447
16:07 -!- vfor [~Adium@g225037024.adsl.alicedsl.de] has joined #bitcoin-wizards
16:07 < gmaxwell> woah: well, mostly experience says they are regardless of the causes. But if I were to guess, it's a mixture of in-band signaling and a lack of clear size bounding. (e.g. generic string handling code probably ought to handle strings of unbounded size; thats unreasonable so things often have limits, the limits can be surprising to callers, even when disclosed they're not always counted consistently)... plus they don't provide crisp ...
16:07 < gmaxwell> ... boundaries, inevitably you don't just implement strings but strings plus adhoc parsing.
16:07 -!- gloriusAgain [~gloriusag@g225037024.adsl.alicedsl.de] has joined #bitcoin-wizards
16:07 < gmaxwell> And then you get bugs from parsing inconsistencies too.
16:07 < woah> hmm very good points
16:08 -!- andy-logbot [~bitcoin--@184.65.107.59] has joined #bitcoin-wizards
16:08  * andy-logbot is logging
16:08 < gmaxwell> plus things like code that isn't 8-bit-clean, or code that handles things as unicode.  (that stuff interacts awesomely with random byte limits in string handling code, since truncation can create invalid codepoints.. or worse, cause a dumb reader to miss a null terminator)
16:08 < woah> hmmm its just a messy undertaking huh
16:09 < gmaxwell> Or code that has one idea of the length (e.g. because it created it) not agreeing with a strlen() (an example of an in-band signaling problem); so you get different code reading data from a string differently.
16:09 < gmaxwell> don't get me wrong, its often necessary to use strings. ... but I try to avoid them anywhere it isn't necessary.
16:11 -!- iambernie [~bernie@82-169-230-87.ip.telfort.nl] has quit [Ping timeout: 250 seconds]
16:12 < gmaxwell> oh another problem with strings is that they get embedded in protocols that carry explicit lengths... and then the two methods of counting can disagree and cause doom.
16:13 < gmaxwell> (in particular, I've found multiple authentication bypass vulnerabilties in commercial networking products due to this)
16:13 -!- iambernie [~bernie@82-169-230-87.ip.telfort.nl] has joined #bitcoin-wizards
16:15 -!- andy-logbot [~bitcoin--@184.65.107.59] has quit [Read error: Connection reset by peer]
16:15 -!- andy-logbot [~bitcoin--@184.65.107.59] has joined #bitcoin-wizards
16:15  * andy-logbot is logging
16:16 < woah> hmm so strings are just an easy place to mess up
16:16 < woah> and it's unfortunate to introduce that to a system that doesn't need it
16:17 < gmaxwell> well, everything is easy to mess up, strings seem simpler than they actually are.
16:19 < nsh> right, it's the distance between perceived complexity and actual complexity that causes many issues
16:19 < nsh> abstraction allows us to build things that we couldn't otherwise, but it blinds us to the complexities that you can't really shove under the carpet
16:19 < nsh> or rug
16:19 -!- andy-logbot [~bitcoin--@184.65.107.59] has quit [Ping timeout: 250 seconds]
16:33 -!- hearn [~mike@84-75-198-85.dclient.hispeed.ch] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
16:34 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has joined #bitcoin-wizards
16:36 -!- zenojis [~quassel@2604:3400:dc1:45:216:3eff:fe76:3263] has quit [Ping timeout: 272 seconds]
16:37 <@gwillen> pascal strings are really not that bad (length-prefixed strings)
16:37 <@gwillen> c-strings are where you get in trouble, I think
16:37 <@gwillen> (of course, true pascal strings also have a maximum length, which has both pluses and minuses)
16:37 < gmaxwell> yes, many of my complaints are c-strings specific... people also do pascal like strings with varable length length bytes which have their own sources of fun.
16:38 < phantomcircuit> gmaxwell, failure to update length being the worst
16:39  * nsh wonders how Rust is coming along
16:40 -!- pen [~linker@42.119.112.255] has quit [Read error: Connection reset by peer]
16:40 -!- hashtag_ [~hashtag@CPE-69-23-221-39.wi.res.rr.com] has joined #bitcoin-wizards
16:40 -!- pen [~linker@42.119.112.255] has joined #bitcoin-wizards
16:40 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has quit [Remote host closed the connection]
16:41 -!- Guest52447 [~omni@75-101-96-71.dsl.static.fusionbroadband.com] has quit [Remote host closed the connection]
16:42 < lechuga_> whoa@strings vuln
16:42 < lechuga_> good2know
16:44 -!- hashtag [~hashtag@CPE-69-23-221-39.wi.res.rr.com] has quit [Ping timeout: 255 seconds]
16:45 -!- zenojis [~quassel@2604:3400:dc1:45:216:3eff:fe76:3263] has joined #bitcoin-wizards
16:47 <@gwillen> gmaxwell: djb's way of representing length-coded strings is pretty reasonable and _reasonably_ hard to fuck up
16:47 <@gwillen> it's something like "ASCII-encoded length, colon, string, comma", I believe
16:48 <@gwillen> so on the one hand it does have a delimiter, but on the other hand it would be hard to get too confused while parsing that without _noticing_ that you were confused
16:48 < phantomcircuit> gwillen, people screw it up even when it's something like big endian 64bit + string
16:48  * gwillen nods
16:48 -!- mapppum [~mappum@c-24-17-76-220.hsd1.wa.comcast.net] has joined #bitcoin-wizards
16:48 <@gwillen> that version seems hard to screw up
16:48 <@gwillen> as long as you have a test for zero and a test for 1
16:48 < phantomcircuit> switch endianness
16:48 <@gwillen> the test for 1 will catch that, though
16:49 <@gwillen> (i.e. if you do that it won't fail _occasionally_, it will fail _catastrophically and always_)
16:49 < phantomcircuit> gwillen, i've seen things where the check correctly swaps endianness
16:49 < phantomcircuit> but the actual code doesn't
16:49  * gwillen nod
16:49 < phantomcircuit> iirc firefox had an issue related to this with X.509 certs
16:51 < nsh> heh
16:53 -!- mapppum [~mappum@c-24-17-76-220.hsd1.wa.comcast.net] has quit [Remote host closed the connection]
16:54 -!- gavinandresen [~gavin@unaffiliated/gavinandresen] has quit [Ping timeout: 240 seconds]
16:54 -!- omni [~omni@75-101-96-71.dsl.static.fusionbroadband.com] has joined #bitcoin-wizards
16:55 -!- gavinandresen [~gavin@unaffiliated/gavinandresen] has joined #bitcoin-wizards
16:55 -!- omni is now known as Guest65380
16:57 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Remote host closed the connection]
16:58 -!- Guest65380 [~omni@75-101-96-71.dsl.static.fusionbroadband.com] has quit [Remote host closed the connection]
17:02 -!- llllllllll [~lllllllll@53-109.bbned.dsl.internl.net] has quit []
17:06 -!- benten [~benten@unaffiliated/benten] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
17:08 -!- mortale [~mortale@gateway/tor-sasl/mortale] has joined #bitcoin-wizards
17:12 < gmaxwell> ascii encoded length is pretty easy to screw up, it's also non-canonical ... e.g. 00001 vs 01 vs 1; which can cause some problems.
17:14 -!- gavinandresen [~gavin@unaffiliated/gavinandresen] has quit [Ping timeout: 258 seconds]
17:21 <@gwillen> gmaxwell: the noncanonicality is annoying, I hadn't noticed that before ... it's trivial to fix though (the first byte just can't be 0x30... assuming you making the zero-length encodeing ":," and not "0:,")
17:21 <@gwillen> encoding*
17:22 < gmaxwell> also, making sure you handle very large numbers and negative numbers is fun.
17:22 <@gwillen> well
17:23 <@gwillen> if you take a reasonable approach to parsing, and you bail if it exceeds you limits, then it shouldn't be too bad
17:23 <@gwillen> but yeah, that's a lot of if's
17:23 < gmaxwell> also, if you just go and atoi, you'll also have locale specific behavior creep in.
17:23 <@gwillen> oh dear, does atoi/strtol support separators?
17:23 <@gwillen> that's annoying
17:23 < phantomcircuit> gwillen, read right to left
17:24 < phantomcircuit> left to right reading value to tmp, right to left reading tmp
17:25 < gmaxwell> gwillen: Yup.
17:25 <@gwillen> :-(
17:25 <@gwillen> okay, that's not great
17:25 < gmaxwell> (you have no clue how much software is actually mildly busted because of this)
17:25 <@gwillen> :-(
17:26 <@gwillen> a lot of code that I've written has been wrong because of this :-(
17:26 <@gwillen> fortunately it was almost surely all hobby code that didn't matter
17:26 <@gwillen> and the wrongness was basically immaterial
17:26  * gmaxwell invokes the gmaxwell no strings maximum once more.
17:27 < gmaxwell> yea, in lots of software you don't have adversarial inputs and its mostly harmless.
17:30  * nsh smiles
17:31 < nsh> problem is people write things, then other people transplant them and attach them to the adversary spigots
17:32 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has quit [Quit: Leaving]
17:32 < nsh> eg, bash and env variables and CGI
17:32 <@gwillen> yeah.
17:33 -!- Quanttek [~quassel@2a02:8108:d00:870:cd38:a04a:8125:844b] has quit [Ping timeout: 260 seconds]
17:33 < gmaxwell> but yea, lots of stuff broken, for example virtually all flac implementations are screwed up... the replaygain tags for automatic levels adjustment are coded in ascii, and read using the locale-heeding C functions;  so you can get files from people in germany which screw up horribly on english hosts and vice versa.
17:34 < gmaxwell> even more fun, locale settings are not thread specific, so you can't wrap the calls easily in a library to force C locale and not risk screwing up other things... so you end up needing your own implementation.
17:37 -!- benten [~benten@unaffiliated/benten] has joined #bitcoin-wizards
17:38 -!- benten [~benten@unaffiliated/benten] has quit [Client Quit]
17:44 -!- benten [~benten@unaffiliated/benten] has joined #bitcoin-wizards
17:45 -!- benten [~benten@unaffiliated/benten] has quit [Client Quit]
17:50 -!- omni [~omni@75-101-96-71.dsl.static.fusionbroadband.com] has joined #bitcoin-wizards
17:50 -!- omni is now known as Guest3015
17:52 -!- benten [~benten@unaffiliated/benten] has joined #bitcoin-wizards
17:52 -!- benten [~benten@unaffiliated/benten] has quit [Client Quit]
17:57 -!- napedia [~napedia@unaffiliated/napedia] has quit [Ping timeout: 258 seconds]
18:00 -!- Adlai [~Adlai@gateway/tor-sasl/adlai] has quit [Remote host closed the connection]
18:00 -!- Adlai [~Adlai@gateway/tor-sasl/adlai] has joined #bitcoin-wizards
18:07 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has quit [Ping timeout: 244 seconds]
18:11 -!- mortale [~mortale@gateway/tor-sasl/mortale] has quit [Remote host closed the connection]
18:13 -!- mortale_ [~mortale@gateway/tor-sasl/mortale] has joined #bitcoin-wizards
18:14 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has joined #bitcoin-wizards
18:14 -!- mapppum [~mappum@c-24-17-76-220.hsd1.wa.comcast.net] has joined #bitcoin-wizards
18:15 -!- samson2 [~samson_@180.183.164.27] has joined #bitcoin-wizards
18:16 -!- samson_ [~samson_@180.183.164.27] has quit [Ping timeout: 240 seconds]
18:17 -!- vfor [~Adium@g225037024.adsl.alicedsl.de] has quit [Ping timeout: 244 seconds]
18:18 -!- zenojis [~quassel@2604:3400:dc1:45:216:3eff:fe76:3263] has quit [Ping timeout: 244 seconds]
18:23 -!- zenojis [~quassel@2604:3400:dc1:45:216:3eff:fe76:3263] has joined #bitcoin-wizards
18:29 -!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has quit [Quit: Leaving]
18:30 -!- tacotime [~mashkeys@198.52.200.63] has quit [Ping timeout: 265 seconds]
18:40 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has quit [Ping timeout: 258 seconds]
18:58 -!- mortale_ [~mortale@gateway/tor-sasl/mortale] has quit [Remote host closed the connection]
19:00 -!- mortale_ [~mortale@gateway/tor-sasl/mortale] has joined #bitcoin-wizards
19:04 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has joined #bitcoin-wizards
19:05 -!- nsh_ [~nsh@host86-158-34-11.range86-158.btcentralplus.com] has joined #bitcoin-wizards
19:14 -!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has joined #bitcoin-wizards
19:21 -!- tacotime [~mashkeys@198.52.200.63] has joined #bitcoin-wizards
19:25 -!- gavinandresen [~gavin@unaffiliated/gavinandresen] has joined #bitcoin-wizards
19:28 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has joined #bitcoin-wizards
19:29 -!- KingCoin [~KingCoin@unaffiliated/kingcoin] has quit [Quit: KingCoin]
19:31 -!- woah [~woah@199-241-202-232.PUBLIC.monkeybrains.net] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
19:33 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has quit [Ping timeout: 256 seconds]
19:35 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has quit [Quit: Reconnecting]
19:35 -!- justanot1eruser [~Justan@unaffiliated/justanotheruser] has joined #bitcoin-wizards
19:35 -!- justanot1eruser is now known as justanotheruser
19:36 -!- devrandom [~devrandom@gateway/tor-sasl/niftyzero1] has joined #bitcoin-wizards
19:40 -!- OX3 [~OX3@gateway-nat.fmrib.ox.ac.uk] has quit [Ping timeout: 256 seconds]
19:47 -!- pen [~linker@42.119.112.255] has quit [Ping timeout: 265 seconds]
19:47 -!- pen [~linker@42.119.112.255] has joined #bitcoin-wizards
19:55 -!- mapppum [~mappum@c-24-17-76-220.hsd1.wa.comcast.net] has quit [Quit: Stay fresh.]
20:01 -!- Greed [~Greed@unaffiliated/greed] has quit [Ping timeout: 240 seconds]
20:05 -!- gloriusAgain [~gloriusag@g225037024.adsl.alicedsl.de] has quit [Remote host closed the connection]
20:05 -!- gloriusAgain [~gloriusag@g225037024.adsl.alicedsl.de] has joined #bitcoin-wizards
20:06 -!- Greed [~Greed@unaffiliated/greed] has joined #bitcoin-wizards
20:10 -!- gloriusAgain [~gloriusag@g225037024.adsl.alicedsl.de] has quit [Ping timeout: 250 seconds]
20:16 -!- Guest3015 [~omni@75-101-96-71.dsl.static.fusionbroadband.com] has quit [Remote host closed the connection]
20:24 -!- Sangheili [Elite8385@gateway/shell/elitebnc/x-dagcgsepocmkiuud] has quit [Ping timeout: 265 seconds]
20:35 -!- gloriusAgain [~gloriusag@g225037024.adsl.alicedsl.de] has joined #bitcoin-wizards
20:36 -!- NewLiberty [~NewLibert@2602:304:cff8:1580:2141:2fb6:3b66:d7f5] has joined #bitcoin-wizards
20:42 -!- gloriusAgain [~gloriusag@g225037024.adsl.alicedsl.de] has quit [Ping timeout: 265 seconds]
20:51 -!- eslbaer_ [~eslbaer@p57BCE50F.dip0.t-ipconnect.de] has joined #bitcoin-wizards
20:55 -!- eslbaer [~eslbaer@p579E9D63.dip0.t-ipconnect.de] has quit [Ping timeout: 245 seconds]
21:05 -!- Burrito [~Burrito@unaffiliated/burrito] has quit [Quit: Leaving]
21:14 -!- TheSeven [~quassel@rockbox/developer/TheSeven] has quit [Disconnected by services]
21:14 -!- [7] [~quassel@rockbox/developer/TheSeven] has joined #bitcoin-wizards
21:16 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has quit [Ping timeout: 245 seconds]
21:23 -!- hashtag_ [~hashtag@CPE-69-23-221-39.wi.res.rr.com] has quit [Ping timeout: 265 seconds]
21:25 -!- devrandom [~devrandom@gateway/tor-sasl/niftyzero1] has quit [Ping timeout: 246 seconds]
21:27 -!- devrandom [~devrandom@gateway/tor-sasl/niftyzero1] has joined #bitcoin-wizards
21:29 -!- anton000 [~anton000@121.54.44.91] has joined #bitcoin-wizards
21:29 -!- anton000 [~anton000@121.54.44.91] has quit [Changing host]
21:29 -!- anton000 [~anton000@unaffiliated/anton000] has joined #bitcoin-wizards
21:31 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has joined #bitcoin-wizards
21:36 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has quit [Ping timeout: 250 seconds]
21:38 -!- c0rw1n is now known as c0rw|sleep
21:40 -!- KingCoin [~KingCoin@unaffiliated/kingcoin] has joined #bitcoin-wizards
21:44 -!- Dr-G [~Dr-G@gateway/tor-sasl/dr-g] has joined #bitcoin-wizards
21:45 -!- HaltingState [~HaltingSt@unaffiliated/haltingstate] has joined #bitcoin-wizards
21:45 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has joined #bitcoin-wizards
21:53 -!- machinery [~textual@148.240.141.29] has joined #bitcoin-wizards
22:00 -!- rdponticelli [~quassel@gateway/tor-sasl/rdponticelli] has quit [Ping timeout: 246 seconds]
22:04 -!- Transisto [~Trans@modemcable026.188-59-74.mc.videotron.ca] has joined #bitcoin-wizards
22:12 -!- napedia [~napedia@unaffiliated/napedia] has joined #bitcoin-wizards
22:25 -!- dansmith_ [~dansmith@178-33-115-54.kimsufi.com] has quit [Quit: quit]
22:38 -!- omni [~omni@75-101-96-71.dsl.static.fusionbroadband.com] has joined #bitcoin-wizards
22:39 -!- omni is now known as Guest83246
22:41 -!- Transisto [~Trans@modemcable026.188-59-74.mc.videotron.ca] has quit []
22:46 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has quit [Quit: Reconnecting]
22:46 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has joined #bitcoin-wizards
22:47 -!- napedia [~napedia@unaffiliated/napedia] has quit [Ping timeout: 265 seconds]
22:48 -!- fanquake [~anonymous@unaffiliated/fanquake] has joined #bitcoin-wizards
23:03 -!- Guest83246 [~omni@75-101-96-71.dsl.static.fusionbroadband.com] has quit [Remote host closed the connection]
23:04 -!- zooko [~user@c-75-70-204-109.hsd1.co.comcast.net] has quit [Ping timeout: 245 seconds]
23:08 -!- zooko [~user@c-75-70-204-109.hsd1.co.comcast.net] has joined #bitcoin-wizards
23:19 -!- omni [~omni@75-101-96-71.dsl.static.fusionbroadband.com] has joined #bitcoin-wizards
23:20 -!- omni is now known as Guest19496
23:24 -!- Dr-G [~Dr-G@gateway/tor-sasl/dr-g] has quit [Remote host closed the connection]
23:26 -!- zooko [~user@c-75-70-204-109.hsd1.co.comcast.net] has quit [Ping timeout: 265 seconds]
23:28 -!- Dr-G [~Dr-G@gateway/tor-sasl/dr-g] has joined #bitcoin-wizards
23:29 -!- NewLiberty [~NewLibert@2602:304:cff8:1580:2141:2fb6:3b66:d7f5] has quit [Ping timeout: 272 seconds]
23:29 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has quit [Ping timeout: 245 seconds]
23:30 -!- machinery [~textual@148.240.141.29] has quit [Quit: Textual IRC Client: www.textualapp.com]
23:33 -!- adam3us [~Adium@c31-67.i07-8.onvol.net] has joined #bitcoin-wizards
23:34 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has joined #bitcoin-wizards
23:39 -!- crowex [~crowex@host-78-147-106-214.as13285.net] has quit [Ping timeout: 265 seconds]
23:48 -!- Transisto [Transisto@213.179.213.67] has joined #bitcoin-wizards
23:51 -!- gsdgdfs [~Trans@modemcable026.188-59-74.mc.videotron.ca] has joined #bitcoin-wizards
23:52 -!- gsdgdfs [~Trans@modemcable026.188-59-74.mc.videotron.ca] has quit [Client Quit]
23:52 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has joined #bitcoin-wizards
23:53 -!- gsdgdfs [~Trans@modemcable026.188-59-74.mc.videotron.ca] has joined #bitcoin-wizards
23:53 -!- Transisto [Transisto@213.179.213.67] has quit [Ping timeout: 250 seconds]
23:58 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has quit [Ping timeout: 244 seconds]
--- Log closed Sun Oct 26 00:00:29 2014