| View previous topic :: View next topic |
| Author |
Message |
xenome
n00b
Joined: 23 Aug 2003
Posts: 10
Location: Germany, PE
|
 Posted: Mon Oct 18, 2004 3:40 pm Post subject: critical connection problem (ssh) |
 |
|
hello,
i have an serious problem, when i try to connect to my root server i've got the follwing error:
| Quote: | Using username "root".
root@myhost.info's password:
sshd: root@ttyp0: relocation error: /lib/libnss_dns.so.2: symbol __res_maybe_init, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference |
i hope somebody can help me.... ah and the only way to access the server is by an recovery console, it's a litte debian bootimage... |
|
| Back to top |
|
 |
casper
Tux's lil' helper
Joined: 02 Nov 2003
Posts: 110
Location: Philadelphia, USA
|
| Posted: Mon Oct 18, 2004 7:16 pm Post subject: |
|
|
i have the same problem
i can connect as any user, however I cannot ssh as root
i have recently upgraded glibc to glibc-2.3.4.20040808-r1
-cos
_________________
fortune men-women:
"To our sweethearts and wives. May they never meet.
-- 19th century toast" |
|
| Back to top |
|
|
Danathan
Tux's lil' helper
Joined: 08 Mar 2004
Posts: 120
|
| Posted: Mon Oct 18, 2004 10:39 pm Post subject: |
|
|
Hi,
I had this problem after I upgrading glibc, and I found that it was a one time thing that went away when I restarted sshd. This is tough to do if you can't log in.
Also, apache had problems after the upgrade and needed to be restarted. I can't remember if there was anything else that needed restarting.
Best,
Dan |
|
| Back to top |
|
|
Danathan
Tux's lil' helper
Joined: 08 Mar 2004
Posts: 120
|
| Posted: Mon Oct 18, 2004 10:43 pm Post subject: |
|
|
...but if you can log in as any user, but cannot do so as root, the likely culprit is your sshd config.
Check /etc/sshd_config and make sure that it's set to allow root to login:
| Code: |
PermitRootLogin yes
|
But also be warned, allowing root to log in via ssh (esp. using passphrase auth) is generally frowned upon by the security conscious.
The security conscious are like this:
 |
|
| Back to top |
|
|
casper
Tux's lil' helper
Joined: 02 Nov 2003
Posts: 110
Location: Philadelphia, USA
|
| Posted: Tue Oct 19, 2004 12:47 am Post subject: |
|
|
i recompiled sshd, guess i shoul've just try and restart it first 
oh well, all's fine now
good luck with 'hacking' your computer :-/
_________________
fortune men-women:
"To our sweethearts and wives. May they never meet.
-- 19th century toast" |
|
| Back to top |
|
|
HomerSimpson
l33t
Joined: 25 Jan 2003
Posts: 869
Location: Ohio, USA
|
| Posted: Wed Oct 20, 2004 1:16 am Post subject: |
|
|
| Danathan wrote: | ...but if you can log in as any user, but cannot do so as root, the likely culprit is your sshd config.
Check /etc/sshd_config and make sure that it's set to allow root to login:
| Code: |
PermitRootLogin yes
|
But also be warned, allowing root to log in via ssh (esp. using passphrase auth) is generally frowned upon by the security conscious.
The security conscious are like this:
|
When you say "esp. using passphrase auth". Does esp mean especially? I thought passphrase was good? When you say passphrase, you mean a user needs a key and a passphrase to decrypt the key. This is bad?
Thx
_________________
The strong must protect the Sweet. |
|
| Back to top |
|
|
Danathan
Tux's lil' helper
Joined: 08 Mar 2004
Posts: 120
|
| Posted: Wed Oct 20, 2004 2:02 pm Post subject: |
|
|
Homer --
I meant passphrase as opposed to key-based auth. This is the default:
# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
...and it's ideal to change it to
PasswordAuthentication no
for the simple reason that a key is harder to guess or hack than a password.
But you're absolutely right -- having a key with a passphrase attached is more secure than one that does not require a passphrase. |
|
| Back to top |
|
|
|
Networking & Security
