** Changed in: server-papercuts
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/543767
Title:
ssh logins doesn't show the MOTD when connecting with public key
I'm sort of confused by the bug report.
Here are the relevant snippets from the man-pages:
UsePAM Enables the Pluggable Authentication Module interface. If
set to
``yes'' this will enable PAM authentication using
ChallengeResponseAuthentication and
I encounter this issue also, MOTD not show when UsePAM no in sshd_config
My environment:
- OS: Ubuntu 16.04.1 LTS
- uname -a: Linux Jenkins 4.4.0-57-generic #78-Ubuntu SMP Fri Dec 9 23:50:32
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
- openssh-client: 7.2p2-4ubuntu2.1, amd64
--
You received this
I was struggling so long to figure out why I was shown no MOTD. Now I
know. I was told disabling PAM makes ssh more secure but does that apply
to key based auth?
** Changed in: openssh (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of
I was struggling so long to figure out why I was shown no MOTD. Now I
know. I was told disabling PAM makes ssh more secure but does that apply
to key based auth?
** Changed in: openssh (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of
I am also curious to understand why MOTD is being controlled by UsePAM
Yes and not just PrintMotd.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/543767
Title:
ssh logins doesn't
I am also curious to understand why MOTD is being controlled by UsePAM
Yes and not just PrintMotd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/543767
Title:
ssh logins doesn't show the MOTD when
Same here, on Ubuntu 14.04:
* Selecting 'PrintMotd yes' has no effect if UsePAM is no.
Choosing 'UsePAM yes' shows the Motd.
IMO, this is is a bug. The MOTD should be controlled solely by
PrintMotd. Is there a rationale behind hiding the MOTD if the user logs
in with a public key?
--
You
Same here, on Ubuntu 14.04:
* Selecting 'PrintMotd yes' has no effect if UsePAM is no.
Choosing 'UsePAM yes' shows the Motd.
IMO, this is is a bug. The MOTD should be controlled solely by
PrintMotd. Is there a rationale behind hiding the MOTD if the user logs
in with a public key?
--
You
[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]
** Changed in: openssh (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]
** Changed in: openssh (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/543767
If you use:
PasswordAuthentication no
ChallengeResponseAuthentication no
PubkeyAuthentication yes
then SSH will only allow public-key auth. The server has the public key
in authorized_keys, you need to have the corresponding private key.
--
ssh logins doesn't show the MOTD when connecting with
If you use:
PasswordAuthentication no
ChallengeResponseAuthentication no
PubkeyAuthentication yes
then SSH will only allow public-key auth. The server has the public key
in authorized_keys, you need to have the corresponding private key.
--
ssh logins doesn't show the MOTD when connecting with
Selecting 'PrintMotd yes' has no effect, I tried that already.
Choosing 'UsePAM yes' shows the Motd.
But: I don't want to allow logins using a simple password, but want to make
sure the exchange of keys is used.
Can you (or anybody else) confirm that every user _has_ to have the key?
--
ssh
Selecting 'PrintMotd yes' has no effect, I tried that already.
Choosing 'UsePAM yes' shows the Motd.
But: I don't want to allow logins using a simple password, but want to make
sure the exchange of keys is used.
Can you (or anybody else) confirm that every user _has_ to have the key?
--
ssh
The MOTD is generated through PAM, so the fact that you have UsePAM no
probably affects your results. In the same vein, you have PrintMotd
no... Having the combination of the 2 parameters probably prevents the
motd from being displayed in certain cases.
I'd suggest trying
UsePAM yes
Or
PrintMotd
The MOTD is generated through PAM, so the fact that you have UsePAM no
probably affects your results. In the same vein, you have PrintMotd
no... Having the combination of the 2 parameters probably prevents the
motd from being displayed in certain cases.
I'd suggest trying
UsePAM yes
Or
PrintMotd
Sure, here it is: I don't use PAM.
# Package generated configuration file
# See the sshd(8) manpage for details
# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress ::
#ListenAddress 0.0.0.0
Protocol 2
#
** Changed in: server-papercuts
Status: New = Incomplete
--
ssh logins doesn't show the MOTD when connecting with public key authorisation
https://bugs.launchpad.net/bugs/543767
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Changed in: server-papercuts
Status: New = Incomplete
--
ssh logins doesn't show the MOTD when connecting with public key authorisation
https://bugs.launchpad.net/bugs/543767
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Sure, here it is: I don't use PAM.
# Package generated configuration file
# See the sshd(8) manpage for details
# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress ::
#ListenAddress 0.0.0.0
Protocol 2
#
This might be way off but if I remember this correctly it has something
to do with with the UsePAM setting in sshd_config.
--
ssh logins doesn't show the MOTD when connecting with public key authorisation
https://bugs.launchpad.net/bugs/543767
You received this bug notification because you are a
@Laryllan:
Could you attach your /etc/ssh/sshd_config file, or tell us if you set UsePAM ?
--
ssh logins doesn't show the MOTD when connecting with public key authorisation
https://bugs.launchpad.net/bugs/543767
You received this bug notification because you are a member of Ubuntu
Server Team,
This might be way off but if I remember this correctly it has something
to do with with the UsePAM setting in sshd_config.
--
ssh logins doesn't show the MOTD when connecting with public key authorisation
https://bugs.launchpad.net/bugs/543767
You received this bug notification because you are a
@Laryllan:
Could you attach your /etc/ssh/sshd_config file, or tell us if you set UsePAM ?
--
ssh logins doesn't show the MOTD when connecting with public key authorisation
https://bugs.launchpad.net/bugs/543767
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The strange thing being, you get the MOTD when doing password
authentication, but you don't get it when you do publickey
authentication. Can you still reproduce that, and if yes, could you
attach your /etc/ssh/sshd_config ?
--
ssh logins doesn't show the MOTD when connecting with public key
@Dustin:
From the server showing the MOTD, I get the following output:
lrwxrwxrwx 1 root root 13 2009-05-09 18:58 /etc/motd - /var/run/motd
-rw-r--r-- 1 root root 168 2010-03-31 19:07 /var/run/motd
/etc/update-motd.d:
total 12
drwxr-xr-x 2 root root 4096 2009-11-10 06:36 ./
drwxr-xr-x 94
@Thierry:
I will try to reproduce the behaviour in the next days, when I'll have access
to the server.
Right now I'm not eager to lock me out by mistake...
--
ssh logins doesn't show the MOTD when connecting with public key authorisation
https://bugs.launchpad.net/bugs/543767
You received this
The strange thing being, you get the MOTD when doing password
authentication, but you don't get it when you do publickey
authentication. Can you still reproduce that, and if yes, could you
attach your /etc/ssh/sshd_config ?
--
ssh logins doesn't show the MOTD when connecting with public key
@Dustin:
From the server showing the MOTD, I get the following output:
lrwxrwxrwx 1 root root 13 2009-05-09 18:58 /etc/motd - /var/run/motd
-rw-r--r-- 1 root root 168 2010-03-31 19:07 /var/run/motd
/etc/update-motd.d:
total 12
drwxr-xr-x 2 root root 4096 2009-11-10 06:36 ./
drwxr-xr-x 94
@Thierry:
I will try to reproduce the behaviour in the next days, when I'll have access
to the server.
Right now I'm not eager to lock me out by mistake...
--
ssh logins doesn't show the MOTD when connecting with public key authorisation
https://bugs.launchpad.net/bugs/543767
You received this
Nope. It isn't present on both servers - not on the one showing the MOTD
nor the one not showing the MOTD.
--
ssh logins doesn't show the MOTD when connecting with public key authorisation
https://bugs.launchpad.net/bugs/543767
You received this bug notification because you are a member of
And what's the output of:
ls -alF /var/run/motd /etc/motd /etc/update-motd.d
--
ssh logins doesn't show the MOTD when connecting with public key authorisation
https://bugs.launchpad.net/bugs/543767
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Nope. It isn't present on both servers - not on the one showing the MOTD
nor the one not showing the MOTD.
--
ssh logins doesn't show the MOTD when connecting with public key authorisation
https://bugs.launchpad.net/bugs/543767
You received this bug notification because you are a member of
And what's the output of:
ls -alF /var/run/motd /etc/motd /etc/update-motd.d
--
ssh logins doesn't show the MOTD when connecting with public key authorisation
https://bugs.launchpad.net/bugs/543767
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Can't reproduce either with a basic publickey karmic setup, running the
same version (1:5.1p1-6ubuntu2). Something else in your configuration
must prevent it from being shown...
--
ssh logins doesn't show the MOTD when connecting with public key authorisation
ls -alF $HOME/.hushlogin
Is that file present?
--
ssh logins doesn't show the MOTD when connecting with public key authorisation
https://bugs.launchpad.net/bugs/543767
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
Can't reproduce either with a basic publickey karmic setup, running the
same version (1:5.1p1-6ubuntu2). Something else in your configuration
must prevent it from being shown...
--
ssh logins doesn't show the MOTD when connecting with public key authorisation
ls -alF $HOME/.hushlogin
Is that file present?
--
ssh logins doesn't show the MOTD when connecting with public key authorisation
https://bugs.launchpad.net/bugs/543767
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Im not able to reproduce this which version are you using?
Regards
chuck
** Changed in: openssh (Ubuntu)
Importance: Undecided = Low
** Changed in: openssh (Ubuntu)
Status: New = Incomplete
--
ssh logins doesn't show the MOTD when connecting with public key authorisation
I'm using:
openssh-server 1:5.1p1-6ubuntu2
Running Ubuntu 9.10.
At this time, I don't have any server running Lucid available.
Both openssh-clients on Karmic an Lucid have the same problem, which should be
normal cause the client doesn't generate the MOTD I guess...
--
ssh logins doesn't
Im not able to reproduce this which version are you using?
Regards
chuck
** Changed in: openssh (Ubuntu)
Importance: Undecided = Low
** Changed in: openssh (Ubuntu)
Status: New = Incomplete
--
ssh logins doesn't show the MOTD when connecting with public key authorisation
I'm using:
openssh-server 1:5.1p1-6ubuntu2
Running Ubuntu 9.10.
At this time, I don't have any server running Lucid available.
Both openssh-clients on Karmic an Lucid have the same problem, which should be
normal cause the client doesn't generate the MOTD I guess...
--
ssh logins doesn't
43 matches
Mail list logo
