openssh.git -

Age	Commit message (Collapse)	Author
2017-03-30	Move privilege separation directory and PID file from /var/run/ to /run/ ↵	Colin Watson
	(closes: #760422, #856825).
2013-06-13	Use 'set -e' rather than '#! /bin/sh -e' in maintainer scripts and	Colin Watson
	ssh-argv0.
2013-05-22	Replace old manual conffile handling code with dpkg-maintscript-helper,	Colin Watson
	via dh_installdeb.
2013-05-21	Remove support for upgrading from ssh-nonfree.	Colin Watson

2013-05-21	Remove ssh/use_old_init_script, which was a workaround for a very old	Colin Watson
	bug in /etc/init.d/ssh. If anyone has ignored this for >10 years then they aren't going to be convinced now.
2013-05-21	Drop conffile handling for upgrades from pre-split ssh package; this was	Colin Watson
	originally added in 1:4.3p2-7 / 1:4.3p2-8, and contained a truly ghastly hack around a misbehaviour in sarge's dpkg. Since this is now four Debian releases ago, we can afford to drop this and simplify the packaging.
2010-12-26	Touch /var/run/sshd/.placeholder in the preinst so that /var/run/sshd,	Colin Watson
	which is intentionally no longer shipped in the openssh-server package due to /var/run often being a temporary directory, is not removed on upgrade (closes: #575582).
2009-07-31	Use 'which' rather than 'type' in maintainer scripts.	Colin Watson

2008-03-22	* Use printf rather than echo -en (a bashism) in openssh-server.config and	Colin Watson
	openssh-server.preinst.
2008-02-08	* Move /etc/pam.d/ssh to /etc/pam.d/sshd, allowing us to stop defining	Colin Watson
	SSHD_PAM_SERVICE (closes: #255870).
2007-10-18	* Discard error output from dpkg-query in preinsts, in case the ssh	Colin Watson
	metapackage is not installed.
2007-06-04	* Use dpkg-query to fetch conffile md5sums rather than parsing	Colin Watson
	/var/lib/dpkg/status directly.
2006-12-23	* It turns out that the people who told me that removing a conffile in the	Colin Watson
	preinst was sufficient to have dpkg replace it without prompting when moving a conffile between packages were very much mistaken. As far as I can tell, the only way to do this reliably is to write out the desired new text of the conffile in the preinst. This is gross, and requires shipping the text of all conffiles in the preinst too, but there's nothing for it. Fortunately this nonsense is only required for smooth upgrades from sarge.
2006-12-06	* When installing openssh-client or openssh-server from scratch, remove	Colin Watson
	any unchanged conffiles from the pre-split ssh package to work around a bug in sarge's dpkg (thanks, Justin Pryzby and others; closes: #335276).
2005-09-02	* Fix XSIish uses of 'test' in openssh-server.preinst.	Colin Watson

2005-06-17	Manoj Srivastava:	Colin Watson
	- Added SELinux capability, and turned it on be default. Added restorecon calls in preinst and postinst (should not matter if the machine is not SELinux aware). By and large, the changes made should have no effect unless the rules file calls --with-selinux; and even then there should be no performance hit for machines not actively running SELinux. - Modified the preinst and postinst to call restorecon to set the security context for the generated public key files. - Added a comment to /etc/pam.d/ssh to indicate that an SELinux system may want to also include pam_selinux.so.
2004-07-31	* Split the ssh binary package into openssh-client and openssh-server	Colin Watson
	(closes: #39741). openssh-server depends on openssh-client for some common functionality; it didn't seem worth creating yet another package for this. * New transitional ssh package, depending on openssh-client and openssh-server. May be removed once nothing depends on it. * When upgrading from ssh to openssh-{client,server}, it's very difficult for the maintainer scripts to find out what version we're upgrading from without dodgy dpkg hackery. I've therefore taken the opportunity to move a couple of debconf notes into NEWS files, namely ssh/ssh2_keys_merged and ssh/user_environment_tell. * In general, upgrading to this version directly from woody without first upgrading to the version in sarge is not currently guaranteed to work very smoothly due to the aforementioned version discovery problems.