make certificate TYPE, CRT, KEY
I'm looking through the HISTORY file at the part where make certificate has been expanded to use four TYPEs -- dummy, test, custom, and official. make certificate TYPE=? CRT=/your/path/to/your.crt KEY=/your/path/to/your.key I'm confused (sorry, but I am). My questions are several: 1) CRT [and KEY], if used, -- can be used with any TYPE? (or only the TYPE=OFFICIAL?) 2) What do CRT and KEY do? I'm presuming that CRT [and KEY], if used, should point to the full path of the server certificate [and key] -- but if I already have the server certificate -- why am I doing "make certificate" (unless when "official" make certificate is only for installing the certificate into Apache source for later make install? --Richard Robinson __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: make certificate TYPE, CRT, KEY
On Wed, Mar 17, 1999, Richard Robinson wrote: > I'm looking through the HISTORY file HISTORY? Hmmm... there is no HISTORY file in mod_ssl... > at the part where make > certificate has been expanded to use four TYPEs -- dummy, test, > custom, and official. > > make certificate TYPE=? CRT=/your/path/to/your.crt > KEY=/your/path/to/your.key > > I'm confused (sorry, but I am). My questions are several: > > 1) CRT [and KEY], if used, -- can be used with any TYPE? (or only the > TYPE=OFFICIAL?) "TYPE=OFFICIAL"? Hmmm.. seems like you're reading something different. But nevertheless, I know what you mean. You mean the "TYPE=existing" option. Yes, CRT=xxx KEY=xxx are only used with TYPE=existing. > 2) What do CRT and KEY do? I'm presuming that CRT [and KEY], > if used, should point to the full path of the server certificate [and > key] Yes. > -- but if I already have the server certificate -- why am I > doing "make certificate" (unless when "official" make certificate is > only for installing the certificate into Apache source for later make > install? The whole TYPE=existing is for easy upgrading an Apache+mod_ssl installation and giving the cert/key files is just for convinience reasons. You can always just say "make install" without a previous "make certificate", but then you've to copy your real cert/keys over the server.crt/server.key files in the installation tree manually. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: make certificate TYPE, CRT, KEY
On Wed, Mar 17, 1999, Richard Robinson wrote: > You're right, it' s called CHANGES, not HISTORY. I was reading it from your Web > site's Documentation page ("CHANGES: History of all changes"). > > The Makefile that's installed into Apache source directory says "existing" but > the CHANGES file > continues to say "official" Oh, there is the "official". I've replaced it now to no longer confuse people. Thanks for the hint. > Thanks for the info. > By the way I think you're doing, and have done, a great job and a great service > to everyone with mod_ssl. Thanks. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: make certificate TYPE, CRT, KEY
Ralf, You're right, it' s called CHANGES, not HISTORY. I was reading it from your Web site's Documentation page ("CHANGES: History of all changes"). The Makefile that's installed into Apache source directory says "existing" but the CHANGES file continues to say "official" Thanks for the info. By the way I think you're doing, and have done, a great job and a great service to everyone with mod_ssl. "Ralf S. Engelschall" wrote: > On Wed, Mar 17, 1999, Richard Robinson wrote: > > > I'm looking through the HISTORY file > > HISTORY? Hmmm... there is no HISTORY file in mod_ssl... > > > at the part where make > > certificate has been expanded to use four TYPEs -- dummy, test, > > custom, and official. > > > > make certificate TYPE=? CRT=/your/path/to/your.crt > > KEY=/your/path/to/your.key > > > > I'm confused (sorry, but I am). My questions are several: > > > > 1) CRT [and KEY], if used, -- can be used with any TYPE? (or only the > > TYPE=OFFICIAL?) > > "TYPE=OFFICIAL"? Hmmm.. seems like you're reading something different. But > nevertheless, I know what you mean. You mean the "TYPE=existing" option. Yes, > CRT=xxx KEY=xxx are only used with TYPE=existing. > > > 2) What do CRT and KEY do? I'm presuming that CRT [and KEY], > > if used, should point to the full path of the server certificate [and > > key] > > Yes. > > > -- but if I already have the server certificate -- why am I > > doing "make certificate" (unless when "official" make certificate is > > only for installing the certificate into Apache source for later make > > install? > > The whole TYPE=existing is for easy upgrading an Apache+mod_ssl installation > and giving the cert/key files is just for convinience reasons. You can always > just say "make install" without a previous "make certificate", but then you've > to copy your real cert/keys over the server.crt/server.key files in the > installation tree manually. >Ralf S. Engelschall >[EMAIL PROTECTED] >www.engelschall.com > __ > Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ > Official Support Mailing List [EMAIL PROTECTED] > Automated List Manager [EMAIL PROTECTED] -- Richard Robinson Web Administrator Litho Development & Research [EMAIL PROTECTED] 503-255-5800 x172 __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]