3 FreeBSD maintainer's guide to OpenSSH-portable
4 ==============================================
7 0) Make sure your mail spool has plenty of free space. It'll fill up
8 pretty fast once you're done with this checklist.
10 1) Grab the latest OpenSSH-portable tarball from the OpenBSD FTP
11 site (ftp://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/)
13 2) Unpack the tarball in a suitable directory.
17 $ eval "rm -rf $(tr '[:space:]' ' ' </usr/src/crypto/openssh/FREEBSD-Xlist)"
19 Make sure that took care of everything, and if it didn't, make sure
20 to update FREEBSD-Xlist so you won't miss it the next time.
22 4) Import the sources:
24 $ cvs import src/crypto/openssh OPENSSH OpenSSH_X_YpZ
26 5) Resolve conflicts. Remember to bump the version number and
27 addendum in version.h.
29 6) Generate configure and config.h.in:
34 Note: this requires a recent version of autoconf, not autoconf213.
36 7) Run configure with the appropriate arguments:
38 $ ./configure --prefix=/usr --sysconfdir=/etc/ssh \
39 --with-pam --with-tcp-wrappers
41 Note that we don't want to configure OpenSSH for Kerberos using
42 configure since we have to be able to turn it on or off depending
43 on the value of MAKE_KERBEROS[45]. Our Makefiles take care of
46 8) Commit the resulting config.h. Make sure you don't accidentally
47 commit any other files created by autoconf, autoheader or
48 configure; they'll just clutter up the repo and cause trouble at
53 A) Re-commit everything on freefall (you *did* use a test repo for
58 An overview of FreeBSD changes to OpenSSH-portable
59 ==================================================
63 The SSH protocol allows for a human-readable version string of up
64 to 40 characters to be appended to the protocol version string.
65 FreeBSD takes advantage of this to include a date indicating the
66 "patch level", so people can easily determine whether their system
67 is vulnerable when an OpenSSH advisory goes out. Some people,
68 however, dislike advertising their patch level in the protocol
69 handshake, so we've added a VersionAddendum configuration variable
70 to allow them to change or disable it.
72 1) Modified server-side defaults
74 We've modified some configuration defaults in sshd:
76 - For protocol version 2, we don't load RSA host keys by
77 default. If both RSA and DSA keys are present, we prefer DSA
80 - LoginGraceTime defaults to 120 seconds instead of 600.
82 - PermitRootLogin defaults to "no".
84 - X11Forwarding defaults to "yes" (it's a threat to the client,
87 - Unless the config file says otherwise, we automatically enable
88 Kerberos support if an appropriate keytab is present.
90 - PAMAuthenticationViaKbdInt defaults to "yes".
92 2) Modified client-side defaults
94 We've modified some configuration defaults in ssh:
96 - For protocol version 2, if both RSA and DSA keys are present,
99 - CheckHostIP defaults to "no".
101 3) Canonic host names
103 We've added code to ssh.c to canonicize the target host name after
104 reading options but before trying to connect. This eliminates the
105 usual problem with duplicate known_hosts entries.
109 We've added support for using OPIE as a drop-in replacement for
114 We use our own PAM code, which wraps PAM in a KbdintDevice and
115 works with privsep, instead of OpenSSH's own PAM code.
117 6) setusercontext() environment
119 Our setusercontext(3) can set environment variables, which we must
120 take care to transfer to the child's environment.
124 This port was brought to you by (in no particular order) DARPA, NAI
125 Labs, ThinkSec, Nescafé, the Aberlour Glenlivet Distillery Co.,
126 Suzanne Vega, and a Sanford's #69 Deluxe Marker.
130 $FreeBSD: src/crypto/openssh/FREEBSD-upgrade,v 1.1.2.2 2003/02/03 17:31:06 des Exp $
131 $DragonFly: src/crypto/openssh/Attic/FREEBSD-upgrade,v 1.2 2003/06/17 04:24:36 dillon Exp $