Re: Secure website - explanation required.

From: GriffithsJ (GriffithsJ_520_at_hotmail.com)
Date: 03/03/04 

Date: Wed, 3 Mar 2004 12:42:32 -0000

Think I've worked out the solution....

VeriSign offer a "Pro" and a "normal" package. The former requires 1024 bit
keys, the latter accepts 1024 and 512 bit keys. The normal package will
allow 128 bit encryption with browsers that allow this (most do nowadays in
the UK).

So, I need to export a 1024 bit private/public key certificate from IIS, get
the far cheaper package from VeriSign (the non-Pro version) and will then be
offering 128-bit session key communication with all my customers, providing
they don't use the crippled 40-bit version of the browser.

Griff

Relevant Pages

  • Re: Keyboard test page updated
    ... Keyboard handling is one of the hardest cross-browser issues. ... Looks good to me at this point, having tested numerous browsers ... Control or Meta keys). ... keypress events on keydown after sniffing out certain browsers (e.g. ...
    (comp.lang.javascript)
  • Re: Congrats to jquery
    ... to me that among the major browsers of the time all but Chrome ... returned the values for objects (not including arrays) in a consistent ... order keys so they can be used effectively. ... depending upon underspecified behavior. ...
    (comp.lang.javascript)
  • Re: Disappearing session variables
    ... react to different browsers in any way? ... sheet, but that's it. ... I've googled this issue a lot, and it seems to be a common problem, ... I added a bit of debugging code to track the _SESSION keys at various ...
    (comp.lang.php)
  • Re: Secure website - explanation required.
    ... keys, the latter accepts 1024 and 512 bit keys. ... The normal package will ... allow 128 bit encryption with browsers that allow this (most do nowadays in ...
    (microsoft.public.inetserver.iis)
  • Re: Secure website - explanation required.
    ... keys, the latter accepts 1024 and 512 bit keys. ... The normal package will ... allow 128 bit encryption with browsers that allow this (most do nowadays in ...
    (microsoft.public.inetserver.misc)