On Mon, Dec 13, 2004 at 08:40:25AM -0500, Justin Miller wrote:
> Could one get the error messages I displayed if the proxy I'm trying
> to use doesn't support SSL (the connect method)?
I suppose you can "telnet your-proxy port-whatever" then type "CONNECT ..."
by hand to see if your proxy supports
The error messages I posted in my first message were from the 'openssl
s_client' command.
I suppose I might try setting up a web server/proxy on one of my home
machines, and trying it that way. Then I'd have direct access to the
proxy itself... something I could control.
On Tue, 14 Dec 2004 10:2
Pierre wrote:
Pierre wrote:
Richard Levitte - VMS Whacker wrote:
In message <[EMAIL PROTECTED]> on
Fri, 18 Apr 2003 02:42:22 +0200, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> said:
pierre42d> >In message
<[EMAIL PROTECTED]> on
pierre42d> Wed, 16 Apr 2003 07:23:56 +0200, "[EMAIL PROTECTED]"
pierre4
> To change the CSR require to parse it first, then form the new CSR with
> mentioned function.
> I want after parsing the CSR get the associative massive and than pass this
> massive to function that constructing new CSR.
> The format of argument-extensions must be corresponding in this two
>
Andrus wrote:
I have a RSA signature S (128 byte integer )
and modulus n (also 128 byte integer)
I need to calculate
( S**3 ) MOD n
All I need is to perform exponent ( S**3 ) and MOD operation on
128 byte integers.
I tried the following command:
openssl rsautl -in signature.bin -out decrsign.bin -
> The textual representation is a human readable version of the encoded
> extension: in general it isn't the same format as used in the config file
> (which is less readable and restricted in various ways).
>
> What are you trying to do?
The hole task is CA.
I have to implement some additional func
I have a RSA signature S (128 byte integer )
and modulus n (also 128 byte integer)
I need to calculate
( S**3 ) MOD n
All I need is to perform exponent ( S**3 ) and MOD operation on
128 byte integers.
I tried the following command:
openssl rsautl -in signature.bin -out decrsign.bin -inkey
RSA
On Mon, Dec 13, 2004, Zerg wrote:
> Hi all.
> I add the such extension to CSR with config file
> authorityInfoAccess = CA Issuers;email:[EMAIL PROTECTED]
> parsing my config file and
> using X509V3_EXT_REQ_add_confcall
>
> but when I have manualy parsed the request with such code
>
> ex
Hi all.
I add the such extension to CSR with config file
authorityInfoAccess = CA Issuers;email:[EMAIL PROTECTED]
parsing my config file and
using X509V3_EXT_REQ_add_confcall
but when I have manualy parsed the request with such code
ext - authorityInfoAccess extension
method = X509V3_EX
CRLs are signed by the CA certificate whose subsidiary certificates
are mentioned (or not) in the CRL. So a CRL is verified just like
any other signed document. You need any certificates in the chain,
which may or may not be supplied along with the CRL, see PKCS#7
format and/or the
openssl crl2pk
Hi all !
I don't anderstand how CRL are verified, someone can explain me a little
please.
CRL are not included in the certificate but a link to the CRL is
included in the certificate issuer, no ?
If a certificate contains a link, how the pointed CRL is verified ?
TIA
Frédéric.
__
I am indeed using the savardd patch (actually an update of the
sweeheng patch - your first link).
Could one get the error messages I displayed if the proxy I'm trying
to use doesn't support SSL (the connect method)?
-J
On Sun, 12 Dec 2004 15:50:00 +0800, Ng Pheng Siong <[EMAIL PROTECTED]> wrote:
Hello All,
I wanted to sign the an OCSP request and found out the function
OCSP_request_sign
What I see from its parameters is that it takes OCSP request object and
other parameters and sign the request, what I wanted to know that if I want
to sign the OCSP request from CAPI or some other toolki
13 matches
Mail list logo
