[OpenAFS-devel] Re: rxgk & rxk5 standards compliance

[Jeffrey Altman]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigDD72A529757C52FEA22FCB21
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

rxgk =3D=3D rx + gss-api + kerberos crypto (rfc 3961)

OpenAFS master builds an rfc 3961 module from hcrypto
which contains all of the crypto components for rxgk.
There is nothing there that you need to add to master.

As for rxk5.  It would need to be standardized before
it could be added to the openafs tree.

On 10/23/2012 11:00 PM, Troy Benjegerdes wrote:
> I would like some feedback on what sort of changes to:
>=20
> https://bitbucket.org/dahozer/tfs
>=20
> would be useful and/or relevant to helping standardize rxgk,
> and what I would need to do to support interoperability with
> the rxk5 patches I've forward ported.=20
>=20
> I would also like some guidance on what AES/SHA1 crypto
> implementation would be acceptable for merging to openafs-master.
>=20
> I have rxk5+k5ssl compiling on Debian for everything but the linux
> kernel module.
>=20



--------------enigDD72A529757C52FEA22FCB21
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iQEcBAEBAgAGBQJQh130AAoJENxm1CNJffh4yHAIAI4HjhvnZrthYCdAkatg+lLE
mZuIOY5gFtR9suBT4qCt5vzqmqEacGgegxGGjBiCDEnrzc7FV8aKqxtLlCnmxfPR
Ie8bZvkEOFQNynUNp7rT02VbOVA3vFth01gKQQamDqrUKlhZQJUJLeYry6qtPSkQ
FE2mHxN+oQOhde/Lj0LGSH6i3dwTour8DACHoTVJutdVwVHjvpud2Fra0zL6IafW
9vmeSt6/TfOR34zSfXfCHRdTW4c7Wy6WQIVYWr9O/7JSLmHwZrrs+e0SjtLEgC7J
hBBwVQnS1reVUaGOLLe8RoKCfBHdy/xlX755s7kTatkFxjwYM0nGhan4U/v3EQA=
=P/+6
-----END PGP SIGNATURE-----

--------------enigDD72A529757C52FEA22FCB21--