1 --- cups-1.1.10/ENCRYPTION.txt.orig Thu Jan 4 07:42:35 2001
2 +++ cups-1.1.10/ENCRYPTION.txt Thu Jan 4 09:23:15 2001
4 properly signed it will generate all kinds of warnings in
9 openssl req -new -x509 -keyout /etc/cups/ssl/server.key \
10 -out /etc/cups/ssl/server.crt -days 365 -nodes
13 encrypted. The cupsd process runs in the background, detached
14 from any input source; if you encrypt these files then cupsd
15 will not be able to load them!
17 +If the above "openssl" command issues messages as
19 + Using configuration from /usr/lib/ssl/openssl.cnf
20 + Unable to load config info
24 + unable to find 'distinguished_name'
25 + problems making Certificate Request
27 +create a file /usr/lib/ssl/openssl.cnf (or how it was called in the
28 +error message) containing
30 +-----------------openssl.cnf-------------------------------------------
33 +distinguished_name = req_distinguished_name
34 +[ req_distinguished_name ]
35 +countryName = Country Name (2 letter code)
36 +countryName_default = US
39 +localityName = Locality Name (eg, city)
40 +organizationalUnitName = Organizational Unit Name (eg, section)
41 +commonName = Common Name (eg, YOUR name)
43 +emailAddress = Email Address
44 +emailAddress_max = 40
46 +-----------------------------------------------------------------------
48 +and repeat the two commands. Now you will be asked some questions and
49 +the certificate will be generated.
59 +if you have further questions. See especially the "DIAGNOSTICS" and
60 +"EXAMPLES" sections of the "req" man page.
62 Send all rants about non-encrypted certificate and key files to
63 /dev/null. It makes sense to encrypt user files, but not for