[Bug 161047] Re: ssh server forces a command when it should not

2014-09-17 Thread Simon Déziel
>From https://bugzilla.mindrot.org/show_bug.cgi?id=1472#c3: Mass update RESOLVED->CLOSED after release of openssh-5.1 And Ubuntu ships version >=5.1+ since at least Precise. ** Changed in: openssh (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because y

[Bug 161047] Re: ssh server forces a command when it should not

2010-08-27 Thread Colin Watson
No update, and no time to look at it at the moment. ** Changed in: openssh (Ubuntu) Status: In Progress => Triaged ** Changed in: openssh (Ubuntu) Assignee: Colin Watson (cjwatson) => (unassigned) -- ssh server forces a command when it should not https://bugs.launchpad.net/bugs/1610

[Bug 161047] Re: ssh server forces a command when it should not

2010-08-26 Thread Thierry Carrez
@Colin, any update on this one ? Maybe set back to "Triaged" if you can't work on it right now ? -- ssh server forces a command when it should not https://bugs.launchpad.net/bugs/161047 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

[Bug 161047] Re: ssh server forces a command when it should not

2009-03-05 Thread Jacob Torrey
If I understand correctly your problem, I think you can use the ssh_config setting 'PreferredAuthentications while using ssh (ssh -o PreferredAuthentications password) to have it prefer the password over the key when you don't want it to use the key. Another option is to disable the ssh-agent bg pr

[Bug 161047] Re: ssh server forces a command when it should not

2008-07-25 Thread Colin Watson
5.1p1 doesn't seem to be working right for this. Bumping back to in- progress while I think about this. ** Changed in: openssh (Ubuntu) Status: Fix Committed => In Progress -- ssh server forces a command when it should not https://bugs.launchpad.net/bugs/161047 You received this bug notif

[Bug 161047] Re: ssh server forces a command when it should not

2008-07-22 Thread Colin Watson
Fixed in OpenSSH 5.1p1, which I'll be aiming to get into Intrepid. ** Changed in: openssh (Ubuntu) Status: In Progress => Fix Committed -- ssh server forces a command when it should not https://bugs.launchpad.net/bugs/161047 You received this bug notification because you are a member of U

[Bug 161047] Re: ssh server forces a command when it should not

2008-06-15 Thread Bug Watch Updater
** Changed in: openssh Status: Confirmed => Fix Released -- ssh server forces a command when it should not https://bugs.launchpad.net/bugs/161047 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-

[Bug 161047] Re: ssh server forces a command when it should not

2008-01-13 Thread Kuznik
Is there any additional info needed to confirm or reject this as a bug? Or if there is a way I could record all the communication so that it can be replayed somehow? -- ssh server forces a command when it should not https://bugs.launchpad.net/bugs/161047 You received this bug notification because

[Bug 161047] Re: ssh server forces a command when it should not

2007-11-16 Thread Kuznik
** Attachment added: "Ubuntu->IRIX64 debug3 output" http://launchpadlibrarian.net/10412463/sshIRIX64.log -- ssh server forces a command when it should not https://bugs.launchpad.net/bugs/161047 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contac

[Bug 161047] Re: ssh server forces a command when it should not

2007-11-16 Thread Kuznik
All the files have their permissions set to 644, also checking the /var/log/dpkg.log* did come up with only two updates: 2007-10-06 both openssh server and client (1:4.6p1-5 -> 1:4.6p1-5build1) 2007-09-17 also both (1:4.3p2-8ubuntu1 -> 1:4.6p1-5) So I did a little more research and it looks like

[Bug 161047] Re: ssh server forces a command when it should not

2007-11-12 Thread Mathias Gug
Thank you for taking the time to report this bug and trying to help make Ubuntu better. Could you check the permission on the ssh configuration files ? Could you run the client in a more verbose mode ? Could you check there was a package upgrade on the server or the client by looking in /var/log/dp