Searched hist:"88 c8bcce" (Results 1 – 1 of 1) sorted by relevance
| /freebsd/lib/libpam/modules/pam_krb5/ |
| H A D | pam_krb5.c | 88c8bcce Wed Nov 13 17:44:29 GMT 2002 Jacques Vidrine <nectar@FreeBSD.org> Use `krb5_get_err_text' instead of `error_message' so that instead of
e.g.
Unknown error: -1765328378
we get
Client not found in Kerberos database
Another way to accomplish this would have been to leave
`error_message' alone, but to explicitly load the Kerberos com_err
error tables. However, I don't really like the idea of a PAM module
dorking with global tables.
Approved by: re (jhb)
88c8bcce Wed Nov 13 17:44:29 GMT 2002 Jacques Vidrine <nectar@FreeBSD.org> Use `krb5_get_err_text' instead of `error_message' so that instead of
e.g.
Unknown error: -1765328378
we get
Client not found in Kerberos database
Another way to accomplish this would have been to leave
`error_message' alone, but to explicitly load the Kerberos com_err
error tables. However, I don't really like the idea of a PAM module
dorking with global tables.
Approved by: re (jhb)
88c8bcce Wed Nov 13 17:44:29 GMT 2002 Jacques Vidrine <nectar@FreeBSD.org> Use `krb5_get_err_text' instead of `error_message' so that instead of
e.g.
Unknown error: -1765328378
we get
Client not found in Kerberos database
Another way to accomplish this would have been to leave
`error_message' alone, but to explicitly load the Kerberos com_err
error tables. However, I don't really like the idea of a PAM module
dorking with global tables.
Approved by: re (jhb)
88c8bcce Wed Nov 13 17:44:29 GMT 2002 Jacques Vidrine <nectar@FreeBSD.org> Use `krb5_get_err_text' instead of `error_message' so that instead of
e.g.
Unknown error: -1765328378
we get
Client not found in Kerberos database
Another way to accomplish this would have been to leave
`error_message' alone, but to explicitly load the Kerberos com_err
error tables. However, I don't really like the idea of a PAM module
dorking with global tables.
Approved by: re (jhb)
88c8bcce Wed Nov 13 17:44:29 GMT 2002 Jacques Vidrine <nectar@FreeBSD.org> Use `krb5_get_err_text' instead of `error_message' so that instead of
e.g.
Unknown error: -1765328378
we get
Client not found in Kerberos database
Another way to accomplish this would have been to leave
`error_message' alone, but to explicitly load the Kerberos com_err
error tables. However, I don't really like the idea of a PAM module
dorking with global tables.
Approved by: re (jhb)
88c8bcce Wed Nov 13 17:44:29 GMT 2002 Jacques Vidrine <nectar@FreeBSD.org> Use `krb5_get_err_text' instead of `error_message' so that instead of
e.g.
Unknown error: -1765328378
we get
Client not found in Kerberos database
Another way to accomplish this would have been to leave
`error_message' alone, but to explicitly load the Kerberos com_err
error tables. However, I don't really like the idea of a PAM module
dorking with global tables.
Approved by: re (jhb)
88c8bcce Wed Nov 13 17:44:29 GMT 2002 Jacques Vidrine <nectar@FreeBSD.org> Use `krb5_get_err_text' instead of `error_message' so that instead of
e.g.
Unknown error: -1765328378
we get
Client not found in Kerberos database
Another way to accomplish this would have been to leave
`error_message' alone, but to explicitly load the Kerberos com_err
error tables. However, I don't really like the idea of a PAM module
dorking with global tables.
Approved by: re (jhb)
88c8bcce Wed Nov 13 17:44:29 GMT 2002 Jacques Vidrine <nectar@FreeBSD.org> Use `krb5_get_err_text' instead of `error_message' so that instead of
e.g.
Unknown error: -1765328378
we get
Client not found in Kerberos database
Another way to accomplish this would have been to leave
`error_message' alone, but to explicitly load the Kerberos com_err
error tables. However, I don't really like the idea of a PAM module
dorking with global tables.
Approved by: re (jhb)
|