Re: DESCryptoServiceProvider weak and semi-weak keys [ADDITION]
From: I.Charitopoulos (i.charitopoulos_at_mellon.com.gr)
Date: 08/28/03
- Next message: John Hynes: "TrustFailure accessing web service from Smart Device application."
- Previous message: Mr.Tickle: "Re: Obfuscators"
- In reply to: Ivan Medvedev [MS]: "Re: DESCryptoServiceProvider weak and semi-weak keys [ADDITION]"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 28 Aug 2003 11:26:53 +0300
Thanx a lot for the info.
Unfortunately, much to my frustration, I can not use anything else.
And by the time the key gets to my hands, it's already too late to change
it...
"Ivan Medvedev [MS]" <ivanmed@online.microsoft.com> wrote in message
news:OVlgsrLbDHA.3768@tk2msftngp13.phx.gbl...
> You can call DES.IsWeakKey(byte[] key) yourself (it is a public static
> methnod) and see if your generated key is weak.
>
> The weak DES keys are:
> 0101010101010101
> fefefefefefefefe
> 1f1f1f1f0e0e0e0e
> e0e0e0e0f1f1f1f1
>
> Semiweak:
> 0x01fe01fe01fe01fe
> 0xfe01fe01fe01fe01
> 0x1fe01fe00ef10ef1
> 0xe01fe01ff10ef10e
> 0x01e001e001f101f1
> 0xe001e001f101f101
> 0x1ffe1ffe0efe0efe
> 0xfe1ffe1ffe0efe0e
> 0x011f011f010e010e
> 0x1f011f010e010e01
> 0xe0fee0fef1fef1fe
> 0xfee0fee0fef1fef1
>
> Although nowdays DES itself is weak. I recommend that you consider using a
> more strong algorithm such as TripleDES or Rijndael.
>
> --Ivan
> This posting is provided "AS IS" with no warranties, and confers no
rights.
- Next message: John Hynes: "TrustFailure accessing web service from Smart Device application."
- Previous message: Mr.Tickle: "Re: Obfuscators"
- In reply to: Ivan Medvedev [MS]: "Re: DESCryptoServiceProvider weak and semi-weak keys [ADDITION]"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
