similar to: Problems in slogin.1, sshd_config.5, ssh_config.5

Hello, There are three small problems with the "slogin" and "slogin.1" symlinks created upon installation: 1. "./" is included in the target path unnecessarily. 2. Symlinks are assumed to be available, while only hardlinks could. 3. EXEEXT is not respected for slogin. Here is a fix for both problems -- the "./" is simply removed, EXEEXT is added, the

https://bugzilla.mindrot.org/show_bug.cgi?id=1728 Summary: unnecessary "./" in slogin and slogin.1 symlinks Product: Portable OpenSSH Version: 5.3p1 Platform: Other OS/Version: Linux Status: NEW Severity: trivial Priority: P2 Component: Build system AssignedTo: unassigned-bugs at

This is automatically generated email about markup problems in a man page for which you appear to be responsible. If you are not the right person or list, please tell me so I can correct my database. See http://catb.org/~esr/doclifter/bugs.html for details on how and why these patches were generated. Feel free to email me with any questions. Note: These patches do not change the modification

http://bugzilla.mindrot.org/show_bug.cgi?id=509 Summary: slogin.1 is a broken symlink Product: Portable OpenSSH Version: -current Platform: All OS/Version: Linux Status: NEW Severity: trivial Priority: P4 Component: Documentation AssignedTo: openssh-unix-dev at mindrot.org ReportedBy:

It appears that the redhat/openssh.spec has not been updated to account for the removal of slogin from the build. This breaks rpmbuild. Specifically lines 361 and 362 still have the following: %attr(-,root,root) %{_bindir}/slogin %attr(-,root,root) %{_mandir}/man1/slogin.1* Robert Moucha Geophysics Syracuse University

Hello. I noticed that OpenSSH 2.1.1p3 does not check whether it is being called as rlogin or slogin, like it's siblings do. This can get ugly if you have rlogin and rsh symlinked to ssh, and old r* commands are moved off in another place, as I do. Since Solaris rsh is hardcoded to call /usr/bin/rlogin, it will get stuck in an infinite loop. Below is a quick patch I hacked up, based on

slogin "deadlocks" if you invoke it with the (useless, but legal) switch "-n". stdin is not passed to it (and the local ssh process ignores stdin), so it is not possible to kill it using <<~.>> Should the "-n_ switch be disallowed for an interactive invocation? Martin -- <Martin.Kraemer at Fujitsu-Siemens.com> | Fujitsu Siemens Fon:

Hi, After extensively looking into puppet + augeas for managing the AllowGroups in sshd_config, I came to the conclusion that it won''t work as I expected :( So I''m sharing my thoughts here. The main objective is allowing multiple groups per-node, depending on what the security team wants. Since I want this to be dynamic, I created a define in a class: class ssh::server::config

Hi! I'm experimenting with migrating the custom sshd_config settings for our (Debian bullseye, openssh-server 8.4) server environment into fragments under sshd_config.d/, and am wondering about sshd's behaviour when encountering multiple AllowGroup lines. The manual states "For each keyword, the first obtained value will be used.", so that gives me the impression that any

https://bugzilla.mindrot.org/show_bug.cgi?id=2292 Bug ID: 2292 Summary: sshd_config(5): DenyUsers, AllowUsers, DenyGroups, AllowGroups should actually tell how the evaluation order matters Product: Portable OpenSSH Version: 6.7p1 Hardware: All OS: All Status: NEW

Enclosed is a patch against 2.2.0p1 that teaches ssh (and therefore slogin and scp) how to invoke ssh-askpass to request a password, RSA/DSA key passphrase, or an skey challenge response. I've tested this on Linux (i386), for passwords and RSA/DSA key passphrases. I cannot easily test whether the Right Thing will happen for skey challenge responses; I would appreciate it if someone who uses

https://bugzilla.mindrot.org/show_bug.cgi?id=3193 Bug ID: 3193 Summary: Add separate section in sshd_config man page on Access Control Product: Portable OpenSSH Version: 8.3p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component:

Hello again, In my constant recompiles of 2.9p1 and 2.9p2, I've noticed that upgrading a current installation with a test compile leads to tons of files being updated even when they don't need to be. The attached patch for Makefile.in splits the install-files target into a bunch of serparate targets: install-dirs, install-prog, install-man, install-conf, which are then all called in

https://bugzilla.mindrot.org/show_bug.cgi?id=2391 Bug ID: 2391 Summary: Enhance AllowGroups documentation in man page Product: Portable OpenSSH Version: 6.8p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: Documentation Assignee:

Hi, This patch fixes a couple of small ``problems'' in 1.2pre17 Makefile.in: 1. Avoid making an empty $(libexecdir)/ssh directory. 2. Don't try to uninstall $(mandir)/man1/slogin.1 twice. --- openssh-1.2pre17/Makefile.in~ Thu Dec 9 00:48:58 1999 +++ openssh-1.2pre17/Makefile.in Thu Dec 9 06:51:41 1999 @@ -92,9 +92,9 @@ -rm -f $(mandir)/man1/slogin.1 ln -s ssh.1

The attached patch (relative to the current CVS snapshot) uses a perl script to convert the OpenSSH manpages from the BSD -mdoc format to the -man format used by other systems. This allows the unformatted manpages to be installed normally, rather than defaulting to preformatted pages. I'd like to see this patch integrated into the portable version of OpenSSH. Please let me know what you

https://bugzilla.mindrot.org/show_bug.cgi?id=2557 Bug ID: 2557 Summary: Incorrect file entries in openssh.spec Product: Portable OpenSSH Version: 7.2p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: Miscellaneous Assignee: unassigned-bugs

Hai, I have AllowGroups sshlinux, sshwindows Add at least 1 user in the linux group and at least 1 in the sshwindows group. Make sure the sshwindows group have a GID. And make sure the windows user loggin in in ssh als have a UID. AND for both, UID 1000+ ( which is in debian the default PAM setting ) . This is base on a "MEMBER" server. If you do : getent windowsuser You

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

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