rxrpc: Use correct timestamp from Kerberos 5 ticket
authorDavid Howells <dhowells@redhat.com>
Tue, 29 Aug 2017 09:15:40 +0000 (10:15 +0100)
committerDavid Howells <dhowells@redhat.com>
Tue, 29 Aug 2017 09:55:06 +0000 (10:55 +0100)
When an XDR-encoded Kerberos 5 ticket is added as an rxrpc-type key, the
expiry time should be drawn from the k5 part of the token union (which was
what was filled in), rather than the kad part of the union.

Reported-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: David Howells <dhowells@redhat.com>
net/rxrpc/key.c

index e2d3661..e7f6b88 100644 (file)
@@ -536,7 +536,7 @@ static int rxrpc_preparse_xdr_rxk5(struct key_preparsed_payload *prep,
             pptoken = &(*pptoken)->next)
                continue;
        *pptoken = token;
-       expiry = rxrpc_u32_to_time64(token->kad->expiry);
+       expiry = rxrpc_u32_to_time64(token->k5->endtime);
        if (expiry < prep->expiry)
                prep->expiry = expiry;