You mean that I should write down my custom information in
openssl.cnf, and then load the custom information to extension of
proxy by openssl command, isn't it?
yes
If I want to do this job by standard openssl API, how to accomplish this/
A rough sketch would be:
// set up context
X509V3_s
Hi all,
I´m adapting a PKCS#11 module for using it on Ubuntu Feisty. I had it
perfectly working on Ubuntu Dapper, but when I compile it (using g++
4.1.2-0ubuntu4 and Kdevelop 3.5.6) and compiler reaches to the call
EVP_idea_cbc(), it shows me this error: 'EVP_idea_cbc' was not declared in
this sc
> I´m adapting a PKCS#11 module for using it on Ubuntu Feisty. I had it
> perfectly working on Ubuntu Dapper, but when I compile it (using g++
> 4.1.2-0ubuntu4 and Kdevelop 3.5.6) and compiler reaches to the call
> EVP_idea_cbc(), it shows me this error: 'EVP_idea_cbc' was not declared in
> this s
Hi,
I'm trying to use BIO to do base64 encoding.
but here's the problem
in the sample code below,
if I comment out like 1 (which uses mem bio) and uncomment 2 (one
that uses file bio)
everything works and the encoded string is written the std out.
Which is good as it tells me that thi
But what i really want is the encoded string in a char buffer.
And so i comment out 2 and use 1 instead. As its suppose to write
the encoded string into a buffer,
but the problem here is pEncBuf is empty even though bytesWritten says it
wrote 4 bytes.
And i can't explain why it won'
Thanks for pointing it out Jim, actually that was a error in creating the
sample code for the post
the actual code looks more like the one show below
int main(int argc, char *argv[])
{
char ch[] = "adsf";
char enc[128];
int encSize= 128;
b64encode(ch, strlen(ch), enc, &encSize);
printf("[%s]\n
And yeah even with the correct size it still doesn't work.
The BIO_new_mem_buf creates a read-only buffer.
If you want to write to memory use
bio = BIO_new(BIO_s_mem());
and use BIO_get_mem_ptr to get a pointer to the buffer.
Jim
that was indeed the problem, a read only buffer. Thanks Jim !
From: Jim Fox <[EMAIL PROTECTED]>
Reply-To: openssl-users@openssl.org
To: openssl-users@openssl.org
Subject: Re: Base64 encoding with BIO_new_mem_buf
Date: Thu, 12 Jul 2007 11:21:28 -0700 (PDT)
And yeah even with the correct size
Before continuing with further programming, I wanted to know if I got
this certificate signing going well. Thanks for any feedback, it will
be deeply appreciated.
I created a self signed certificate and used s_server to create a
secured server on one machine (zzserver.mynet.com) and secured clie
> If I want to do this job by standard openssl API, how to accomplish this/
A rough sketch would be:
// set up context
X509V3_set_ctx(...)
X509_EXTENSION *ext;
// read ext information
ext = X509V3_EXT_conf(...)
// add extension
if (!X509_add_ext(cert, ext, ...) {
error output
}
You need to
Thanks. But it seems that I must add my custom information as
extension when the certificate is being created. Can I add to the
certificate which has already been created ?
No. Once the certificate has been signed it's done. If you want
to change anything you have to resign (recreate) it.
Ji
hi...
i'm a noob in openssl.. my employee asked me to edit our c++ cert issuer
engine developed using openssl. currently the cert generated will be valid
based on the time we generate it. for example, if i generate a cert at 13
july 2007 1:30pm and set its validity for 5 days, the cert will be va
On Jul 12, 2007, at 9:29 PM, imin macho wrote:
hi...
i'm a noob in openssl.. my employee asked me to edit our c++ cert
issuer engine developed using openssl. currently the cert generated
will be valid based on the time we generate it. for example, if i
generate a cert at 13 july 2007 1:3
No. Once the certificate has been signed it's done. If you want
to change anything you have to resign (recreate) it.
OK, then how to fetch the custom information? Is it same as the sketch
but using X509_get_ext()?
__
OpenSSL
14 matches
Mail list logo
