IRC logs of #boinc for Friday, 2014-07-11

00:13 *** yoyo[RKN] has joined #boinc

00:15 *** PovAddictW has quit IRC

00:18 *** yoyo[RKN] has quit IRC

04:12 *** irsol has quit IRC

04:24 *** irsol has joined #boinc

05:08 *** LocutusOfBorg1 has quit IRC

05:26 *** chek2fire has joined #boinc

05:38 *** desti has joined #boinc

05:40 *** desti_T2 has quit IRC

05:56 *** LocutusOfBorg1 has joined #boinc

07:56 *** Caterpillar has joined #boinc

08:34 *** PovAddictW has joined #boinc

08:37 *** Caterpillar has quit IRC

08:38 *** Caterpillar has joined #boinc

09:01 *** LocutusOfBorg1 has quit IRC

09:21 *** LocutusOfBorg1 has joined #boinc

10:46 *** eagles0513875 has quit IRC

10:46 *** eagles0513875 has joined #boinc

10:46 *** eagles0513875 has joined #boinc

12:03 *** LocutusOfBorg1 has quit IRC

13:12 *** Caterpillar has quit IRC

13:37 *** stux|RC has joined #boinc

13:41 *** stux|RC-only has quit IRC

15:22 *** yoyo[RKN] has joined #boinc

16:23 *** whynot has joined #boinc

16:39 *** chek2fire has quit IRC

17:39 *** desti_T2 has joined #boinc

17:42 *** desti has quit IRC

17:51 *** desti has joined #boinc

17:53 *** desti_T2 has quit IRC

18:04 *** efc has joined #boinc

18:26 *** desti has quit IRC

18:26 *** desti has joined #boinc

18:30 *** efc has quit IRC

18:30 *** MiniFridge has joined #boinc

18:31 *** efc has joined #boinc

18:37 *** si has joined #boinc

18:37 *** si has quit IRC

18:37 *** si has joined #boinc

18:39 *** whynot has quit IRC

19:40 *** si has quit IRC

19:43 *** efc has quit IRC

19:57 *** ChanServ sets mode: -o CoderForLife

19:57 <CoderForLife> &wx 45140

19:57 <Romulus> CoderForLife: Temperature: 82.2F / 27.9C | Humidity: 55% | Pressure: 30.15in / 1021hPa (Falling) | Conditions: Mostly Cloudy | Wind Direction: SW | Wind Speed: 0.0mph / 0.0km/h ; Friday - Clear. High of 88F. Winds less than 5 mph.; Friday Night - Partly cloudy. Fog overnight. Low of 61F. Winds less than 5 mph.; Saturday - Partly cloudy. High of 90F. Winds less than 5 mph.;

20:00 <PovAddictW> hi CFL

20:01 <PovAddictW> &wx london

20:01 <Romulus> PovAddictW: Temperature: 77F / 25C | Humidity: 57% | Pressure: 30.19in / 1022hPa (Steady) | Conditions: Scattered Clouds | Wind Direction: SW | Wind Speed: 6mph / 9km/h ; Tonight - Partly cloudy. Becoming clear this evening. Low 13C(55F).; Saturday - Sunny. Becoming a mix of sun and cloud late in the morning. High 29C(84F). UV index 10 or very high. Saturday night increasing cloudiness. A few (1 more message)

20:01 <PovAddictW> nice, hope it stays that way in 3 weeks

20:21 <desti> no way

20:26 *** Switeck has joined #boinc

20:27 *** Switeck has left #boinc

20:54 <Patriot> broke 4m pts today in gpugrid :D

20:56 <CoderForLife> hi PovAddictW

20:57 *** efc has joined #boinc

21:09 *** zombie67 has joined #boinc

21:10 *** scatterp has joined #boinc

21:10 <scatterp> !help

21:10 <scatterp> Romulus help

21:10 <Romulus> scatterp: (help [<plugin>] [<command>]) -- This command gives a useful description of what <command> does. <plugin> is only necessary if the command is in more than one plugin.

21:10 <scatterp> Romulus help help

21:10 <Romulus> scatterp: (help [<plugin>] [<command>]) -- This command gives a useful description of what <command> does. <plugin> is only necessary if the command is in more than one plugin.

21:11 <scatterp> :/

21:11 <scatterp> if i have a 20 byte readme file and its sha1 is it possible to recover the readme file ?

21:11 <scatterp> from the sha1 alone that is

21:12 <Patriot> theoretcially....

21:12 <scatterp> sorry 21 bytes

21:12 <Patriot> I think

21:12 <PovAddictW> no

21:12 <scatterp> i guess 6 bytes might be the file name README

21:12 <Patriot> lol

21:13 <PovAddictW> you'd have to try 1461501637330902918203684832716283019655932542976 files till you get the right hash

21:13 <scatterp> PovAddictW: why no ?

21:13 <Patriot> and there is why I said theoretcially

21:13 <Patriot> or you would have to reverse engineer the hash

21:14 <scatterp> that does not seem such a lot especially if the first 6 bytes are README

21:14 <scatterp> could be a EOF byte too

21:14 <Patriot> so you could make some assumptions as you brute force it

21:14 <Patriot> still a darn lot of combinations

21:15 <efc> the hash of X would map to various possible files of various lengths

21:15 <scatterp> read me contains a-z A-Z

21:15 <Patriot> it is possible for a hash to not be unique ....

21:15 <scatterp> efc oh so it wouldnt result in one file even if it worked

21:15 <scatterp> ah ok

21:15 <Patriot> someone proved that in court to get out of a camera speeding ticket

21:15 <Patriot> lol

21:16 <scatterp> nice lol

21:16 <efc> knowing something of the plaintext would help a lot

21:16 <efc> and the length or any other characateristics

21:16 <scatterp> ok second question if this was a part of a zip file and i had the readme.txt would that be any help in getting the password ?

21:16 <efc> but you are still talking brute force

21:16 <scatterp> efc well i think 6 bytes are README

21:18 <efc> if you know its 21 bytes, then generate every 21 byte string, SHA it, if it matches you are doing. It will take a while.

21:18 <efc> *you are done

21:18 <scatterp> ok there is another vector that might be easier

21:18 <scatterp> the password to the zip its self

21:19 <efc> that's the one-way or trapdoor aspect of the hash, supposed to be hard to reverse compute

21:20 <scatterp> yeah

21:20 <scatterp> i also have this 64132F89804DF4DB3F03DED87B36D467027132EF9D79AE6CD38E1E2CD3ED9080860EF53ED1CBA6D8395BDBCF541C1E2B

21:21 <scatterp> if thats encrypted with a string of the same length the result is F8A555D2 .... F4DFD3CB which needs a 32-bit endian byte flip to produce the pass to the ziped readme

21:24 <scatterp> i guess thats no help with out the encryption string

21:25 <scatterp> ooh the 21 bytes are words that helps a lot right

21:25 <efc> There must be something really juicy in this readme file.

21:26 <scatterp> well i am wondering if i could use it to get the zip password

21:26 <scatterp> but yea

21:26 <Romulus> Title: r0bf0rdsn0w (at

21:27 <scatterp> i dont have the s5l8940x AES GID key

21:27 <scatterp> :/

21:28 <scatterp> the zip is version 5.1

21:28 <scatterp> and key seems to long to brute force

21:29 <efc> you might be able to brute force 64 bits, depending on various factors

21:30 <scatterp> the zip key ?

21:31 <efc> i withdraw the comment

21:31 <scatterp> should be 96 bytes for the zip key i think

21:32 <scatterp> oh i see

21:32 <scatterp> go after the gid key hrm

21:38 <scatterp> what would the factors be ?

21:38 <scatterp> how much reduction could be achieved?

21:39 <scatterp> my brother has some ex-bitcoin rigs that are quite fast

21:43 <efc> for serious brute force, you'd want to go video, fpga, or asic, depending on the size of your intelligence agency.

21:45 <efc> don't know anything about sha, but some of the others I looked at were very amenable to hardware

21:48 <scatterp> my brothers a director of the company that created one of the fpga boards for bitcoins there working on asics and he has a lot of redundant video power

21:48 <efc> generally though, brute forcing 96 bytes of anything would be infeasible no matter what the resources.

21:49 <scatterp> but sounds like creating a fpga or asic would be more work than extracting the aes gid key from the a5 chip

21:49 <scatterp> i was just thinking maybe there was a doorway due to the size of the readme file and having the sha1

21:54 <efc> ever heard of the Pigeonhole Principle?

21:54 <scatterp> yes

21:54 <scatterp> birthday stuff

21:54 <PovAddictW> birthday doesn't apply here

21:55 <scatterp> looking for collisions right?

21:55 <PovAddictW> one thing is finding two files with the same hash, another is to find a file with a *given* hash

21:56 <scatterp> yeah ill just have to extract that key some how it seems

21:56 <scatterp> another issue is identifying the type of encryption used

21:58 <scatterp> some how r0bf0rdsn0w-r0bf0rdsn0w-r0bf0rdsn0w-r0bf0rdsn0w!! becomes E6A9B03D9670523CFA8849A23A28722E 3c083980452574871418763c6e0ee2cf6f0a952652791ca74d3206d6e5b15368

21:58 <efc> how long is an AES key?

21:59 <CoderForLife> GN cryptologists

21:59 <efc> Night WallBuilderForLife

22:00 <CoderForLife> ha!

22:00 <efc> :)

22:00 <efc> whats an IV? Intermediate Value?

22:01 <PovAddictW> initial value I think

22:01 <efc> ah

22:01 <PovAddictW> initialization vector!

22:01 <scatterp> salt so some type of hashing maybe its sha1 ?

22:03 <scatterp> sorry my knowledge is some what patchy in encryption :/

22:03 <scatterp> gn CoderForLife

22:04 <scatterp> oh if i encrypt with a key do i get the salt back ?

22:08 <scatterp> to have a key that long maybe its rsa 768 ?

22:12 *** efc has quit IRC

22:13 *** efc has joined #boinc

22:23 <efc> 768 would be bad news for brute forcing..

22:25 <scatterp> yeah but there are some attacks for it

22:25 <scatterp> i think ill sleep on it

22:25 <scatterp> its 3:30am here

22:26 <scatterp> thanks for all the help gn guys

22:27 <efc> &nn

22:27 <Romulus> Live long and crunch!

22:27 <efc> I haven't seen xcamel on the strikestar network in a while.

22:37 *** MiniFridge has quit IRC

23:48 *** yoyo[RKN] has quit IRC

Generated by 2.4 by Marius Gedminas - find it at!