openssh.git -

Age	Commit message (Collapse)	Author
2006-09-29	* Read /etc/default/locale as well as /etc/environment (thanks, Raphaël	Colin Watson
	Hertzog; closes: #369395).
2006-05-16	* Include commented-out pam_access example in /etc/pam.d/ssh.	Colin Watson

2006-05-12	move pam_nologin to account; auth doesn't work with publickey	Colin Watson

2006-05-12	* Restore pam_nologin to /etc/pam.d/ssh; sshd no longer checks this itself	Colin Watson
	when PAM is enabled, but relies on PAM to do it.
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.
2005-01-11	Remove pam_nologin from /etc/pam.d/ssh, as sshd's built-in support appears	Colin Watson
	to be sufficient and more useful (closes: #162996).
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.