Dr. Stephen Henson wrote:
On Mon, Nov 06, 2006, Andrew White wrote:
Maybe I just missed this, but how do you set some OID = some string
which could contain newlines?
I was just hex encoding a string which worked fine until newlines were
added (DER:(hex encoded env var), and then weird stuff happened. Do I
need to use ASN.1 string types? If so, how?
You need to say what you are trying to do, how you've tried to do it and what
actually happened.
That is what did you put in the configuration file and what do you mean by
"weird stuff"?
Steve.
--
Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage
OpenSSL project core developer and freelance consultant.
Funding needed! Details on homepage.
Homepage: http://www.drh-consultancy.demon.co.uk
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
Ah I see. Long story short I just want to have an OID populated by some
string which contains newlines. In the past I was just DER encoding a
string ie...
1.2.3.4=DER:${ENV::CUSTOM_DATA_DER}
Where CUSTOM_DATA_DER was created via...
export CUSTOM_DATA_DER = `echo -n "$CUSTOM_DATA" | hexdump -v -e '1/1
"%x"'`
This works fine as long as no newlines are around, but as soon as
newlines are added some certs are unsignable and a text dump of a cert
shows the 1.2.3.4 OID with some random data.
Sorry for the lack of details. I am sure there is a better way to add
something as simple as a string into a cert, but I haven't found a good
way as of yet.
Thanks,
Andrew
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
