On 25-08-2013 13:38, Alexander Klimov wrote:
> There was a ECC program from the previous century that worked as you
> described: the private key was derived solely from the user password.
> Unfortunately, I cannot recall its name (and I suspect it already
> vanished from the net since it was not
On Sun, Aug 25, 2013 at 08:13:51AM -0400, Matthew Orgass wrote:
> On 2013-08-25 alser...@inbox.ru wrote:
> >On Sat, 24 Aug 2013, Krisztián Pintér wrote:
> >>has anybody done something like that already? does it have a name?
> >
> >There was a ECC program from the previous century that worked as you
Bitcoin Brainwallet software creates ECDSA keys that you can use for
multiple purposes, not only for Bitcoin.
A link to Phidelius, which was previously mentioned:
http://dankaminsky.com/2012/01/03/phidelius/
---
I would like to see some standardized hierarchial deterministic scheme
to generate v
On 2013-08-25 alser...@inbox.ru wrote:
On Sat, 24 Aug 2013, Krisztián Pintér wrote:
has anybody done something like that already? does it have a name?
There was a ECC program from the previous century that worked as you
described: the private key was derived solely from the user password.
Se
On Sat, 24 Aug 2013, Krisztián Pintér wrote:
> has anybody done something like that already? does it have a name?
There was a ECC program from the previous century that worked as you
described: the private key was derived solely from the user password.
Unfortunately, I cannot recall its name (an
On 2013-08-25 7:58 AM, James A. Donald wrote:
On 2013-08-25 2:30 AM, � wrote:
hi list,
i had an epiphany today, and i wonder if such a thing already exists
or not.
so the usual thing is to create a key pair, store the private key
encripted with a password. we automatically get a two factor
On 2013-08-25 2:30 AM, � wrote:
hi list,
i had an epiphany today, and i wonder if such a thing already exists or not.
so the usual thing is to create a key pair, store the private key encripted with a password. we
automatically get a two factor authentication, we have a "know" and a "have".
o
aha, i'm not that original after all. my attention was called to Dan Kaminsky's
"Phidelius" too.
> It's very similar (as Greg Rose noted) to IBE, and thus pretty much what I
> did in:
> http://middleware.internet2.edu/pki05/proceedings/callas-conventional_ibe.pdf
_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I like it, myself.
It's very similar (as Greg Rose noted) to IBE, and thus pretty much what I did
in:
http://middleware.internet2.edu/pki05/proceedings/callas-conventional_ibe.pdf
Jon
-BEGIN PGP SIGNATURE-
Version: PGP Universal 3
On 24 August 2013 19:55, Krisztián Pintér wrote:
>
> > Can it not? A distributed store for salts seems possible...
>
> but then distributed keyring is also possible, is it not?
>
Yes. Or at least cloud storage for secrets.
___
cryptography mailing list
On August 24, 2013 at 1:41:27 PM, Ben Laurie (b...@links.org) wrote:
On 24 August 2013 19:14, Krisztián Pintér wrote:
> 1. In your system the KDF for creating the seed to PRNG can’t be
> salted.
nope, it can't be.
Can it not? A distributed store for salts seems possible...
OK, “can’t” was too
> Can it not? A distributed store for salts seems possible...
but then distributed keyring is also possible, is it not?
___
cryptography mailing list
cryptography@randombit.net
http://lists.randombit.net/mailman/listinfo/cryptography
On 24 August 2013 19:14, Krisztián Pintér wrote:
>
> adjisten :)
>
> > 1. In your system the KDF for creating the seed to PRNG can’t be
> > salted.
>
> nope, it can't be.
>
Can it not? A distributed store for salts seems possible...
___
cryptography ma
adjisten :)
> 1. In your system the KDF for creating the seed to PRNG can’t be
> salted.
nope, it can't be.
> And so two people with the same password will end up with
> the same key pair.
for this reason, and others, a really strong key phrase is needed for that
reason. this is definitely a
Szervusz Kristián.
On August 24, 2013 at 11:29:57 AM, Krisztián Pintér (pinte...@gmail.com) wrote:
so the usual thing is to create a key pair, store the private key encripted
with a password. we automatically get a two factor authentication, we have a
"know" and a "have".
Yep. We need both the
On Aug 24, 2013, at 9:30 , Krisztián Pintér wrote:
>
> hi list,
>
> i had an epiphany today, and i wonder if such a thing already exists or not.
>
> so the usual thing is to create a key pair, store the private key encripted
> with a password. we automatically get a two factor authentication
On Aug 24, 2013, at 11:30 AM, Krisztián Pintér wrote:
> we can do that. how about this? stretch the password with some KDF, derive a
> seed to a PRNG, and use the PRNG to create the the key pair. if the algorithm
> is fixed, it will end up with the same keypair every time. voila, no-keyring
>
hi list,
i had an epiphany today, and i wonder if such a thing already exists or not.
so the usual thing is to create a key pair, store the private key encripted
with a password. we automatically get a two factor authentication, we have a
"know" and a "have". okay, but what if we don't want th
18 matches
Mail list logo
