lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6075.1403687355@warthog.procyon.org.uk>
Date:	Wed, 25 Jun 2014 10:09:15 +0100
From:	David Howells <dhowells@...hat.com>
To:	Paul Bolle <pebolle@...cali.nl>
Cc:	dhowells@...hat.com, Jiri Kosina <trivial@...nel.org>,
	linux-afs@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [TRIVIAL] Documentation: Fix typo 'CONFIG_AFS'

Paul Bolle <pebolle@...cali.nl> wrote:

> Perhaps AF_RXRPC should be dropped from this short list (it is selected
> if AFS_FS is set). But since I couldn't actually determine how AFS_FS
> and RXKAD interact I decided to not touch that list any further.

The key_type_rxrpc key that the AFS fs or userspace passes to AF_RXRPC
indicates the protocol that AF_RXRPC should use.  The AFS fs doesn't need to
care how the security actually works and the token is opaque to it.

rxkad registers itself with AF_RXRPC, which maintains a list.  The
security_index is the number that appears in the protocol that indicates the
security driver to use.

David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ