Module Rpc_auth_dh

module Rpc_auth_dh: sig .. end

Diffie-Hellman authentication (AUTH_DH alias AUTH_DES)

This module implements DH authentication, the simplest form of Secure RPC. Despite its name, this form of authentication provides only a medium level of security, see below.

To use AUTH_DH you need the public-key infrastructure for Secure RPC. This requires that a special daemon, the so-called keyserv, runs on both the client's system and the server's system. The task of keyserv is to store public and private keys. We do not have a keyserv in Ocamlnet, so you must use the keyserv your system provides. (Note that keyserv is often distributed together with NIS+. However, you can run keyserv without needing to set up NIS+.)

In order to make a remote call, the keyserv daemon of the client must know the private key of the client user, and the public key of the server user. The keyserv daemon of the server must know the public key of the client user and the private key of the server user. Note that you can load a key pair into keyserv with the command keylogin. (This is not necessary for the root user, root's key pair is loaded at daemon startup time.)

See the manual pages of your OS for keyserv, keylogin, keylogout, and /etc/publickey.

Furthermore, it is strictly necessary that time synchronization is enabled between the client and the server. The recommended solution is to synchronize both clocks independently using a time normal (with NTP). Alternatively, the server can provide a time service on port 37 ("netdate").

To identify users, AUTH_DH uses so-called netnames. These have the form "<osflavor>.<user>@<domain>", where <osflavor> determines the kind of operating system (usually "unix"), <user> is an identifier for the user, and <domain> determines where the user identifiers are valid. In UNIX environments, the netnames are formed like:

• For root users: "unix.<hostname>@<nisdomain>"
• For non-privileged users: "unix.<uid>@<nisdomain>". Note that <uid> is the numeric user ID.

The keyserv daemon provides a service net_get that returns the netname of the calling user. AUTH_DH uses this service to determine the netname of the current process, but this does not hide netnames from the user of AUTH_DH:

• The client must know the netname of the server
• The server must interpret the netname of the client and decide whether the client user is authorized or not

How secure is AUTH_DH? As pointed out, the security is not the best.

• The chosen prime for DH is too short
• It uses DES (56 bits) to encrypt the verifiers

The DES weakness can be reduced by changing the conversation key frequently. This AUTH_DH implementation allows it to specify the maximum lifetime of a DES key.

Note that it is hard to attack AUTH_DH without knowing the public key. So it is best not to make it accessible for third parties.

val domainname : unit -> string

val client_auth_method : ?ttl:int ->
       ?getdeviation:(Unix.inet_addr -> float) ->
       ?key_lifetime:int ->
       ?keyserv:Rpc_key_service.connector -> string -> Rpc_client.auth_method

val server_auth_method : ?max_sessions:int ->
       ?max_ttl:int ->
       ?key_lifetime:int ->
       ?attack_detector:bool ->
       ?keyserv:Rpc_key_service.connector -> unit -> Rpc_server.auth_method