1MUPDATETEST(1)              General Commands Manual             MUPDATETEST(1)
2
3
4

NAME

6       mupdatetest - interactive MUPDATE test program
7

SYNOPSIS

9       mupdatetest [ -p port ] [ -m mechanism ]
10                   [ -a userid ] [ -u userid ] [ -k num ] [ -l num ]
11                   [ -r realm ] [ -f file ] [ -n num ] [ -c ]
12                   [ -i ] [ -o option=value ] [ -v ] hostname
13

DESCRIPTION

15       mupdatetest  is  a utility that allows you to authenticate to a MUPDATE
16       server and interactively issue commands to it. Once  authenticated  you
17       may  issue any MUPDATE command by simply typing it in. It is capable of
18       multiple SASL authentication mechanisms and handles  encryption  layers
19       transparently.  This utility is often used for testing the operation of
20       a mupdate server. Note that you must be an admin in order to  authenti‐
21       cate to an mupdate server.
22

OPTIONS

24       -p port
25              Port  to  connect  to.  If  left off this defaults to mupdate as
26              defined in /etc/services.
27
28       -m mechanism
29              Force mupdatetest to use mechanism for  authentication.  If  not
30              specified  the  strongest  authentication mechanism supported by
31              the server is chosen.
32
33       -a userid
34              Userid to use for authentication; defaults to the current  user.
35              This  is  the  userid whose password or credentials will be pre‐
36              sented to the server for verification.
37
38       -u userid
39              Userid to use for authorization; defaults to the  current  user.
40              This  is the userid whose identity will be assumed after authen‐
41              tication.  NOTE: This is only used  with  SASL  mechanisms  that
42              allow proxying (e.g. PLAIN, DIGEST-MD5).
43
44       -k num Minimum protection layer required.
45
46       -l num Maximum protection layer to use (0=none; 1=integrity; etc).  For
47              example if you are using the KERBEROS_V4  authentication  mecha‐
48              nism  specifying  0  will force mupdatetest to not use any layer
49              and specifying 1 will force it to use the integrity  layer.   By
50              default the maximum supported protection layer will be used.
51
52       -r realm
53              Specify  the  realm  to  use.  Certain authentication mechanisms
54              (e.g. DIGEST-MD5) may require one to specify the realm.
55
56       -f file
57              Pipe file into connection after authentication.
58
59       -n num Number of authentication attempts; default = 1.  The client will
60              attempt to fast reauth (e.g. DIGEST-MD5), if possible.
61
62       -c     Enable  challenge  prompt  callbacks.   This  will cause the OTP
63              mechanism to ask for the the one-time password  instead  of  the
64              secret pass-phrase (library generates the correct response).
65
66       -i     Don't  send an initial client response for SASL mechanisms, even
67              if the protocol supports it.
68
69       -o option=value
70              Set the SASL option to value.
71
72       -v     Verbose. Print out more information than usual.
73

SEE ALSO

75       mupdate(8)
76
77
78
79CMU                              Project Cyrus                  MUPDATETEST(1)
Impressum