Re: hardware crypto and SSL?

From: Michael Sierchio (kudzu_at_tenebras.com)
Date: 10/22/03

  • Next message: Jason Stone: "Re: hardware crypto and SSL?" 
    Date: Wed, 22 Oct 2003 07:19:01 -0700
To: security@freebsd.org

    Bill Swingle wrote:

    > When you say that they help quite a bit, do you mean for http+SSL or
    > some other application?

    It depends on the traffic profile -- it significantly reduces the
    overhead of session establishment, because that's where pubkey
    calculations occur.

    > What I'm getting at is this: can anyone actually confirm that using
    > hardware crypto can increase http+SSL speeds? I've yet to find any
    > mention of it on the web.

    For a first estimate, look at the claims of the manufacturers ;-)
    (nCipher, Hifn, etc.)

    _______________________________________________
    freebsd-security@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-security
    To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org"

  • Next message: Jason Stone: "Re: hardware crypto and SSL?"

    Relevant Pages

    • Re: Function Vs Expressions
      ... But, also I listen to increase the speed, store calculations results. ... Normally, i don't store the calculations results to save memory, but I ... There is overhead associated with the use of a domain aggregate ... When used singularly in code or a form/report expression this overhead ...
      (microsoft.public.access.formscoding)
    • Re: GetRows
      ... Even with the overhead ... I was planning to do some benchmarks with the array idea ... array could possibly result in faster calculations than you'd get on ... Is the temp table slow from an end user's point of view? ...
      (comp.databases.ms-access)
    • Re: For-loop expression?
      ... >> code wiill immediately understand that the value is invariant. ... calculations I move them outside the loop. ... performance should be the least factor as the overhead is so ... It's more important to choose one coding style and stick to it for ...
      (microsoft.public.dotnet.languages.csharp)