Will consider your input
On Friday, October 9, 2020 at 2:25:22 PM UTC+5:30 m8il...@gmail.com wrote:
> On 2020-10-09 09:01, Kevin Chadwick wrote:
> > However, there is even a possibility that a quantum computer with
> > enough qubits to defeat p256 is never built or a traditionally binary
> compu
On 2020-10-09 09:01, Kevin Chadwick wrote:
> However, there is even a possibility that a quantum computer with
> enough qubits to defeat p256 is never built or a traditionally binary computer
> succeeds first in many years time.
It is also worth noting that the amount of money required to build a
On 2020-10-08 16:22, Marcin Romaszewicz wrote:
> Practically, there isn't much reason today to use the P384 and P521 curves.
> The
> security provided by P256 is very good, not known to be crackable today, and
> it's a widely supported curve. P384 is reasonably well supported, but not as
> widely,
Thank you Marcin for your response.
It is really helpful.
On Thu, 8 Oct 2020, 21:52 Marcin Romaszewicz, wrote:
> Yes, in my experience, the C SSL libraries are much faster than Go's
> implementation on curves P384 and P521, however, Go's tuned implementation
> of P256 curves is comparable to Op
Yes, in my experience, the C SSL libraries are much faster than Go's
implementation on curves P384 and P521, however, Go's tuned implementation
of P256 curves is comparable to OpenSSL performance (
https://golang.org/src/crypto/elliptic/). If you look in the directory I
linked, you'll see that it h
Thanks for the detailed explanation for your issue.
Thanks for the pointers for the library. Just a quick question, do you
think calling C library from Go can give great results for 521 curve.
On Thu, 8 Oct 2020, 21:03 Marcin Romaszewicz, wrote:
> My issue was slightly different than yours, in
My issue was slightly different than yours, in that I was burning way too
much CPU verifying 384 bit client certificates for TLS. The solution was to
have nginx do TLS termination, and proxy decrypted traffic to my Go server,
rather than doing TLS termination in Go.
The first place I would start l
Hey Marcin
Can you give me the pointer on C library and if can be used in Cgo .
Thanks
On Wed, 7 Oct 2020, 22:27 Shobhit Srivastava, wrote:
> Yeah the inclination is towards 512 curve only so need to optimise it.
>
> Will check out the C library. Thanks
>
>
>
> On Wed, 7 Oct 2020, 22:22 Marcin
Yeah the inclination is towards 512 curve only so need to optimise it.
Will check out the C library. Thanks
On Wed, 7 Oct 2020, 22:22 Marcin Romaszewicz, wrote:
> secp256r1 has been hand optimized for performance, the others haven't.
>
> If performance there matters to you, it's actually fast
secp256r1 has been hand optimized for performance, the others haven't.
If performance there matters to you, it's actually faster to call out to C
libraries to verify 384 and 512 bit curves.
On Wed, Oct 7, 2020 at 9:27 AM Shobhit Srivastava
wrote:
> Hi All
>
> I have tried to do the performance
Hi All
I have tried to do the performance analysis for different curve in golang
and got below output:
for secp256r1 I got 28000 Signature verified per second
for secp384r1 I got 1600 Signature verified per second
for secp521r1 I got 700 Signature verified per second
Is there something I
11 matches
Mail list logo
