| /freebsd/crypto/openssh/regress/ |
| H A D | sshsig.sh | 178 trace "$tid: key type $t find-principals with valid lifespan"
179 ${SSHKEYGEN} -vvv -Y find-principals -s $sigfile \
182 fail "failed find-principals for $t key with valid expiry interval"
184 trace "$tid: key type $t find principals with not-yet-valid lifespan"
185 ${SSHKEYGEN} -vvv -Y find-principals -s $sigfile \
188 fail "failed find-principals for $t not-yet-valid key"
190 trace "$tid: key type $t find-principals with expired lifespan"
191 ${SSHKEYGEN} -vvv -Y find-principals -s $sigfile \
194 fail "failed find-principals for $t with expired key"
196 trace "$tid: key type $t find-principals with expired lifespan (now)"
[all …]
|
| H A D | cert-userkey.sh | 63 # Test explicitly-specified principals
152 # Setup for principals= key option
163 # Wrong principals list
164 verbose "$tid: ${_prefix} wrong principals key option"
166 printf 'cert-authority,principals="gregorsamsa" '
175 # Correct principals list
176 verbose "$tid: ${_prefix} correct principals key option"
178 printf 'cert-authority,principals="mekmitasdigoat" '
344 test_one "wrong principals" failure "-n foo"
351 # Behaviour is different here: TrustedUserCAKeys doesn't allow empty principals
[all …]
|
| H A D | principals-command.sh | 1 # $OpenBSD: principals-command.sh,v 1.14 2021/09/30 05:26:26 dtucker Exp $
4 tid="authorized principals command"
52 test $? -eq 0 || fatal "couldn't prepare principals command"
67 # Test explicitly-specified principals
139 # Setup for principals= key option
146 # Wrong principals list
147 verbose "$tid: wrong principals key option"
149 printf 'cert-authority,principals="gregorsamsa" '
158 # Correct principals list
159 verbose "$tid: correct principals key option"
[all …]
|
| /freebsd/crypto/krb5/src/windows/leash/htmlhelp/html/ |
| H A D | Manage_Multiple_Principals.htm | 6 <Title>Multiple Principals</Title>
9 <H1> Manage Multiple Principals </H1>
11 If you have multiple principals, several features in MIT Kerberos will help you manage them. </p>
13 <li>You can save principals when you enter them in the Get Ticket window. Kerberos will then auto-c…
19 All of your principals with tickets are listed in the main window. The default principal is in bold…
30 <li><a href=#manage-multiple> Manage multiple principals</a></li>
37 <li><a href="HTML/View_Tickets.htm"> View tickets for all principals</a></li>
46 <H2><a name="manage-multiple">Manage Multiple Principals</a></H2>
49 <th id="th2">Enter and save principals</th>
56 …he Home tab (e.g., Change Password). Note that you can select multiple principals before you click…
[all …]
|
| H A D | Forget_Principals.htm | 10 Kerberos saves your principals for you if you select "Remember this
11 principal" in the Get Ticket window. Saved principals then
20 … MIT Kerberos clears <em>all</em> of your saved principals. It is not possible to remove some prin…
36 <li><a href="HTML/Principals.htm">About principals</a></li>
37 <li><a href="HTML/Manage_Multiple_Principals.htm">Manage multiple principals</a></li>
|
| H A D | Principals.htm | 6 <Title>Principals</Title>
9 <H1> <a name="top">About Principals </a></H1>
19 <li><a href=#manage-multiple> Multiple principals</a></li>
36 <H2><a name="manage-multiple">Multiple principals</a></H2>
38 …principals. For example, administrators often have one principal with standard access and an admin…
40 …<a href="HTML/Manage_Multiple_Principals.htm">How to: Manage Multiple Principals</a> <br> <a href…
47 …ncipal, that principal is always the default. But if you have multiple principals you will need to…
51 When applications make a generic request, Kerberos does not know which of your principals is being …
|
| H A D | Make_Default.htm | 11 … plan to use an application, service, or network that only one of your principals has access to, f…
25 <li><a href="HTML/Principals.htm">About principals</a></li>
26 <li><a href="HTML/Manage_Multiple_Principals.htm">Manage multiple principals</a></li>
|
| H A D | Kerberos_Terminology.htm | 10 It is helpful to understand three terms when using Kerberos; <a href="#principal"> principals</a>, …
14 <th><a name="principal">Principals</a></th>
20 Principals are a combination of your user name and the name of the <a href="#realm"> realm</a> (or …
28 network resources that use Kerberos also have unique principals.
49 (or principals) in only one realm that provides you with all the access
50 you need, or you might have different principals for accessing
|
| H A D | Glossary.htm | 13 …ipal is always the default. <br><a href="HTML/Principals.htm#default-principal">About: Default Pr…
41 …beros. Principals are a combination of your user name and the name of the realm you belong to. <br…
|
| /freebsd/crypto/krb5/src/man/ |
| H A D | kadm5.acl.man | 38 For operations that affect principals, the ACL file also controls
39 which principals can operate on which other principals.
87 [Dis]allows the addition of principals or policies
93 [Dis]allows the changing of passwords for principals
99 [Dis]allows the deletion of principals or policies
111 [Dis]allows inquiries about principals or policies
117 [Dis]allows the listing of all principals or policies
123 [Dis]allows the modification of principals or policies
160 like those of the kadmin/* or krbtgt/* principals. The
162 key extraction from specific principals regardless of the
[all …]
|
| H A D | kdb5_ldap_util.man | 89 Specifies the list of subtrees containing the principals of a
94 Specifies the scope for searching the principals under the
99 Specifies the DN of the container object in which the principals
101 configured for a realm, the principals will be created in the
134 principals in this realm.
138 tickets for principals in this realm.
179 Specifies the list of subtrees containing the principals of a
184 Specifies the scope for searching the principals under the
189 container object in which the principals of a realm will be
194 principals in this realm.
[all …]
|
| H A D | kvno.man | 32 kvno \- print key version numbers of Kerberos principals
49 kvno acquires a service ticket for the specified Kerberos principals
84 interpreted as hostnames, and the service principals are to be
87 rules for constructing service principals.
|
| H A D | kadmin.man | 62 Kerberos principals, password policies, and service key tables
69 principals, and the \fB\-c\fP credentials_cache option is specified, that
103 Requests anonymous processing. Two types of anonymous principals
270 assign this policy to previously existing principals. This policy
390 prevent a malicious administrator from replacing principals like
391 krbtgt/* or kadmin/* with new principals without the attribute.
443 adding the principal, the principals are created under the
571 necessary except perhaps for \fBkrbtgt\fP principals.
804 locked. Authentication failures are only tracked for principals
869 principals.
[all …]
|
| H A D | kdb5_util.man | 142 [\fIprincipals\fP\&...]]
182 dumps in reverse order. This may recover principals that do not
187 This may recover principals that do not dump normally, in cases
189 corruption, this option will probably retrieve more principals
239 principals.
316 protect any principals. This command can be used to remove old master
341 version, and give a count at the end of the number of principals
|
| /freebsd/crypto/heimdal/doc/ |
| H A D | kerberos4.texi | 19 First, Kerberos 4 and Kerberos 5 principals are different. A version 4
25 principal. One notable example is the ``host'' type principals, where
27 version 5 name is @samp{host}. For the class of principals that has a
43 simplest cases you can cover most principals with the first rule. If you
54 @code{krb5_425_conv_principal_ext} to convert principals when handling
69 be because these principals are not used anymore, or it might be just
73 principals. For instance, if you are using DNS lookups and you have two
74 principals @samp{rcmd.foo} and @samp{rcmd.bar}, where `foo' is a CNAME
75 for `bar', the resulting principals will be the same. Since the
89 you have a database that consists of the following principals:
[all …]
|
| H A D | whatis.texi | 24 the network (users and services, usually called @dfn{principals}). All
25 principals share a secret password (or key) with the kerberos server and
26 this enables principals to verify that the messages from the kerberos
64 In Kerberos, principals use @dfn{tickets} to prove that they are who
72 checks that both @var{A} and @var{B} are valid principals.
74 Having verified the validity of the principals, it creates a packet
|
| /freebsd/crypto/openssh/regress/unittests/sshkey/ |
| H A D | test_sshkey.c | 61 struct sshbuf *ca_buf, *pk, *principals, *critopts, *exts; in build_cert() local
78 principals = sshbuf_new(); in build_cert()
79 ASSERT_PTR_NE(principals, NULL); in build_cert()
80 ASSERT_INT_EQ(sshbuf_put_cstring(principals, "gsamsa"), 0); in build_cert()
81 ASSERT_INT_EQ(sshbuf_put_cstring(principals, "gregor"), 0); in build_cert()
98 ASSERT_INT_EQ(sshbuf_put_stringb(b, principals), 0); /* principals */ in build_cert()
113 sshbuf_free(principals); in build_cert()
428 k1->cert->principals = calloc(4, sizeof(*k1->cert->principals)); in sshkey_tests()
429 ASSERT_PTR_NE(k1->cert->principals, NULL); in sshkey_tests()
430 k1->cert->principals[0] = strdup("estragon"); in sshkey_tests()
[all …]
|
| /freebsd/crypto/openssh/ |
| H A D | sshsig.c | 740 char *opts = NULL, *tmp, *cp, *principals = NULL; in parse_principals_key_and_options() local
764 if ((principals = strdup(tmp)) == NULL) { in parse_principals_key_and_options()
775 principals, 0) != 1) { in parse_principals_key_and_options()
818 *principalsp = principals; in parse_principals_key_and_options()
819 principals = NULL; /* transferred */ in parse_principals_key_and_options()
831 free(principals); in parse_principals_key_and_options()
841 char *cp, *oprincipals, *principals; in cert_filter_principals() local
847 oprincipals = principals = *principalsp; in cert_filter_principals()
855 while ((cp = strsep(&principals, ",")) != NULL && *cp != '\0') { in cert_filter_principals()
865 if (match_pattern(cert->cert->principals[i], cp)) { in cert_filter_principals()
[all …]
|
| H A D | auth2-pubkeyfile.c | 63 * Check keys/principals file expiry time. in auth_authorise_keyopts()
75 debug("%s: principals on non-CA key", loc); in auth_authorise_keyopts()
76 auth_debug_add("%s: principals on non-CA key", loc); in auth_authorise_keyopts()
155 if ((result = match_list(cert->principals[i], in match_principals_option()
201 debug("%s: bad principals options: %s", loc, reason); in auth_check_principals_line()
202 auth_debug_add("%s: bad principals options: %s", loc, reason); in auth_check_principals_line()
205 /* Check principals in cert against those on line */ in auth_check_principals_line()
207 if (strcmp(cp, cert->principals[i]) != 0) in auth_check_principals_line()
210 loc, cert->principals[i]); in auth_check_principals_line()
358 * If the user has specified a list of principals as in auth_check_authkey_line()
[all …]
|
| H A D | PROTOCOL.certkeys | 85 string valid principals
105 string valid principals
125 string valid principals
142 string valid principals
176 "valid principals" is a string containing zero or more principals as
177 strings packed inside it. These principals list the names for which this
180 zero-length "valid principals" field means the certificate is valid for
|
| H A D | ssh-keygen.1 | 124 .Op Fl n Ar principals
149 .Fl Y Cm find-principals
154 .Fl Y Cm match-principals
468 .It Fl n Ar principals
469 Specify one or more principals (user or host names) to be included in
471 Multiple principals may be specified, separated by commas.
695 .It Fl Y Cm find-principals
705 If one or more matching principals are found, they are returned on
707 .It Fl Y Cm match-principals
713 If one or more matching principals are found, they are returned on
[all …]
|
| /freebsd/crypto/heimdal/kadmin/ |
| H A D | kadmin.8 | 89 one or more principals as argument
97 matching principals.
149 Creates a keytab with the keys of the specified principals.
159 Lists the matching principals, short prints the result as a table,
171 just printing the names of matched principals.
281 Check database for strange configurations on important principals. If
314 the principals that had at least one strong encryption type
315 key should work and any keytabs for those principals should still work.
|
| H A D | kadmin-commands.in | 110 …help = "Initializes the default principals for a realm. Creates the database\nif necessary. Local …
221 help = "Changes the password of one or more principals matching the expressions."
230 help = "Deletes all principals matching the expressions."
260 …help = "Extracts the keys of all principals matching the expressions, and stores them in a keytab.…
294 help = "Shows information about principals matching the expressions."
348 help = "allowed target principals"
404 help = "Lists principals in a terse format. Equivalent to \"get -t\"."
|
| /freebsd/crypto/krb5/src/windows/leash/htmlhelp/ |
| H A D | TOC.hhc | 74 <param name="Name" value="Principals">
75 <param name="Local" value="HTML\Principals.htm">
79 <param name="Name" value="About Principals">
80 <param name="Local" value="HTML\Principals.htm">
83 <param name="Name" value="Manage Multiple Principals">
|
| /freebsd/crypto/heimdal/lib/krb5/ |
| H A D | krb5_425_conv_principal.3 | 41 .Nd converts to and from version 4 principals
53 Converting between version 4 and version 5 principals can at best be
63 the conversion between principals will have to be site customized.
72 principals, and if
|