12-22-2008
I forgot to mention that the userid is using NIS authentication.
8 More Discussions You Might Find Interesting
1. SuSE
OK, this is the problem. I have 2 machines TestA ( Suse 9.0 ) TestB ( Mandrake 10 ) and one of our guys wants to scp from TestA to TestB without the password prompt appearing. Sounds simple so far....
Ok, I haven't used ssh-keygen before, so I create identical logins to test what I'm doing...... (4 Replies)
Discussion started by: PaulC
4 Replies
2. Solaris
Hi Gurus,
Got another issue.
I am trying to configure a user to run some scripts through trusted user where in while logging to remote system it shouldn't ask for password.
i did following to get it working but its not working
i create a private and public key with the below... (1 Reply)
Discussion started by: kumarmani
1 Replies
3. HP-UX
I get a message similar to this, in the syslog file.
Actually, I am trying to let the host at 10.10.10.10 access the HP-UX system.
How do I get it trusted?
Thanks! (2 Replies)
Discussion started by: instant000
2 Replies
4. UNIX for Dummies Questions & Answers
Hi, i am setting up ssh trust setup between two servers where SVRA is a solaris box and SVRB is a Red Hat Linux.
It is asking for the password all the time.
I have copied over the SVRA:/home/nagios/.ssh/id_dsa.pub as authorized_keys on
to SVRB:/dat01/home/nagios/.ssh/
-bash-3.00$ ssh -vvv... (4 Replies)
Discussion started by: uxadmin007
4 Replies
5. Shell Programming and Scripting
Hi Experts,
I came across this interesting situation. I have following ssh script login to multiple server. This works fine for one set of servers (linux) but on my sun boxes i am getting. error
#!/usr/bin/perl -w
use Net::SSH::Perl;
use POSIX;
use Term::ANSIColor qw(:constants);
use... (2 Replies)
Discussion started by: mtomar
2 Replies
6. AIX
Hi ,
I am trying to create public key on my AIX server on other than home directory.However the command does not ask for
Enter file in which to save the key :
It is directly taking me to Enter the passphrase.
I don't want to save the key in home dir as that is the home dir for other userID... (6 Replies)
Discussion started by: saurau
6 Replies
7. Shell Programming and Scripting
Hello Everyone,
I have the following codes that only works for the first login element. I can't get it work with the second and third login credentials. Can anyone here see the problem?
I ran the code with host1, it works as expect. see below:
# ./test.pl host1
Trying to connect... (3 Replies)
Discussion started by: tqlam
3 Replies
8. Shell Programming and Scripting
Hi,
I want test the ssh trust between two host. It works fine if the trust is working fine but if the trust is not working fine it gets stuck.
#!/bin/sh
>/users/test/ssh.txt
for i in `cat /users/test/host.txt`;
do
ssh test@$i uname -a >> /users/test/ssh.txt
test=`cat... (0 Replies)
Discussion started by: Abhayman
0 Replies
SIVTEST(1) General Commands Manual SIVTEST(1)
*
NAME
sivtest - interactive MANAGESIEVE test program
SYNOPSIS
sivtest [ -t keyfile ] [ -p port ] [ -m mechanism ]
[ -a userid ] [ -u userid ] [ -k num ] [ -l num ]
[ -r realm ] [ -f file ] [ -n num ] [ -c ]
[ -i ] [ -o option=value ] [ -v ] hostname
DESCRIPTION
sivtest is a utility that allows you to authenticate to a MANAGESIEVE server and interactively issue commands to it. Once authenticated you
may issue any MANAGESIEVE command by simply typing it in. It is capable of multiple SASL authentication mechanisms and handles encryption
layers transparently. This utility is often used for testing the operation of a timsieved server. Also those developing MANAGESIEVE clients
find it useful.
OPTIONS
-t keyfile
Enable TLS. keyfile contains the TLS public and private keys. Specify "" to negotiate a TLS encryption layer but not use TLS
authentication.
-p port
Port to connect to. If left off this defaults to sieve as defined in /etc/services.
-m mechanism
Force sivtest to use mechanism for authentication. If not specified the strongest authentication mechanism supported by the server
is chosen.
-a userid
Userid to use for authentication; defaults to the current user. This is the userid whose password or credentials will be presented
to the server for verification.
-u userid
Userid to use for authorization; defaults to the current user. This is the userid whose identity will be assumed after authentica-
tion. NOTE: This is only used with SASL mechanisms that allow proxying (e.g. PLAIN, DIGEST-MD5).
-k num Minimum protection layer required.
-l num Maximum protection layer to use (0=none; 1=integrity; etc). For example if you are using the KERBEROS_V4 authentication mechanism
specifying 0 will force sivtest to not use any layer and specifying 1 will force it to use the integrity layer. By default the max-
imum supported protection layer will be used.
-r realm
Specify the realm to use. Certain authentication mechanisms (e.g. DIGEST-MD5) may require one to specify the realm.
-f file
Pipe file into connection after authentication.
-n num Number of authentication attempts; default = 1. The client will attempt to do SSL/TLS session reuse and/or fast reauth (e.g.
DIGEST-MD5), if possible.
-c Enable challenge prompt callbacks. This will cause the OTP mechanism to ask for the the one-time password instead of the secret
pass-phrase (library generates the correct response).
-i Don't send an initial client response for SASL mechanisms, even if the protocol supports it.
-o option=value
Set the SASL option to value.
-v Verbose. Print out more information than usual.
SEE ALSO
timsieved(8)
CMU
Project Cyrus SIVTEST(1)