similar to: [Bug 2181] New: error message changed for sftp(get command)

https://bugzilla.mindrot.org/show_bug.cgi?id=2210 Bug ID: 2210 Summary: scp -q isn't quiet when copying between two remote hosts Product: Portable OpenSSH Version: 6.0p1 Hardware: PPC OS: AIX Status: NEW Severity: normal Priority: P5 Component: scp

https://bugzilla.mindrot.org/show_bug.cgi?id=2006 Bug #: 2006 Summary: AIX 5.2 /32 bit - a windows Putty session will not connect to AIX box Classification: Unclassified Product: Portable OpenSSH Version: 6.0p1 Platform: All OS/Version: All Status: NEW Severity: normal

https://bugzilla.mindrot.org/show_bug.cgi?id=1463 Summary: Running nohup sleep 70 & and then exiting shell, hangs ssh Classification: Unclassified Product: Portable OpenSSH Version: 5.0p1 Platform: Sparc OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component:

https://bugzilla.mindrot.org/show_bug.cgi?id=2034 Priority: P5 Bug ID: 2034 Assignee: unassigned-bugs at mindrot.org Summary: make fails Severity: critical Classification: Unclassified OS: FreeBSD Reporter: kris.universe at gmail.com Hardware: amd64 Status: NEW Version: 6.0p1

What does "getent passwd <username>@<domainname>" return on the server for the login shell. By default a samba AD DC sets the login shell for all Active Directory user accounts to /bin/false. The only way I've found to change this, is to override that globally with the "template shell = /bin/bash" option in smb.conf, which enables it globally for all Active

5.1p1 disconnects after the password prompt when connecting to my router and UPS. 5.1p1 connects fine to other unix hosts, and my Windows client connects fine to 5.1p1 servers. 5.0p1 works fine everywhere. I've tried ssh -T, ssh -t, permutations with ssh -o Compression=no -o TCPKeepAlive=no, etc, to no avail. I've used the default ssh_config file, and it still fails. Can anyone

A thought came to me: The smb.conf file on the system has the following entry: template shell = /bin/bash Would creating a symbolic link with the name PHSshell pointing to the /bin/bash shell solve the problem? ________________________________ From: Kaplan, Andrew H. Sent: Thursday, June 09, 2016 11:00 AM To: Data Control Systems - Mike Elkevizth Cc: samba-technical at lists.samba.org; samba

On Wed, Jun 08, 2016 at 07:46:00PM +0000, Kaplan, Andrew H. wrote: > Hello -- > > We are running the 14.04.3 LTS 64-bit release as a virtual machine on a Vmware appliance. The goal of the installation is to create a Samba server that utilizes Active Directory authentication. To that end I utilized the following procedure: > >

Hello -- I started a thread on the list that you suggested in your e-mail, and thank-you for the reference. Also, I checked the auth.log file on the server, and the following entries were present: I checked the auth.log file, and the following entries were present: Jun 10 07:10:50 <samba server> sshd[7419]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh

The build bug: DESTDIR=$SOMEDIR does not work: mkdir ${HOME}/tools/openssh/openssh-5.0p1/_i/usr/local/etc ${HOME}/tools/openssh/openssh-5.0p1/_i/usr/local/sbin/sshd -t -f ${HOME}/tools/openssh/openssh-5.0p1/_i/usr/local/etc/sshd_config Could not load host key: /usr/local/etc/ssh_host_rsa_key Could not load host key: /usr/local/etc/ssh_host_dsa_key Disabling protocol version 2. Could not load

https://bugzilla.mindrot.org/show_bug.cgi?id=1484 Summary: escape character does not work over shared connections Classification: Unclassified Product: Portable OpenSSH Version: 5.0p1 Platform: Other OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: ssh AssignedTo:

Hello -- I tried the two methods listed in your e-mail, and unfortunately neither worked. The connection simply closed, or timed out, after about a minute. I mentioned the possibility of creating a symbolic link to the bash shell in my previous e-mail, could that be part of the solution? Thanks. ________________________________ From: Data Control Systems - Mike Elkevizth [mike at

I recently had to upgrade my version of OpenSSH from 4.7 to 5.0p1 on my MacBook (Darwin). I installed the latest 'portable' tarball and removed the system version: $ ssh -V OpenSSH_5.0p1, OpenSSL 0.9.7l 28 Sep 2006 $ which ssh /usr/bin/ssh sshd is the same version, installed in /usr/sbin/sshd. Now, things are a bit broken: I am able to ssh from another machine into my MacBook, so the

Hello -- The output of the getent passwd command was the following: <username>@<domainname>:*:##########:##########::/PHShome/<username>:/bin/PHSshell ________________________________ From: Data Control Systems - Mike Elkevizth [mike at datacontrolsystems.com] Sent: Wednesday, June 08, 2016 6:12 PM To: Kaplan, Andrew H. Cc: samba-technical at lists.samba.org; samba at

CentOS Errata and Security Advisory 2018:2181 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:2181 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 4d58715b4fb8e1a09e0f18ec69e93edc6e4b0558639d37421e8a7c5bd48ad344 gnupg2-2.0.22-5.el7_5.x86_64.rpm

Hello -- We are running the 14.04.3 LTS 64-bit release as a virtual machine on a Vmware appliance. The goal of the installation is to create a Samba server that utilizes Active Directory authentication. To that end I utilized the following procedure:

Hi, If you have the "template = /bin/bash" option, I think it is more likely something wrong with the way ssh is trying to authenticate the username. Do a "getent passwd" and then try "ssh -v '<username exactly as getent returns it (case sensitive)>'@<fqdn of server>. If it doesn't work, post the output of what ssh generates. Mike E. On Thu,

Hello -- The winbind packages that are installed on the server are the following: Package Description libnss-winbind 4.3.9+dfsg-0ubuntu0.14.04.3 amd64 Samba nameservice integration plugins libpam-winbind 4.3.9+dfsg-0ubuntu0.14.04.3 amd64 Windows domain authentication integration plugin libwbclient0 4.3.9+dfsg-0ubuntu0.14.04.3 amd64 Samba

Hi, Try using the format <domainname><winbind separator><username> to login instead of <username>@<domainname>. I'm not sure why, and don't have time to check into it right now, but ssh doesn't like the <username>@<domainname> format for me either. The default winbind separator is a backslash "\", so you'll have to escape it,

Hi openssh mailing list, I'm currently running Arch x86_64 with openssh 6.5p1, but the following is also reproduceable on Debian stable (openssh 6.0p1 I believe). Entering unicode characters directly into sftp results in no input. Not a placeholder character or a space, just no input. Here are some relevant details: The machines in my test both have locale correctly set (in this specific