Re: RSA maximum key size

From: Rob Teixeira (RobTeixeira_at_@msn.com)
Date: 11/08/04

  • Next message: Kal: "Encrypted connection string in registry"
    Date: Sun, 7 Nov 2004 22:39:11 -0500
    
    

    RSA (the company) recommends 1024 or 2048-bit keys. 512-bit keys appear to
    be rather vulnerable with today's computing horsepower.
    Windows will default to 1024-bit keys if the Strong or Enhanced Crypto API
    providers are used. User certificates usually come with a 1024-bit key and a
    CA certificate usually has 4096-bit keys.

    One thing to note is that the larger the key, the slower the cipher,
    particularly with regards to generating the key. In that sense, a 16,384-bit
    key is almost unusable to begin with right now.

    -Rob Teixeira

    "Novice" <6tc1ATqlinkDOTqueensuDOTca> wrote in message
    news:B0B95EDF-4EB6-4314-AD59-404818E0F28C@microsoft.com...
    > Hey all, I have a question about what key lengths are supported by RSA
    > encryption in .Net (through RSACryptoServiceProvider). I have checked
    using
    > code - something like this:
    > RSACryptoServiceProvider RSA = new RSACryptoServiceProvider();
    > RSA.LegalKeySize[0].MaxKeySize
    >
    > and I found that it supports 16384 bit keys.
    >
    > Isn't the current standard for a "good" key length (difficult to deduce
    > through cryptoanalysis) - 1024 or 2048 bit encryption?
    >
    > Lastly, I have read that though the officially supported key length is
    16384
    > bits - the modulus that RSA will end up using is inappropriate. What I'm
    > asking is whether the .Net libraries are actually capable of supporting
    the
    > maximum key length size that they indicate.
    >
    > Thanks,
    > Novice


  • Next message: Kal: "Encrypted connection string in registry"

    Relevant Pages

    • RSA maximum key size
      ... I have a question about what key lengths are supported by RSA ... encryption in .Net. ... RSACryptoServiceProvider RSA = new RSACryptoServiceProvider; ... asking is whether the .Net libraries are actually capable of supporting the ...
      (microsoft.public.dotnet.security)
    • Re: 0300 Number!
      ... the calls come from networks other than BT but have to transit the BT network), ... the Xp/min is actually a minus ... ... So some providers will lose money by supporting 03 numbers! ...
      (uk.telecom)

  • Quantcast