10-07-2002
sshd
i just downloaded and installed succesfully openssh server, and am running it on netbsd 1.5, i can not login with anyuser, i enabled root login just to see what happens and i can login as root, but no other user, i checked my config and most things are default, whats going on? has any one else had similar problems?
any responce and help is appreaciated, thanks!
----
more generally, why cant any users except root login using ssh?
Last edited by norsk hedensk; 10-08-2002 at 01:40 PM..
10 More Discussions You Might Find Interesting
1. AIX
need some clarification:
if i ssh to the server & i restart the sshd process, did my connection gone?
one more thing, there are a few sshd processes in aix, how do i restart it all to read new config? using HUP?
thanks in advance! (2 Replies)
Discussion started by: ashterix
2 Replies
2. AIX
Friends,
I made the installation of the ssh in the it conspires,
I configured in the ssh_config the following
parameters..
SyslogFacility AUTH
LogLevel INFO
that should generate sshd.log in the /var/log.... more no this generating.
Somebody could help myself in... (0 Replies)
Discussion started by: sandba
0 Replies
3. UNIX for Dummies Questions & Answers
Can someone tell me the difference between the (2) listed below:
oracle pts/1 ip1 May1 7:11 9:11
oracle sshd ip1 May1 7:11 8:22
How do I read the above information, the fact that the row for pts/1 has a longer time duration than the row for sshd. Why is the... (2 Replies)
Discussion started by: banyan
2 Replies
4. AIX
I installed OpenSSH on AIX 5.1 but when I try to start it, it says:
bash-2.05a# /usr/sbin/sshd
bash-2.05a#
bash-2.05a# tail /var/adm/syslog.out
Jan 8 11:52:22 xyz sshd: fatal: Cannot bind any address.
:confused: (31 Replies)
Discussion started by: untamed
31 Replies
5. Solaris
My ssh log appear to the screen which i want it to be log to /var/log/sshd.log
how to log the sshd to /var/log? (5 Replies)
Discussion started by: hezry79
5 Replies
6. Solaris
Hi,
I´m trying to make Solaris authenticate users in AD. NTP is working, nsswitch.ldap is listed above, DNS is Ok and I made something different in pam.conf, krb5.conf and sshd_config (see above)
nsswitch.ldap:
passwd: files ldap
group: files ldap
hosts: files dns
ipnodes: ... (0 Replies)
Discussion started by: mpcavalcanti
0 Replies
7. Solaris
Hi,
I was able to putty a few server (Solaris 10) of mine using hostname, but when i change to ip address, it shows
login as: root
Using keyboard-interactive authentication.
Password:
Access denied
I change PermitRootLogin to yes. I tried to do a sshd restart, however
... (6 Replies)
Discussion started by: beginningDBA
6 Replies
8. Solaris
I have shamelessly tried all the possible ways to see if my /var/adm/loginlog logs user access entries for ssh but nothing has worked for me so far..:confused:
for telnet login its working fine.
Adding auth.info in syslog.conf works but i dont want that output.
Is there any way to edit... (2 Replies)
Discussion started by: ningy
2 Replies
9. AIX
Hello,
AIX 6.1
sshd worked fine.
Then I upgraded my AIX from 6100-02-04-0920 to 6100-03-10-1119 successfully(no errors, nothing unusual). After reboot sshd was not started, 3 errors in errpt:
# lssrc -s sshd
Subsystem Group PID Status
sshd ssh ... (0 Replies)
Discussion started by: vilius
0 Replies
10. Red Hat
Hi,
Do you know what cause the error message ?
Nov 19 13:42:19 cfsasnd02 sshd: pam_env(sshd:setcred): non-alphanumeric key '-- /etc/environment' in /etc/environment', ignoring
Nov 19 13:42:20 cfsasnd02 sshd: pam_env(sshd:setcred): non-alphanumeric key '-- /etc/environment' in... (0 Replies)
Discussion started by: xitrum
0 Replies
LEARN ABOUT MOJAVE
hosts.equiv
HOSTS.EQUIV(5) BSD File Formats Manual HOSTS.EQUIV(5)
NAME
hosts.equiv, .rhosts -- trusted remote hosts and host-user pairs
DESCRIPTION
The hosts.equiv and .rhosts files list hosts and users which are ``trusted'' by the local host when a connection is made via rlogind(8),
rshd(8), or any other server that uses ruserok(3). This mechanism bypasses password checks, and is required for access via rsh(1).
Each line of these files has the format:
hostname [username]
The hostname may be specified as a host name (typically a fully qualified host name in a DNS environment) or address, +@netgroup (from which
only the host names are checked), or a ``+'' wildcard (allow all hosts).
The username, if specified, may be given as a user name on the remote host, +@netgroup (from which only the user names are checked), or a
``+'' wildcard (allow all remote users).
If a username is specified, only that user from the specified host may login to the local machine. If a username is not specified, any user
may login with the same user name.
EXAMPLES
somehost
A common usage: users on somehost may login to the local host as the same user name.
somehost username
The user username on somehost may login to the local host. If specified in /etc/hosts.equiv, the user may login with only the same
user name.
+@anetgroup username
The user username may login to the local host from any machine listed in the netgroup anetgroup.
+
+ +
Two severe security hazards. In the first case, allows a user on any machine to login to the local host as the same user name. In the
second case, allows any user on any machine to login to the local host (as any user, if in /etc/hosts.equiv).
WARNINGS
The username checks provided by this mechanism are not secure, as the remote user name is received by the server unchecked for validity.
Therefore this mechanism should only be used in an environment where all hosts are completely trusted.
A numeric host address instead of a host name can help security considerations somewhat; the address is then used directly by iruserok(3).
When a username (or netgroup, or +) is specified in /etc/hosts.equiv, that user (or group of users, or all users, respectively) may login to
the local host as any local user. Usernames in /etc/hosts.equiv should therefore be used with extreme caution, or not at all.
A .rhosts file must be owned by the user whose home directory it resides in, and must be writable only by that user.
Logins as root only check root's .rhosts file; the /etc/hosts.equiv file is not checked for security. Access permitted through root's
.rhosts file is typically only for rsh(1), as root must still login on the console for an interactive login such as rlogin(1).
FILES
/etc/hosts.equiv Global trusted host-user pairs list
~/.rhosts Per-user trusted host-user pairs list
SEE ALSO
rcp(1), rlogin(1), rsh(1), rcmd(3), ruserok(3), netgroup(5)
HISTORY
The .rhosts file format appeared in 4.2BSD.
BUGS
The ruserok(3) implementation currently skips negative entries (preceded with a ``-'' sign) and does not treat them as ``short-circuit'' neg-
ative entries.
BSD
November 26, 1997 BSD