[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABob6iqTOBqdTN2BhjU14E5RfuR5fhC5CJPD8W=GTh-WOn-qiA@mail.gmail.com>
Date: Tue, 10 Jul 2012 23:35:16 +0200
From: Lukas Odzioba <lukas.odzioba@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: Cracking GNOME Keyrings [the easy way]
2012/7/9 Dhiru Kholia <dhiru.kholia@...il.com>:
> Hi,
>
> The attached trivial program cracks GNOME Keyrings at a rate of ~300
> tries/second. I am not sure if the library calls used in it are
> thread-safe. This program requires gnome-keyring-daemon to be running.
> I am not sure if we can include something like this in even jumbo ;).
> Hence I am thinking host it as a separate project on github. Thoughts?
>
> Cracking GNOME Keyrings [the hard way] by implementing underlying
> crypto is TODO.
>
> One curious observation, do you find something weird with the following stats?
>
> $ time ./gkcrack &> /dev/null # looping 1000 times
>
> real 0m3.459s
> user 0m0.054s
> sys 0m0.281s
>
> I was expecting user value to be high but it isn't. Is it due to
> actual work being done in another process (gnome-keyring-daemon)?
It looks like not this process is doing the job.
I am a bit confused about what gkcrack does, could you say something
more about it?
Have you looked into gnome-keyring-deamon source?
If yes, have you found something that can tell us what kind of crypto
alg is under the hood?
Lukas
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
