summaryrefslogtreecommitdiff
path: root/debian/openssh-server.dirs
AgeCommit message (Collapse)Author
2020-02-24Add /etc/ssh/sshd_config.d/ to openssh-serverColin Watson
Closes: #952427
2014-08-02Remove several unnecessary entries in debian/*.dirs.Colin Watson
2014-08-02Use dh-exec to simplify override_dh_install target.Colin Watson
2014-02-10Stop manually creating /usr/share/lintian/overrides; dh_lintian handles this.Colin Watson
2012-11-26Install apport hooks.Colin Watson
2009-06-05Remove /var/run/sshd from openssh-server package; it will be created atColin Watson
run-time before starting the server.
2009-01-28Add ufw integration (thanks, Didier Roche; seeColin Watson
https://wiki.ubuntu.com/UbuntuFirewall#Integrating%20UFW%20with%20Packages; LP: #261884).
2008-07-23Add lintian overrides for empty /usr/share/doc/openssh-clientColin Watson
directories in openssh-server and ssh (necessary due to being symlink targets).
2007-06-13* Add /etc/network/if-up.d/openssh-server to restart sshd when newColin Watson
interfaces appear (LP: #103436).
2005-05-31Change libexecdir to /usr/lib/openssh, and fix up various alternatives andColin Watson
configuration files to match (closes: #87900, #151321).
2004-08-31Move sshd_config(5) to openssh-server, where it belongs.Colin Watson
2004-07-31* Split the ssh binary package into openssh-client and openssh-serverColin 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.