1 # User configuration file for Shishi @VERSION@
2 # Copyright 2002, 2003 Simon Josefsson
4 # This file is free software; as a special exception the author gives
5 # unlimited permission to copy and/or distribute it, with or without
6 # modifications, as long as this notice is preserved.
8 # This file is distributed in the hope that it will be useful, but
9 # WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
10 # implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
12 # Unless you you specify which configuration file to use (with the
13 # commandline option "--configuration-file filename"), Shishi uses the
14 # file $HOME/.shishi/config by default. Note that the system
15 # configuration file is read before this file. Settings specified
16 # here overrides those specified in the system configuration file.
18 # An option file can contain all long options which are
19 # available in Shishi. If the first non white space character of
20 # a line is a '#', this line is ignored. Empty lines are also
23 # See the manual for a list of options.
25 # Read MIT or Heimdal configuration file for the following parameters:
31 # You can override these values by specifying alternate values below.
32 # Not implemented yet.
33 #read-krb5conf=/etc/krb5.conf
35 # Specify the default realm, by default the hostname of the host is used.
36 #default-realm JOSEFSSON.ORG
38 # Specify the default principal, by default the login username is used.
39 #default-principal jas
41 # Specify which encryption types client asks server to respond in
42 # during AS/TGS exchanges. List valid encryption types, in preference
43 # order. Supported algorithms include aes256-cts-hmac-sha1-96,
44 # aes128-cts-hmac-sha1-96, des3-cbc-sha1-kd, des-cbc-md5, des-cbc-md4,
45 # des-cbc-crc and null. This option also indicates which encryption
46 # types are accepted by the client when receiving the response. Note
47 # that the preference order is not cryptographically protected, so a
48 # man in the middle can modify the order without being detected.
49 # Thus, only specify encryption types you trust completely here. The
50 # default only includes aes256-cts-hmac-sha1-96, as suggested by
52 #client-kdc-etypes=aes256-cts-hmac-sha1-96 des3-cbc-sha1-kd des-cbc-md5
54 # Enable verbose library messages.
60 # Specify KDC addresses for realms.
61 # Value is REALM,KDCADDRESS[/PROTOCOL][,KDCADDRESS[/PROTOCOL]...]
62 # KDCADDRESS is the hostname or IP address of KDC.
63 # Optional PROTOCOL is udp for UDP, tcp for TCP, and TLS for TLS
64 # connections. By default UDP is tried first, and TCP used as a
65 # fallback if the KRB_ERR_RESPONSE_TOO_BIG error is received.
66 # If not specified, Shishi tries to locate the KDC using SRV RRs,
67 # which is recommended. This option should normally only be
68 # used during experiments, or to access badly maintained realms.
69 #realm-kdc=JOSEFSSON.ORG,ristretto.josefsson.org
71 # Specify realm for servers.
72 # Value is REALM,SERVERREGEXP[,SERVERREGEXP...]
73 # SERVERREGEXP is a regular expression matching servers in the realm.
74 # The first match is used.
75 #server-realm=JOSEFSSON.ORG,.josefsson.org
77 # How long shishi waits for a response from a KDC before continuing
78 # to next KDC for realm. The default is 5 seconds.
81 # How many times shishi sends a request to a KDC before giving up.
82 # The default is 3 times.
85 # How username and passwords entered from the terminal, or taken
86 # from the command line, are processed.
87 # "none": no processing is used.
88 # "stringprep": convert from locale charset to UTF-8 and process using
89 # experimental RFC 1510 stringprep profile.
90 # It can also be a string indicating a character set supported by
91 # iconv() via libstringprep, in which case data is converted from
92 # locale charset into the indicated character set. E.g., UTF-8,
93 # ISO-8859-1, KOI-8, EBCDIC-IS-FRISS are supported on GNU systems.
94 # On some systems you can use "locale -m" to list available character
95 # sets. By default, the "none" setting is used which is consistent
96 # with RFC 1510 that is silent on the issue. In practice, however,
97 # converting to UTF-8 improves interoperability.
100 # Specify default ticket life time.
101 # The string can be in almost any common format. It can contain month
102 # names, time zones, `am' and `pm', `yesterday', `ago', `next', etc.
103 # Refer to the "Date input formats" in the GNU CoreUtils package for
104 # entire story. As an extra feature, if the resulting string you
105 # specify has expired within the last 24 hours, an extra day is added
106 # to it. This allows you to specify "17:00" to always mean the next
107 # 17:00, even if your system clock happens to be 17:30.
108 # The default is 8 hours.
114 # Specify how long a renewable ticket should remain renewable.
115 # See ticket-life for the syntax. The extra feature that handles
116 # negative values within the last 2 hours is not active here.
117 # The default is 7 days.
120 #renew-life=friday 17:00
123 # User configuration file ends here