04-21-2019
Have $var in quotes: "$password"
These 2 Users Gave Thanks to MadeInGermany For This Post:
10 More Discussions You Might Find Interesting
1. Cybersecurity
I would like to know how to validate an unix password from shell script (If is possible)
Thanks very much
;) (3 Replies)
Discussion started by: juan_o_morillo
3 Replies
2. UNIX for Advanced & Expert Users
i finally got my key-pair system working... sort of a makeshift eToken
system. however, i only want to allow this sytem for system access. i
don't want to allow for the standard user/pass authentication system.
right now i changed the following:
# To disable tunneled clear text passwords,... (2 Replies)
Discussion started by: xyyz
2 Replies
3. UNIX for Advanced & Expert Users
AIX password authentication very slow
I installed and already removed openssh and our login on the aix box very slow.
It takes 30 seconds to get the password authenticated.
How can i debug this problem? and what might be the reason. It was working
fine until i tried to get openssh... (0 Replies)
Discussion started by: progressdll
0 Replies
4. Solaris
Hello;
I am moving a customer from Solaris 2.6 to Solaris 2.8. The customer has requested the following two requirements also be implemented:
1. Lock a user account out for X number of days after 3 unsuccessful login attempts.
2. No reuse of the last 5-10 passwords. Also referred to... (1 Reply)
Discussion started by: rambo15
1 Replies
5. Solaris
I am using solaris unix 8.2 version. I want to bypass password authentication for sftp. Can you please give some ideas on this. thanks.Regards. (4 Replies)
Discussion started by: vijill
4 Replies
6. Solaris
I can able to SFTP from my web server unix to apps server unix end. but the other way from APPS server to Web server is still asking me the password. I have done same procedure both side. still i am having same problem. Any one help on this. thanks, regards (3 Replies)
Discussion started by: vijill
3 Replies
7. Shell Programming and Scripting
Hello Friends,
I know this issue has been raised many times and hence I tried every resolution provided in the forum before I posted this issue again.
My Password-less RSA authentication was working fine for quite some time. Whenever the remote server password used to change I used to re-do... (5 Replies)
Discussion started by: mehimadri
5 Replies
8. Solaris
Hi,
I am facing strange problem in solaris 10.
My requirement is that on server A using user test, any user which is created on Server B will be able to login wihtout password (ssh) from Server A
All the users which are on Server B are able able to login from Server A using test user.
... (8 Replies)
Discussion started by: manoj.solaris
8 Replies
9. Red Hat
Hi all,
Hereby wish to have your advise for below:
Main concept is
I intend to get current directory of my script file.
This script file will be copied to /etc/init.d.
A string in this copy will be replaced with current directory value.
Below is original script file:
... (6 Replies)
Discussion started by: cielle
6 Replies
10. UNIX for Dummies Questions & Answers
Hi!
Im trying to set access from ServerA(SunOS) to ServerB(Some custom Linux with Keyboard Interactive login) with SSH Keys. As a proof of concept I was able to do it between 2 virtual machines. Now in my real life scenario it isnt working.
I created the keys in ServerA, copied them to... (7 Replies)
Discussion started by: RedSpyder
7 Replies
LEARN ABOUT SUSE
mupdatetest
MUPDATETEST(1) General Commands Manual MUPDATETEST(1)
*
NAME
mupdatetest - interactive MUPDATE test program
SYNOPSIS
mupdatetest [ -p port ] [ -m mechanism ]
[ -a userid ] [ -u userid ] [ -k num ] [ -l num ]
[ -r realm ] [ -f file ] [ -n num ] [ -q ]
[ -c ] [ -i ] [ -o option=value ] [ -v ] hostname
DESCRIPTION
mupdatetest is a utility that allows you to authenticate to a MUPDATE server and interactively issue commands to it. Once authenticated you
may issue any MUPDATE command by simply typing it in. It is capable of multiple SASL authentication mechanisms and handles encryption lay-
ers transparently. This utility is often used for testing the operation of a mupdate server. Note that you must be an admin in order to
authenticate to an mupdate server.
OPTIONS
-p port
Port to connect to. If left off this defaults to mupdate as defined in /etc/services.
-m mechanism
Force mupdatetest 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 mupdatetest to not use any layer and specifying 1 will force it to use the integrity layer. By default the
maximum 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 fast reauth (e.g. DIGEST-MD5), if possible.
-q Enable MUPDATE COMPRESSion (before the last authentication attempt).
-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
mupdate(8)
CMU
Project Cyrus MUPDATETEST(1)