Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] Codenamed: MUD4TLD

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] Codenamed: MUD4TLD


Chronological Thread 
  • From: Amrit Panesar <apanesar AT 4195tech.com>
  • To: discuss AT lists.opennicproject.org
  • Subject: Re: [opennic-discuss] Codenamed: MUD4TLD
  • Date: Tue, 05 Jun 2012 21:05:58 -0700


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ah, yes 'de-hashed' is rather ambiguous.
You're correct, I was meaning to refer to a rainbow-table lockup or even
a brute-force against the hash itself.

Reversing an MD5 hash is nearly impossible as far as I know.

Thanks

- --Neo

On 6/5/2012 7:54 PM, mike wrote:
> Just a little clarification on terminology.
>
> I think when you are saying "de-hashed" you mean cracked by means of
> known-hash lookup table, or in other words comparing with a table of
> known hash values.
>
> I think it would be troublesome to actually 'de-hash' or in other
> words to actually reverse an md5 hash derived from an arbitrary and
> sufficiently complex clear text.
>
> --Mike
>
> On 06/05/2012 07:42 PM, Amrit Panesar wrote:
> > Mmm, I hope you add salt to your md5's. Normal md5's are easily
> > 'de-hashed'
>
> > Sent from my iPhone
>
Amrit Panesar
OpeNIC .Neo Administrator
[ @neo_desktop ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPztckAAoJEA/K84XwmW5ayC4H/2K9Ce5aadQVJ4Z/kiTk0MxS
up0+et8DyRcZDL6YsKnMi1K3PtcSWPBPH64Yd7mEcGvDYcE0f82Td/CpYKWedG95
3FHnyrQsGssWEmeqI/fVZ4GC1diJaS7iOqHGGR1wAtYCQhlPW67irvzgJ/na1bHh
pg9bdbNEvUECUgMiI0dPdr30yWDwQ+4L8Ktokm6irT6NVwcmvsa0+HPwCCfeD29w
gOt6K0CNHddzOG9lLn5fUc08Q1QAVeyuW9Uo061+ve2kMTaAbBXnv9hV701MEdVJ
CSBzUHa/4xtlAswSj34V+kCEjgKkSeh+432PKkOVGROhpLEOj3uVkB9H/xZJOKA=
=m7p3
-----END PGP SIGNATURE-----




Archive powered by MHonArc 2.6.19.

Top of Page