The user is prompted for the following:
signer The name of the signing server, for example signer.froop.com . The default is the default signer for the site: the value of SIGNER in the local network configuration database (see ndb (6)).
remote user name The name of the user for whom a certificate is to be obtained. The default is the current user name in /dev/user .
password The user's password. The password entered on the client must match the password previously stored on the server using changelogin (8), or a certificate will be refused.
save in file? The default is `no'. If the user responds `yes', the certificate is written directly to the file. Otherwise, getauthinfo becomes a file server, serving a secure temporary file bound over the file name above (because that is where applications look for it). The temporary will disappear if the name is unmounted, or Inferno is rebooted.
Note that the certificate will expire at or before expiry of the password entry on the signer.
The signer needs its own key to endorse the certificates that it gives to clients. If a user requests a certificate with getauthinfo (8) before the signer's key is created on the signer (eg, using createsignerkey (8)), then the request will be rejected with a suitable diagnostic by logind (8).
Machines that will be file servers must obtain a certificate and save the certificate in a key file named default , thus:
"getauthinfo default"The user invoking getauthinfo must be the same user who later runs svc (8) to start the machine's services.
/usr/ user /keyring/ net ! machine where a certificate is stored on a client machine
/usr/ user /keyring/default where a certificate is stored on a file server
/lib/ndb/local contains the default host name of the signer