Login annoyance [SOLVED]

[BFGod]

Hello.

First of all, greetings to entire gentoo community from a newcomer.

Ok, on to the questions. Could someone tell me how can one change the way the login is displayed, for example:

from:

Code: Select all

bfgod@gentoobox ~ $ ssh gentoobox
bfgod@gentoobox's password:

to:

Code: Select all

bfgod@gentoobox ~ $ ssh gentoobox
password:

Is there a way to NOT display username@computername before the password, and how can I go about changing that?

The second question would be how can I change /etc/issue and /etc/motd usage?

I have created /etc/motd but commenting out this line in /etc/login.defs. Also, I've uncommented /etc/issue line so that issue is displayed instead of motd, but motd is still displayed.

The relevant part looks like this:

Code: Select all

#MOTD_FILE      /etc/motd
ISSUE_FILE      /etc/issue

Am I working on a wrong config file, or do I need to execute some command or restart a service after modifying /etc/login.defs?

Thanks in advanced.

[papal_authority]

I am not aware of any way of changing the SSH password prompt short of hacking the source. Can you use key based authentication if you dislike the prompt?

[Kaste]

I don't think that is what s/he wants.
You need to specify a way for ssh to do something with the login shell it uses and then you need this:
http://gentoo-wiki.com/TIP_Prompt_Magic

But I'm fairly confident fiddling this to work will take a few hours.

I don't know about your other problem, but I think the solution is somehwere in man agetty

[BFGod]

Thank you for your answers. I'll probably skip your suggestion, because from my experience that "few hours" easily stretches to few days

And I thing I can answer myself the second question. I am logging on the machine over ssh, and displaying of motd over ssh obviously isn't controlled by /etc/login.defs but with /etc/ssh/sshd_config and there i could enable/disable displaying of the motd without problem. Also I didn't know that /etc/issue is only displayed locally, so turning it on/off offcourse didn't change anything when connecting over ssh.

I won't put [SOLVED] yet in the topic, because maybe someone will have a simpler solution to the first question, and I'm pretty sure it will be someting simple, because I talked to one person on #gentoo and he doesn't get that username@machine when ssh-ing, and he says it always worked like that for him.

[SirYes]

I talked to one person on #gentoo and he doesn't get that username@machine when ssh-ing, and he says it always worked like that for him.

Same experience here: I haven't seen "user@host's password" for a long time, even though I log to servers with different Linux distributions.

[converter]

Why is the inclusion of the user name and host name in the ssh password prompt a problem for you?

[BFGod]

Why is the inclusion of the user name and host name in the ssh password prompt a problem for you?

Well, it isn't a problem at all, it's an annoyance. It's just my curiosity to find out how things, even the small and/or insignificant thing like this work.

It's like this, on the debian machine that I have ssh access to, when logging in I get:

Code: Select all

username:
password:

MOTD

mail notification

last login

and on the server on which I installed gentoo, it's like this:

Code: Select all

username:
username@hostname's password:
last login

motd

and I just wanted to know if there is a (simple) way to change stuff like that, just out of curiosity, nothing more.

[converter]

Fair enough. Curiosity is a good thing.

Try running sshd in debug mode, listening to a special port (so you can run it independently of your regular sshd service) and run ssh with the -v switch. If you're watching the debug output of both the daemon and client, you should be able to figure out which authentication mechanism is printing the <user>@<hostname> prompt. My guess would be PAM.

[BFGod]

Nop, it doesn't seem to be PAM.

This is what I get:

Code: Select all

sshd[31718]: debug1: rexec start in 4 out 4 newsock 4 pipe 6 sock 7
sshd[31536]: debug1: Forked child 31718.
sshd[31718]: debug1: inetd sockets after dupping: 3, 3
sshd[31718]: Connection from xx.xx.xx.xx port 1997
sshd[31718]: debug1: Client protocol version 2.0; client software version PuTTY-Release-0.53b
sshd[31718]: debug1: no match: PuTTY-Release-0.53b
sshd[31718]: debug1: Enabling compatibility mode for protocol 2.0
sshd[31718]: debug1: Local version string SSH-2.0-OpenSSH_4.4
sshd[31718]: Failed none for bfgod from xx.xx.xx.xx port 1997 ssh2
sshd[31718]: Accepted password for bfgod from xx.xx.xx.xx port 1997 ssh2
sshd[31718]: debug1: monitor_child_preauth: bfgod has been authenticated by privileged process
sshd[31721]: debug1: permanently_set_uid: 1000/1000
sshd[31721]: debug1: Entering interactive session for SSH2.
sshd[31721]: debug1: server_init_dispatch_20
sshd[31721]: debug1: server_input_channel_open: ctype session rchan 256 win 16384 max 16384
sshd[31721]: debug1: input_session_request
sshd[31721]: debug1: channel 0: new [server-session]
sshd[31721]: debug1: session_new: init
sshd[31721]: debug1: session_new: session 0
sshd[31721]: debug1: session_open: channel 0
sshd[31721]: debug1: session_open: session 0: link with channel 0
sshd[31721]: debug1: server_input_channel_open: confirm session
sshd[31721]: debug1: server_input_channel_req: channel 0 request pty-req reply 1
sshd[31721]: debug1: session_by_channel: session 0 channel 0
sshd[31721]: debug1: session_input_channel_req: session 0 req pty-req
sshd[31721]: debug1: Allocating pty.
sshd[31718]: debug1: session_new: init
sshd[31718]: debug1: session_new: session 0
sshd[31721]: debug1: session_pty_req: session 0 alloc /dev/pts/5
sshd[31721]: debug1: server_input_channel_req: channel 0 request shell reply 1
sshd[31721]: debug1: session_by_channel: session 0 channel 0
sshd[31721]: debug1: session_input_channel_req: session 0 req shell
sshd[31722]: debug1: Setting controlling tty using TIOCSCTTY.

[BFGod]

Hey converter, thanks for mentioning PAM, I recompiled openssh with pam, set "UsePAM yes" in sshd_config and voila, no more username@hostname

I just need to figure out how to put last login *after* motd, but this is pretty much solved. I'll just keep it without [SOLVED] tag for two or three more days, maybe someone will suggest something about this last login after motd.