There is the "x509" tool which is part of SSLeay (or OpenSSL).
-Jeff
Sanket Naik wrote:
> hi
>
> can someone point me to a tool (preferably unix command line) for
> conversion between different X.509 certificate encodings, DER, base64,
>
>
> thanks
> sanket
"Steven M. Bellovin" wrote:
> Purely procedurally, if you tried to get it published as an RFC it
> would probably be bounced by the IESG -- there's a policy against RFCs
> that are or appear to be end-runs around a working group. If something
> is in a WG's area, it's up to them to publish it.
Actually for the TLS crowd, going to DES is a step up. I presume that the
TLS WG is planning to use DES to replace the RC4 40 bit cipher that was used
for export compliance. Normally we would not profile a weak cipher for use
in export applications. We made an exception for TLS/SSL because it was
Ben Laurie wrote:
> OpenSSL has them disabled by default. But I am torn on this question:
> these new ciphersuites give greater strength than existing ones when
> interopping with export stuff. Is it sensible to refuse to add stronger
> ciphersuites? If it isn't, because they are crap, should we
I suspect that the reason they would want Carnivore as opposed to
looking at spool files is that it is less invasive then looking at spool
files, isn't dependent on the technology choices made by the ISP and
finally its operation is beyond the ISP's examination.
"Here just connect this to your ne
