Thanks for your answers.
We need to calculate signature for the bit size 192 as well. as i am able
to see the P-192 in NistNamedCurves.cs [namespace
Org.BouncyCastle.Asn1.Nist],i think P-192 is supported in bouncy castle. is
it right?
DefineCurve("P-521",
SecObjectIdentifiers.SecP521r1);
DefineCurve("P-384", SecObjectIdentifiers.SecP384r1);
DefineCurve("P-256", SecObjectIdentifiers.SecP256r1);
DefineCurve("P-224", SecObjectIdentifiers.SecP224r1);
DefineCurve("P-192", SecObjectIdentifiers.SecP192r1);
Best regards,
Mohan
On Fri, Apr 24, 2015 at 4:50 PM, Edward Ned Harvey (bouncycastle) <
bouncycas...@nedharvey.com> wrote:
> > From: Mohan Kumar [mailto:mohan...@gmail.com]
> > Sent: Friday, April 24, 2015 1:40 AM
> >
> > As per wiki
> > page, http://www.bouncycastle.org/wiki/pages/viewpage.action?pageId=36
> > 2269, NIST (aliases for SEC curves) supports only P-224, P-256,
> P-384,P-521. i
> > couldn't find P-192. whether bouncy castle supports P-192 or not?
> >
> > thanks in advance.
>
> I don't have the answer to your question, but in EC, the cryptographic
> strength is about half the number of bits, so 192 would have a
> cryptographic strength of 96, which is not considered strong enough in the
> present world. 224 would have the strength of 112, which is about the same
> as RSA 2048, which is still good enough for many purposes now, but not much
> longer. The recommended sizes to use are 256 and larger, which correspond
> to cryptographic strength of 128 or larger, roughly equivalent to RSA 3072
> or 4096.
>
> Please note, 521 is not a type-o.
>
