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

NAME

6       sivtest - interactive MANAGESIEVE test program
7

SYNOPSIS

9       sivtest [ -t keyfile ] [ -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       sivtest  is  a utility that allows you to authenticate to a MANAGESIEVE
16       server and interactively issue commands to it. Once  authenticated  you
17       may issue any MANAGESIEVE command by simply typing it in. It is capable
18       of multiple SASL authentication mechanisms and handles encryption  lay‐
19       ers transparently. This utility is often used for testing the operation
20       of a timsieved server. Also those developing MANAGESIEVE  clients  find
21       it useful.
22

OPTIONS

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

SEE ALSO

81       timsieved(8)
82
83
84
85CMU                              Project Cyrus                      SIVTEST(1)
Impressum