On Fri, Sep 2, 2011 at 1:07 PM, Dr. Stephen Henson wrote:
Actually you can't. Applications generaally have their own way of setting the
cipherlist or just rely on the default value and don't allow it to be changed
at all.
Would this be worth adding environment variables for?
-Kyle H
Verif
On Mon September 5 2011, Michael B Allen wrote:
> On Sat, Sep 3, 2011 at 7:16 AM, Michael S. Zick wrote:
> > On Fri September 2 2011, Michael B Allen wrote:
> >> On Fri, Sep 2, 2011 at 4:07 PM, Dr. Stephen Henson
> >> wrote:
> >> > On Fri, Sep 02, 2011, Coda Highland wrote:
> >> >
> >> >> > Well
On Sat, Sep 3, 2011 at 7:16 AM, Michael S. Zick wrote:
> On Fri September 2 2011, Michael B Allen wrote:
>> On Fri, Sep 2, 2011 at 4:07 PM, Dr. Stephen Henson wrote:
>> > On Fri, Sep 02, 2011, Coda Highland wrote:
>> >
>> >> > Well I was hoping there was some kind of global configuration file
>>
Hi there
Am 02.09.2011 17:20, schrieb Eduardo Navarro:
The data for the timestamp is done on the signature, not the file. So
the TS command should reflect that.
which signature?? cmd "openssl ts -query -data tmp.pdf -out req.tsq"
gives no input for any signature
Greetz
As far as merging
silly me.. didn't notice the line in the server response of the second case:
verify depth is 1, must return a certificate
Using default temp DH parameters
ACCEPT
SSL_accept:before/accept initialization
SSL_accept:SSLv3 read client hello A
SSL_accept:SSLv3 write server hello A
SSL_accept:SSLv3 wri
Hi,
There must be something wrong with my assumptions or theory while I can get
connected openssl client and server with different certs.
What I do is:
create CA:
openssl genrsa -out ca_key.pem 1024
openssl req -config openssl.cnf -new -x509 -key ca_key.pem -out
ca.crt
create
