openssh.git -

Age	Commit message (Collapse)	Author
2010-01-02	Remove ssh/new_config, only needed for direct upgrades from potato which	Colin Watson
	are no longer particularly feasible anyway (closes: #420682).
2008-03-22	* Use printf rather than echo -en (a bashism) in openssh-server.config and	Colin Watson
	openssh-server.preinst.
2006-10-04	* Remove ssh/insecure_telnetd check altogether (closes: #391081).	Colin Watson

2005-05-31	Drop debconf support for allowing SSH protocol 1, which is discouraged and	Colin Watson
	has not been the default since openssh 1:3.0.1p1-1. Users who need this should edit sshd_config instead (closes: #147212).
2005-03-15	Remove obsolete and unnecessary ssh/forward_warning debconf note.	Colin Watson

2004-10-06	Forward-port from HEAD:	Colin Watson
	* If PasswordAuthentication is disabled, then offer to disable ChallengeResponseAuthentication too. The current PAM code will attempt password-style authentication if ChallengeResponseAuthentication is enabled (closes: #250369). * This will ask a question of anyone who installed fresh with 1:3.8p1-2 or later and then upgraded. Sorry about that ... for this reason, the default answer is to leave ChallengeResponseAuthentication enabled.
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.