1 .\" Copyright 2002 walter harms (walter.harms@informatik.uni-oldenburg.de)
2 .\" Distributed under GPL
3 .\" I had no way the check the functions out
5 .TH KEY_SETSECRET 3 2002-07-18 "secure rpc"
7 key_decryptsession, key_encryptsession, key_setsecret, key_gendes,
8 key_secretkey_is_set \- interfaces to rpc keyserver daemon
11 .BR "#include <rpc/rpc.h>"
13 .BI "int key_decryptsession(const char *" remotename ,
14 .BI "des_block *" deskey );
16 .BI "int key_encryptsession(const char *" remotename ,
17 .BI "des_block *" deskey );
19 .BI "int key_gendes(des_block *" deskey );
21 .BI "int key_setsecret(const char *" key );
23 .B "int key_secretkey_is_set(void);"
26 The functions here are used within the RPC's secure authentication
27 mechanism (AUTH_DES). There should be no need for user programs to
31 .BR key_decryptsession ()
32 uses the (remote) server netname and takes the DES key
33 for decrypting. It uses the public key of the server and the
34 secret key associated with the effective UID of the calling process.
37 .BR key_encryptsession ()
39 .BR key_decryptsession ().
40 It encrypts the DES keys with the public key of the server and
41 the secret key associated with the effective UID of the calling process.
45 is used to ask the keyserver for a secure conversation key.
49 is used to set the key for the effective UID of the calling process.
52 .BR key_secretkey_is_set ()
53 can be used to determine whether a key has been
54 set for the effective UID of the calling process.
57 Please note that we talk about two types of encryption here. One is
58 asymmetric using a public and secret key. The other is symmetric, the
61 The routines were part of the linux/doors-project, abandoned by now.
64 The functions return 1 on success and 0 on failure.