similar to: [Bug 729] Feature request + patch: DenyLockedAccounts option in sshd_config

http://bugzilla.mindrot.org/show_bug.cgi?id=898 Summary: support for AddressFamily in sshd_config Product: Portable OpenSSH Version: 3.8.1p1 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: sshd AssignedTo: openssh-bugs at mindrot.org ReportedBy: peak

Hello list, This is a patch to rsync 2.5.5, and it serves two purposes. The small patches to batch.c, flist.c and log.c simply add "void" to some function definitions so that all declarations in proto.h have full parameter lists. unsigned char read_batch_flags() OLD unsigned char read_batch_flags(void) NEW The SCO UNIXWare compiler correctly objected to these functions not having a

Hi, Guus I did some test regarding the points you mentioned below, and yes, you’re right, but some of points may need further adjusted: 1. The destination of IPv4 wouldn’t be changed, Yes I agree, that’s the goal and final destination for the communication. But during the path, it may be encapsulated into another packet(tunnel mode), where the outside IP header is the physical address, but the

http://bugzilla.mindrot.org/show_bug.cgi?id=108 Summary: Enable continuation with '\' (backslash) in /etc/ssh/sshd_config (feature request) Product: Portable OpenSSH Version: 2.9.9p2 Platform: ix86 OS/Version: Linux Status: NEW Severity: enhancement Priority: P5 Component: sshd

http://bugzilla.mindrot.org/show_bug.cgi?id=647 Summary: Setting "UsePAM no" in sshd_config gives error if not config'ed w/ --with-pam Product: Portable OpenSSH Version: -current Platform: Sparc OS/Version: SunOS Status: NEW Severity: minor Priority: P4 Component: sshd

http://bugzilla.mindrot.org/show_bug.cgi?id=285 ------- Additional Comments From dtucker at zip.com.au 2002-06-23 20:31 ------- Disabling PrivSep (add "UsePrivilegeSeparation no" to sshd_config) should get it working on 2.2 kernels. 3.3p1 defaults PrivSep to on. Previous releases (that supported it) defaulted to off. ------- You are receiving this mail because: ------- You

The sshd_config tweaks were executed even if the old file was still in place. Fix that. Also disable sshd user creation. It's not used on Cygwin. --- contrib/cygwin/ssh-host-config | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/contrib/cygwin/ssh-host-config b/contrib/cygwin/ssh-host-config index 52916d14ba94..cc36ea102f42 100644 ---

The NetBSD packages system "forbids" packages from installing stuff outside of the package tree (typically "/usr/pkg"). OpenSSH installs ssh*_config into $sysconfdir by default, which violates that rule. Christos Zoulas reworked Makefile.in to seperate the install from sysconfdir, and I added some logic to configure.in to add --with-example-dir. NetBSD's package would

https://bugzilla.mindrot.org/show_bug.cgi?id=2025 Priority: P5 Bug ID: 2025 Assignee: unassigned-bugs at mindrot.org Summary: Comments with 1024 chars or more break sshd_config Severity: normal Classification: Unclassified OS: Linux Reporter: bugzilla.mindrot.org-mail at nils.toedtmann.net Hardware: All

Hi I am just porting ssh-5.2 to my HPUX system. but while I'm doing it, I accidently found a different handling of the sshd for the SIGHUP signal when it is started with a "./sshd_config" and "/sshd_config". The problem is as following: root at sshpa6# uname -a HP-UX sshpa6 B.11.31 U 9000/800 2404418693 unlimited-user license root at sshpa6#

No response yet, so resending. -- Pekka Savola "Tell me of difficulties surmounted, Netcore Oy not those you stumble over and fall" Systems. Networks. Security. -- Robert Jordan: A Crown of Swords ---------- Forwarded message ---------- Date: Fri, 12 Oct 2001 09:44:54 +0300 (EEST) From: Pekka Savola <pekkas at netcore.fi> To: Damien Miller

http://cvs-mirror.mozilla.org/webtools/bugzilla/show_bug.cgi?id=353 ------- Additional Comments From Wayne.Corelli at hp.com 2002-08-14 23:56 ------- A temporary work around is to set "UsePrivilegeSeparation no" in sshd_config althought this disables all the "enhanced security" features. Would someone PLease address this!!! ------- You are receiving this mail

It seems the syntax for AllowUsers in sshd_config is not the same that is given in man sshd_config and in several documentation on the web. (http://www.openssh.com/cgi-bin/man.cgi?query=sshd_config) e.g. AllowUsers root does work. AllowUsers root username does not work. If I try to login as root I get "User root from <hostname> not allowed because not listed in AllowUsers".

Hi , I have two problems when i went through a) the man page of sshd_config and b) the comments quoted in sshd_config file itself. They are given below. a) >From the man page of sshd_config: "If UsePAM is enabled, you will not be able to run sshd(8) as a non-privileged user." I changed the permission of the hostkeys to a non-privileged user and tried to run sshd alongwith

https://bugzilla.mindrot.org/show_bug.cgi?id=2320 Bug ID: 2320 Summary: end-of-line comments work in sshd_config but not in ssh_config Product: Portable OpenSSH Version: 6.7p1 Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P5 Component: ssh

http://bugzilla.mindrot.org/show_bug.cgi?id=716 Summary: OpenSSH 3.7.1p2: sshd doesn't start at reboot (Tru64 UNIX) Product: Portable OpenSSH Version: -current Platform: Alpha OS/Version: OSF/1 Status: NEW Severity: major Priority: P2 Component: sshd AssignedTo: openssh-bugs

The following patch reformats sshd_config in sections. - Add section breaks to help finding visual cues. - Indent standard text to column 8 (position of tab) and leave configuration examples to the left. - Add new example: how to restrict root login only inside local LAN. Hope you find the changes helpful. The patch is against: CVS anoncvs at anoncvs.mindrot.org:/cvs 2010-12-21 12:59 UTC

The man 5 sshd_config fails to clarify what happens when multiple qualifying Match blocks specify the same configuration option. This patch updates the man page to do so. I tested the behaviour and described what was empirically observed. I can only assume this is the desired behaviour. This is a first attempt. If format or something else is off, let me know; I'll be happy to adjust.

https://bugzilla.mindrot.org/show_bug.cgi?id=1846 Priority: P2 Bug ID: 1846 Assignee: unassigned-bugs at mindrot.org Summary: wishlist: [PATCH] sshd_config - reformat for easier reading Severity: enhancement Classification: Unclassified OS: All Reporter: jari.aalto at cante.net

So I add the line PubkeyAcceptedKeyTypes +ssh-dss to my opensshd_config file. When I restart sshd, I am told that May 11 09:33:14 pickles systemd: Started OpenSSH Server Key Generation. May 11 09:33:14 pickles systemd: Started OpenSSH server daemon. May 11 09:33:14 pickles systemd: Starting OpenSSH server daemon... May 11 09:33:14 pickles sshd: /etc/ssh/sshd_config: line 156: Bad configuration