For the record, the original bug here is the symptom of the libnss-
files-udeb package being missing in the installer environment for some
reason. This was probably transient.
--
edgy intall shell won't do scp
https://bugs.launchpad.net/bugs/53753
You received this bug notification because you ar
moot, cuz it looks like it got fixed.
for the record: user carl existed, but wouldn't have mattered - sshd
will not reject a connection on just user name - it needs both user and
pass.
** Changed in: openssh (Ubuntu)
Status: Needs Info => Rejected
--
edgy intall shell won't do scp
https
Does the user carl exist on the host 192.168.1.7 or the machine that you
try to remote logon ?
Do you have any restrictions configured which users can logon via ssh on
the remote machine ?
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) => txwikinger
Status: Unconfirmed => Need
** Changed in: Ubuntu
Sourcepackagename: None => openssh
--
edgy intall shell won't do scp
https://launchpad.net/bugs/53753
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
ssh 192.168.1.7 -l carl
You don't exist, go away!
(just in case anyone was wondering)
--
edgy intall shell won't do scp
https://launchpad.net/bugs/53753
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Right, for ssh, use the -l option to specify a valid username.
ssh xxx.yyy.zzz.sss -l carthik will let me login as carthik
Since you are running the command as root, it tries to login as root and
begets the message it does.
--
edgy intall shell won't do scp
https://launchpad.net/bugs/53753
--
# id
uid=0(root) gid=0(root)
--
edgy intall shell won't do scp
https://launchpad.net/bugs/53753
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Linux FAQ > 10. Frequently Encountered Error Messages
Question: 10.21. ``You don't exist. Go away.''
Answer:
This is not a viral infection. It comes from programs like write, talk,
and wall, if your invoking UID doesn't correspond to a valid user
(probably due to /et
