Likes Likes:  0
Resultaten 31 tot 32 van de 32
Pagina 3 van de 3 Eerste 1 2 3
Geen

Onderwerp: SHA-1 broken

  1. #31
    Peter J. Holzer
    SHA-1 broken
    Gast
    n/a Berichten
    Berichten zijn liked



    Thread Starter

    Re: SHA-1 broken


    --dDRMvlgZJXvWKvBx
    Content-Type: text/plain; charset=us-ascii
    Content-Disposition: inline
    Content-Transfer-Encoding: quoted-printable

    On 2005-02-19 10:58:23 +0100, exon wrote:
    > Michael Silk wrote:
    > > But wouldn't it render a login-based hashing system resistant to the
    > >current hashing problems if it is implemented something like:
    > >
    > > --
    > > result =3D hashFunc1( input + hashFunc1(input) + salt )
    > > //
    > > // instead of
    > > //
    > > result =3D hashFunc1( input + salt )
    > > --
    > >

    >=20
    > I assume you mean hashFUnc2 inside the parentheses (I'll refer to it as=

    =20
    > that anyway, for clarity).


    I don't think so. Hashing functions for login (e.g., the BSD/Linux style
    MD5-hash) usually call the same hashing function multiple times.


    > No it won't, because if hashFunc2 has collisions the resulting output=20
    > will collide in hashFunc1 as well.


    No, it wont. (input1 + hashFunc2(input1)) and (input2 +
    hashFunc2(input2)) are still different strings, even if
    hashFunc2(input1) and hashFunc2(input2) collide, so you have to find an
    input which collides in both hashes (well, not quite), which should be
    harder to find than one which collides in only one.


    > If you didn't mean hashFunc2 inside the parentheses, you have actually=20
    > lessened the collision resistance, owing to the possibility that two=20
    > different outputs might collide as well.


    No, because again, (input1 + hashFunc1(input1)) and (input2 +
    hashFunc1(input2)) are two different strings, even if hashFunc1(input1)
    and hashFunc1(input2) collide, and they must collide as well.=20

    hp

    --=20
    _ | Peter J. Holzer | If the code is old but the problem is new
    |_|_) | Sysadmin WSR / LUGA | then the code probably isn't the problem.
    | | | hjp@wsr.ac.at |
    __/ | http://www.hjp.at/ | -- Tim Bunce on dbi-users, 2004-11-05

    --dDRMvlgZJXvWKvBx
    Content-Type: application/pgp-signature
    Content-Disposition: inline

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.2.4 (GNU/Linux)

    iQDQAwUBQhjftVLjemazOuKpAQEyAgXTBYzDdnqsZ/1L6KgU6J+t7NYkYI5biREu
    gH9arOFQ3LVbofLM/i5NTHYMvqGNQgRohPTSmJwVi3ohEy7FCWwomkPfr/Nh5+I1
    NqKbS8IfzBT5sVB9v3AqmK4ddub9f0glhD8y2BRae5PJeo3ucR Jxrr8pMcIEecaH
    DNvAl87vHH8gbAQKhI4Mb0Nz5H78qUBvwB70PoTGvpq99w/cDlceTPuC4hK+CrpF
    F9qmx3nUUxKI2g5bEQJv+StqVQ==
    =Htij
    -----END PGP SIGNATURE-----

    --dDRMvlgZJXvWKvBx--

  2. #32
    Pavel Machek
    SHA-1 broken
    Gast
    n/a Berichten
    Berichten zijn liked



    Thread Starter

    Re: SHA-1 broken

    Hi!

    > In much the same way if the original text was 'I owe you 1 million dollars' and the collision text was 'sdf86*&6989h,mni lkj99j' its not significant.
    >


    See the demos I posted to bjgtraq some time ago... It had pretty reasonable
    horse-selling texts with same md5 sum.
    --
    64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms


Pagina 3 van de 3 Eerste 1 2 3

Webhostingtalk.nl

Contact

  • Rokin 113-115
  • 1012 KP, Amsterdam
  • Nederland
  • Contact
© Copyright 2001-2026 Webhostingtalk.nl.
Web Statistics