1MUPDATETEST(1)              General Commands Manual             MUPDATETEST(1)
2
3
4
5 *
6

NAME

8       mupdatetest - interactive MUPDATE test program
9

SYNOPSIS

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

DESCRIPTION

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

OPTIONS

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

SEE ALSO

80       mupdate(8)
81
82
83
84CMU                              Project Cyrus                  MUPDATETEST(1)
Impressum