If you just need a test certificate for experimentation, check with Thawte:
theirs are free for application testing, and they don't trigger the
client-side 'Add a Certificate' dialog. Once you work out the bugs, try
Verisign or RSA for a production certificate.
- Roby
Sam Newman wrote:
> Tim Wrote:
>
> > If you are using passwords as the key, then it is unlikely that using
> > 1024 vs. 128 bit means a bit of difference. Unless you are requiring
> > that users use a 250 character password. The entropy of 6-10 digit
> > passwords is such that they are the weak point no matter how many bits
> > you use > 64, even if they are "good" passwords. If you worried, you're
> > worried about the wrong thing. Throwing more bits at it ain't going to
> > help.
>
> I really should read up on cryptography :-)
> ta for the info. Looking at verisign now for pircing - but thier
> certificates seem to cost anywhere from $200 to $2000. Just got to work out
> which ones we need....
>
> sam
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
