Kurt Quackenbush wrote: > There are various formats that you can save a certificate in. You want a > Base64-encoded X.509 format, often with extension .CER (I mention all those > terms in case one of them rings an inkling). If wherever you're exporting it > from offers options, try 'em all, until you see the -----BEGIN CERTIFICATE > stuff. >As Phil states, there are indeed several formats for certificate files, and I >get them confused myself. In any case, the file mentioned in the Flash is NOT >the format containing human readable text -BEGIN CERTIFICATE-. Regardless, >the format of the file is usable, as directed in the Flash.
Ok, let me jump in: First thing first. Forget for now about the file name suffixes like .pem , .cer , .crt , etc. Use something like NotePad to look at the file containing the Certificate. If you see the Encoding Header and Footer lines and the max length of the 'gibberish' line(s) are 64 characters, then it is Base64 encoded X.509 format. Just a quick copy/paste or FTP with ASCII is needed. If you see 'gibberish' or just random unreadable contents [1] with NO Header and Footer lines, then you need to do Binary FTP to a dataset with LRECL=256, DSORG=PS, RECFM=VB. I like to pre-allocate it before any FTP. Oh, let BLKSIZE be 27998 or just let it be default according to your SMS setup, not BLKSIZE=27988 as written by Phil. Encoding Header "-----BEGIN CERTIFICATE-----" Encoding Footer "-----END CERTIFICATE-----" [1] - for DigiCert Certificates, in this format you could see 'DigiCert Global Root CA' and www.digicert.com embedded in the gibberish text. With Binary FTP, these readable parts will disappear after transfer at the destination dataset. HTH! Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
