summaryrefslogtreecommitdiffstats
path: root/source3/libads/krb5_errs.c
Commit message (Collapse)AuthorAgeFilesLines
* s3-kerberos: only use krb5 headers where required.Günther Deschner2009-11-271-0/+1
| | | | | | | This seems to be the only way to deal with mixed heimdal/MIT setups during merged build. Guenther
* fix build on old Heimdal based systemsBjörn Jacke2009-03-191-5/+3
| | | | Signed-off-by: Günther Deschner <gd@samba.org>
* r23801: The FSF has moved around a lot. This fixes their Mass Ave address.Andrew Tridgell2007-10-101-2/+1
| | | | (This used to be commit 87c91e4362c51819032bfbebbb273c52e203b227)
* r23779: Change from v2 or later to v3 or later.Jeremy Allison2007-10-101-1/+1
| | | | | Jeremy. (This used to be commit 407e6e695b8366369b7c76af1ff76869b45347b3)
* r22701: Fix the krb5_nt_status error table and add the "no DCs found" mappingGerald Carter2007-10-101-2/+4
| | | | (This used to be commit 2ab617fbbffbd6bf98ee02150f62b87a2610531f)
* r21845: Refactor the sessionsetupX code a little to allow usJeremy Allison2007-10-101-0/+2
| | | | | | | | | | | | to return a NT_STATUS_TIME_DIFFERENCE_AT_DC error to a client when there's clock skew. Will help people debug this. Prepare us for being able to return the correct sessionsetupX "NT_STATUS_MORE_PROCESSING_REQUIRED" error with associated krb5 clock skew error to allow clients to re-sync time with us when we're eventually able to be a KDC. Jeremy. (This used to be commit c426340fc79a6b446033433b8de599130adffe28)
* r20536: In the offline PAM session close case the attempt to delete aGünther Deschner2007-10-101-0/+2
| | | | | | | non-existing krb5 credential cache should not generate an error. Guenther (This used to be commit 11c6f573af5c1d3387e60f3fc44b00e28cd87813)
* r20273: Map KRB5_KDCREP_SKEW to NT_STATUS_TIME_DIFFERENCE_AT_DC.Günther Deschner2007-10-101-0/+1
| | | | | | | | This gives much nicer error messages when failing to join due to clock skew. Guenther (This used to be commit 5c5a7611029ff1b630c53d4660578e188acf97f5)
* r17677: There is no need for a 2nd krb5_to_nt_status function, is there?Günther Deschner2007-10-101-0/+1
| | | | | | | Michael Adam/Volker, please check. Guenther (This used to be commit d0feb85781f69325ee70aff98370cfac037c4cc2)
* r15392: In most cases, this mapping is more appropriate. (I know, it is still aGünther Deschner2007-10-101-1/+1
| | | | | | | mess, but there is no way the get NTSTATUS from the edata yet). Guenther (This used to be commit be2bd3945c057a4ad72251f809cffbe4694a7e3d)
* r14074: Some cleanup; there is no point in declaring and mappingGünther Deschner2007-10-101-29/+6
| | | | | | | | KRB5KRB_ERR_RESPONSE_TOO_BIG when the krb5 library does not know about this. Guenther (This used to be commit 4a1a3c4808307e09fa8ff85da9a963a4a6f0e9ae)
* r13599: krb5 error codes are defined as long. Also for the other direction.Lars Müller2007-10-101-1/+1
| | | | (This used to be commit 7b8ea1499124d1e1efe325339419a66ab8885b38)
* r13597: krb5 error codes are defined as long.Lars Müller2007-10-101-1/+1
| | | | (This used to be commit bab8c156a464c1beaa022e0026184e0de84c0bf9)
* r13316: Let the carnage begin....Gerald Carter2007-10-101-0/+132
Sync with trunk as off r13315 (This used to be commit 17e63ac4ed8325c0d44fe62b2442449f3298559f)