Hitchhiker's Guide to Openbsd

ssl/private/server.csr
This server.csr file can then be given to Certifying Authority who will sign the key. One such CA is 
Thawte Certification which you can reach at 
http://www.thawte.com/
. 
If you cannot afford this, or just want to sign the certificate yourself, you can use the following. 
# openssl x509 -req -days 365 -in /etc/ssl/private/server.csr 
\
-signkey /etc/ssl/private/server.key -out /etc/ssl/
http://www.openbsd.org/faq/faq10.html (7 of 32)9/4/2011 10:02:15 AM

---

10 - System Management
server.crt
With /etc/ssl/server.crt and /etc/ssl/private/server.key in place, you should be able to start 
httpd(8)
 with the 
-DSSL flag (see the 
section about rc(8)
in this faq), enabling https transactions with your machine on port 
443. 
10.8 - I edited /etc/passwd, but the changes didn't seem to take 
place. Why?
If you edit /etc/passwd directly, your changes will be lost. OpenBSD generates /etc/passwd dynamically 
with 
pwd_mkdb(8)
. The main password file in OpenBSD is /etc/master.passwd. According to pwd_mkdb
(8), 
FILES
/etc/master.passwd current password file
/etc/passwd a 6th Edition-style password file
/etc/pwd.db insecure password database file
/etc/pwd.db.tmp temporary file
/etc/spwd.db secure password database file
/etc/spwd.db.tmp temporary file
In a traditional Unix password file, such as /etc/passwd, everything including the user's encrypted 
password is available to anyone on the system (and is a prime target for programs such as Crack). 4.4BSD 
introduced the master.passwd file, which has an extended format (with additional options beyond those 
provided by /etc/passwd) and is only readable by root. For faster access to data, the library calls which 
access this data normally read /etc/pwd.db and /etc/spwd.db. 
OpenBSD does come with a tool with which you should edit your password file. It is called 
vipw(8)
. Vipw 
will use vi (or your favourite editor defined per $EDITOR) to edit /etc/master.passwd. After you are done 
editing, it will re-create /etc/passwd, /etc/pwd.db, and /etc/spwd.db as per your changes. Vipw also takes 
care of locking these files, so that if anyone else attempts to change them at the same time, they will be 
denied access.