From: Done, George (george.done@orangemail.nl)
Date: Fri Aug 05 2005 - 11:00:35 EDT
Hi !
I try to do an rcp (remote copy) between 2 solaris machines, as root
/.rhosts and /etc/default/login (comment console entry) have been
edited.
I can rsh from machine A to machine B, as root, passwordless connection.
But when I try to rcp a file from machine A to machine B, as root, I get
the message:
"Insufficent credentials" (mispelled)
The /etc/pam.conf entries on machine B are:
"/etc/pam.conf" 89 lines, 3005 characters
#
# ident "@(#)pam.conf 1.19 03/01/10 SMI"
#
# Copyright 1996-2002 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
#
# PAM configuration
# defined in the "other" section.
#
# Modules are defined with relative pathnames, i.e., they are
# relative to /usr/lib/security/$ISA. Absolute path names, as
# present in this file in previous releases are still acceptable.
#
# Authentication management
#
# login service (explicit because of pam_dial_auth)
#
login auth requisite pam_authtok_get.so.1
login auth required pam_dhkeys.so.1
login auth required pam_unix_auth.so.1
login auth required pam_dial_auth.so.1
#
# rlogin service (explicit because of pam_rhost_auth)
#
rlogin auth sufficient pam_rhosts_auth.so.1
rlogin auth requisite pam_authtok_get.so.1
rlogin auth required pam_dhkeys.so.1
rlogin auth required pam_unix_auth.so.1
#
# rsh service (explicit because of pam_rhost_auth,
# and pam_unix_auth for meaningful pam_setcred)
#
#rsh auth required pam_rhosts_auth.so.1
#rsh auth required pam_rhosts_auth.so.1
rsh auth sufficient pam_rhosts_auth.so.1
rsh auth required pam_unix_auth.so.1
#
# PPP service (explicit because of pam_dial_auth)
#
ppp auth requisite pam_authtok_get.so.1
ppp auth required pam_dhkeys.so.1
ppp auth required pam_unix_auth.so.1
ppp auth required pam_dial_auth.so.1
#
# Default definitions for Authentication management
# Used when service name is not explicitly mentioned for authenctication
#
other auth requisite pam_authtok_get.so.1
other auth required pam_dhkeys.so.1
other auth required pam_unix_auth.so.1
#
# passwd command (explicit because of a different authentication module)
#
passwd auth required pam_passwd_auth.so.1
#
# cron service (explicit because of non-usage of pam_roles.so.1)
#
cron account required pam_projects.so.1
cron account required pam_unix_account.so.1
#
# Default definition for Account management
# Used when service name is not explicitly mentioned for account
management
#
other account requisite pam_roles.so.1
other account required pam_projects.so.1
other account required pam_unix_account.so.1
#
# Default definition for Session management
# Used when service name is not explicitly mentioned for session
management
#
other session required pam_unix_session.so.1
#
# Default definition for Password management
# Used when service name is not explicitly mentioned for password
management
#
other password required pam_dhkeys.so.1
other password requisite pam_authtok_get.so.1
other password requisite pam_authtok_check.so.1
other password required pam_authtok_store.so.1
#
# Support for Kerberos V5 authentication (uncomment to use Kerberos)
#
#rlogin auth optional pam_krb5.so.1 try_first_pass
#login auth optional pam_krb5.so.1 try_first_pass
#other auth optional pam_krb5.so.1 try_first_pass
#cron account optional pam_krb5.so.1
#other account optional pam_krb5.so.1
#other session optional pam_krb5.so.1
#other password optional pam_krb5.so.1 try_first_pass
What am I missing here ? I is clearly a pam.conf issue, but why rsh do
work and rcp do not ?
===========================================================
De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is alleen
bestemd voor de geadresseerde. Indien u dit bericht onterecht ontvangt, wordt
u verzocht de inhoud niet te gebruiken en de afzender direct te informeren
door het bericht te retourneren. Hoewel Orange maatregelen heeft genomen om
virussen in deze email of attachments te voorkomen, dient u ook zelf na te
gaan of virussen aanwezig zijn aangezien Orange niet aansprakelijk is voor
computervirussen die veroorzaakt zijn door deze email.
The information contained in this message may be confidential and is intended
to be only for the addressee. Should you receive this message unintentionally,
please do not use the contents herein and notify the sender immediately by
return e-mail. Although Orange has taken steps to ensure that this email and
attachments are free from any virus, you do need to verify the possibility of
their existence as Orange can take no responsibility for any computer virus
which might be transferred by way of this email.
===========================================================
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:31:15 EDT