Plasma GitLab Archive
Projects Blog Knowledge

Module Netmech_scram_gssapi

module Netmech_scram_gssapi: sig .. end

The SCRAM security mechanism for GSS-API

This module needs the SHA-1 hash function. In order to use it, initialize crypto support, e.g. by including the nettls-gnutls packages and calling Nettls_gnutls.init.

See RFC 5802

val scram_mech : Netsys_gssapi.oid


class type client_key_ring = object .. end

A client_key_ring identifies the user on the client side

class type server_key_verifier = object .. end

A server_key_verifier verifies on the server side that the users exist and have the right authentication credentials

val scram_gss_api : ?client_key_ring:client_key_ring ->
?server_key_verifier:server_key_verifier ->
Netmech_scram.profile -> (module Netsys_gssapi.GSSAPI)

Returns a standard-compliant GSS-API object for the passed SCRAM profile. The object can be used on the client side for all users whose passwords are available via client_key_ring. By default, the key ring is empty. On the server side, the object authenticates all users whose credentials are available via server_key_verifier. By default, no user can be verified.

SCRAM only allows usernames of type NT_USER_NAME for identifying users.

For principals (servers), this SCRAM implementation allows identifiers of type NT_HOSTBASED_SERVICE and NT_USER_NAME. Any such name can be used, because the SCRAM protocol does not use principal names. The contexts will always return the hostbased service "@" as name of the principals.

This implementation checks whether the messages are verified and unwrapped in the same order than generated, and reports this via the `Unseq_token and `Gap_token flags. Support for true replay detection (`Duplicate_token) is not implemented, though. Replayed tokens will also be marked as `Unseq_token.

This web site is published by Informatikbüro Gerd Stolpmann
Powered by Caml