Commit graph

6 commits

Author SHA1 Message Date
jlam
b477150822 We actually use the openssl buildlink2.mk file. 2002-08-28 04:02:50 +00:00
jlam
206e28e98a It's 0.9.6f, not 0.9.5f, and move things around so that IGNORE is set to
the proper message.
2002-08-28 04:00:55 +00:00
abs
6ea7067ecb openssl/buildlink.mk enforces OpenSSL>=0.9.5f due to the DoS fix. Do not bother
trying to ask for 0.9.5a as we will not be allowed to use it anyway.
2002-08-20 17:13:38 +00:00
jlam
6ac62a9292 IGNORE platforms that aren't noted to have an in-tree OpenSSH. For now,
this means only NetBSD-1.5.* and NetBSD-1.6* can do this update.
2002-06-28 18:34:14 +00:00
jlam
fbebf3817c Only allow an in-tree update to occur if OpenSSL>=0.9.5a is in the base
distribution.  This prevents surprises like "hey, why is /usr/sbin/sshd
broken" if a pkgsrc openssl is pkg_delete'd.  Idea by itojun.
2002-06-28 18:00:45 +00:00
jlam
18dad003e4 Add ability to update the in-tree OpenSSH directly from pkgsrc. This
installs the binaries directly in /usr and places the manpages and example
files in the correct hier(7) locations.  We don't register installation in
this case because the package database can't handle it.  We deal with the
ssh config files and directories as follows:

	NetBSD-1.5.*	use /etc/ssh_config, /etc/sshd_config
	NetBSD-1.6	use /etc/ssh/ssh_config, /etc/ssh/sshd_config

We also emit a warning in the MESSAGE file that /etc/ssh.conf and
/etc/sshd.conf should be renamed in order to keep using them.  Lastly,
there is a new target "tarball" to generate a tarball of the installed
files that might be used to install quickly on many machines, though it
may be only of limited utility.

These changes are only active if UPDATE_INTREE_OPENSSH is defined.
2002-06-28 17:10:16 +00:00