Re: Re[2]: encryption algs
From: Kevin Conaway (kevin.conaway_at_gmail.com)
Date: 01/31/05
- Previous message: LordInfidel: "RE: RPC over HTTP security"
- In reply to: BoI base: "Re[2]: encryption algs"
- Next in thread: miguel.dilaj_at_pharma.novartis.com: "Re:encryption algs"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 31 Jan 2005 09:06:52 -0500 To: security-basics@securityfocus.com
If you look at the manpage for crypt():
http://www.rt.com/man/crypt.3.html
It shows that crypt() takes the lower 7 bits of the plaintext to
produce a 56bit key. This produces the "13-letters state" as you put
it. So as far as taking the output from a normal implementation of
DES and transforming it an output like that of crypt(), I'm not sure
its possible. I think you would need to have the plaintext.
Is this what you were looking for?
Kevin
On Fri, 28 Jan 2005 13:41:33 +0300, BoI base <postbase@mail.ru> wrote:
> Hello Ghaith,
> Friday, January 28, 2005, 12:42:53 PM, you wrote:
>
> You said, that MD5 has 2 different implementations: NT-MD5 and UNIX-MD5?
> Maybe there is no difference in 2 algorithms before fixed point
> (before output)?
>
> GN> Sorry, I didn't get your second question.
>
> By FIPS-46-3 we have, that result of DES function is 64-bit array. But
> using unix crypt(3) function (implementation of the same DES algorithm) has
> 13*8=104-bit result (for example, hash: VF6NabIjwyOI2). I have code
> for 64-bit DES result. But I need code for receiving 104-bit DES
> result (unix crypt(3)).
>
>
> --
> Best regards, Xanders mailto:postbase@mail.ru
>
>
- Previous message: LordInfidel: "RE: RPC over HTTP security"
- In reply to: BoI base: "Re[2]: encryption algs"
- Next in thread: miguel.dilaj_at_pharma.novartis.com: "Re:encryption algs"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
