From owner-freebsd-current Mon Jul 17 18:52:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 4CAA737B7D7 for ; Mon, 17 Jul 2000 18:52:38 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id VAA04807; Mon, 17 Jul 2000 21:52:22 -0400 (EDT) (envelope-from wollman) Date: Mon, 17 Jul 2000 21:52:22 -0400 (EDT) From: Garrett Wollman Message-Id: <200007180152.VAA04807@khavrinen.lcs.mit.edu> To: "Leif Neland" Cc: Subject: cer/b7b/pfc -> pem In-Reply-To: <005f01bff04d$3d39a800$0e00a8c0@neland.dk> References: <005f01bff04d$3d39a800$0e00a8c0@neland.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I can export the key as a .cer, .p7b or .pfx, but openssl seems to want it > in .pem format. Of course, you haven't really told us what the format of these things is, so it's difficult to say. The ``standard'' export format is something called PKCS#12. You can use `openssl pkcs12' with various options to extract the key and certificate from this sort of format. It will prompt you for the password you specified when exporting. If you export in any other format, it is highly unlikely to contain your private key, which is required to make use of the certificate. Those other formats are normally used when you want to distribute your public key to someone or as a part of something other than a mail message. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message