Thanks for your answer.
Opps sorry, wrong list... i just subscribed to users and will resubmit there.
anyway, just in case , since im posting here again anyway, heres what i did
with xxd , and some more infos about the key. if anyone has any ideas how i
could get this to work i would greatly appreciate any hints. offlist, if you
prefer, as this is dev , i know... so, ignore if you like. this was my last
post here;)
my private key looks *something* like this (no need to delete, this is not a
real key here):
064DA77A8E7CFA65EDCE641
(but much longer....)
just one long string of hex values.
in xxd, i cant seem to find the option i need. i pasted the output of -help for
xxd below. I tried:
xxd -r infile outfile
but had to learn that a hexdump is not quite what my key is in..
i can do a binary digit dumb, and then -r that, but that doesnt make sense,
does it? :S
too many trees to see the forest for me here atm.
thanks,
Alois
xxd [options] [infile [outfile]]
or
xxd -r [-s [-]offset] [-c cols] [-ps] [infile [outfile]]
Options:
-a toggle autoskip: A single '*' replaces nul-lines. Default off.
-b binary digit dump (incompatible with -p,-i,-r). Default hex.
-c cols format <cols> octets per line. Default 16 (-i: 12, -ps: 30).
-E show characters in EBCDIC. Default ASCII.
-g number of octets per group in normal output. Default 2.
-h print this summary.
-i output in C include file style.
-l len stop after <len> octets.
-ps output in postscript plain hexdump style.
-r reverse operation: convert (or patch) hexdump into binary.
-r -s off revert with <off> added to file positions found in hexdump.
-s [+][-]seek start at <seek> bytes abs. (or +: rel.) infile offset.
-u use upper case hex letters.
-------- Original-Nachricht --------
Datum: Wed, 2 May 2007 13:31:30 -0700
Von: "David Schwartz" <[EMAIL PROTECTED]>
An: [email protected], [EMAIL PROTECTED]
Betreff: RE: Private Key problem
>
> > Im tearing my hair out here with what is probably a stupid problem.
> > I'm new to openssl , rsa, etc... , so bear with me please:)
> [snip]
> > Ok then, i know the key needs to be in PEM format, for PHP /
> > openssl... but, i can't get it recognized at all by openssl.
> [snip]
> > Ok, so i guess i do somehow have to convert that hex data into
> > binary, right?
> > i tried to do that with xxd , but failed.
> > how can i do that?
> > Sorry if this is a stupid question, but i seem unable to find
> > infos on this with google, for whatever reason...
>
> Describing a result as "failed" is not helpful. You really give us nothing
> to go on. How about some example files? How about what the input and
> output
> was to 'xxd' and what parameters you passed to it? Something.
>
> Also, what does this have to do with OpenSSL development? Perhaps you
> wanted
> the users mailing list?
>
> DS
>
>
> ______________________________________________________________________
> OpenSSL Project http://www.openssl.org
> Development Mailing List [email protected]
> Automated List Manager [EMAIL PROTECTED]
--
"Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [EMAIL PROTECTED]
