10 More Discussions You Might Find Interesting
1. Forum Support Area for Unregistered Users & Account Problems
Registration process refused two user names.
I may have already registered here and
it's kicking me out because of email address but
giving me username msg.
What's the solution to this?
Thanks (0 Replies)
Discussion started by: Unregistered
Hey everyone. I was at my local star bucks, which has open free wifi. And I (against my better judgement) deceided to check my school email. I was using their wifi network. when I went to go login, I was presented with the safari prompt "Can not Verify Server identity". I clicked 'details' and... (1 Reply)
Discussion started by: Lost in Cyberia
I have two servers with a fresh install of Solaris 11, and having problems when doing rpcinfo between them. There is no firewall involved, so everything should theoretically be getting through. Does anyone have any ideas? I did a lot of Google searches, and haven't found a working solution yet.
... (2 Replies)
Discussion started by: christr
4. UNIX Desktop Questions & Answers
I have two Solaris 10 systems, A and B, both of which share home directories via NFS (served from a 3rd, Linux, machine). User names, uids, and home directories are identical when the same user has accounts on both Solaris 10 machines.
When I run ssh -X user@A from my home machine, I can easily... (0 Replies)
Discussion started by: WolfyPDX
5. Forum Support Area for Unregistered Users & Account Problems
There was a problem with the site servicing our spam address checking. As a result all registrations were being rejected. If you have encountered this problem please try again and you should be permitted to join. (0 Replies)
Discussion started by: reborg
6. UNIX for Advanced & Expert Users
Hi - I am getting the error
`Error reading response length from authentication socket'
when I ssh from my cluster to another cluster, and then back to my cluster. It doesn't seem to affect anything, but it's just annoying that it always pops up and tends to confuse new users of the cluster. I... (1 Reply)
Discussion started by: cpp6f
Running as cron, I get error msg in mail: KERBEROS_V4 rejected as an authentication type,
even though the ftp does work. Can anyone explain this? Is there a way to stop it?
35 6 * * 1-5 ./PSS/pss.sh >> ./PSS/pss.log
DIR=/home/informix/PSS... (0 Replies)
Discussion started by: ejaggers
8. Shell Programming and Scripting
#FTP concatenated file
ftp -n $HOST <<END_SCRIPT
quote USER $USER
quote PASS $PASSWD
get $ifile retrieval.$$
echo "FTP of... (2 Replies)
Discussion started by: Sgiri1
9. UNIX for Dummies Questions & Answers
I'm getting the following Error:
prepare_pcap.c: In function `prepare_pkts':
prepare_pcap.c:127: error: dereferencing pointer to incomplete type
prepare_pcap.c:138: error: dereferencing pointer to incomplete type
This is the part of the relevant... (8 Replies)
Discussion started by: katwala
10. Forum Support Area for Unregistered Users & Account Problems
To Whom It May Concern,
I've tried registering, and am unable to do so. The message being returned is that my name choices are being rejected for not meeting some administrator criteria, which is not discernible from the message returned by the board software.
The password I chose was all... (1 Reply)
Discussion started by: username_in_use
MUPDATETEST(1) General Commands Manual MUPDATETEST(1)
mupdatetest - interactive MUPDATE test program
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
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.
Port to connect to. If left off this defaults to mupdate as defined in /etc/services.
Force mupdatetest to use mechanism for authentication. If not specified the strongest authentication mechanism supported by the
server is chosen.
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.
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.
Specify the realm to use. Certain authentication mechanisms (e.g. DIGEST-MD5) may require one to specify the realm.
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.
Set the SASL option to value.
-v Verbose. Print out more information than usual.
Project Cyrus MUPDATETEST(1)