frosix

Multiparty signature service (experimental)
Log | Files | Refs | README | LICENSE

glossary.tex (3497B)

      1 \newglossaryentry{provider}{
      2   name={Frosix service provider},
      3   description={A webserver, running Frosix on it and exposing a RESTful interface to interact with.},
      4   plural={frosix service providers}
      5 }
      6 
      7 \newglossaryentry{client}{
      8   name={Frosix client},
      9   description={A client application which allows a user to use Frosix.}
     10 }  
     11 
     12 \newglossaryentry{nonce}{
     13   name={nonce},
     14   description={A nonce (number used once) is usually a high-entropy value which is only used once.},
     15   plural={nonces}
     16 }
     17 
     18 \newglossaryentry{secret server salt}{
     19   name={secret server salt},
     20   description={A secret, high entropy source of entropy of a Frosix service provider to protect against a bad random attack.},
     21   plural={secret server salts}
     22 }
     23 
     24 \newglossaryentry{trusted dealer}{
     25   name={trusted dealer},
     26   description={A trusted dealer is a central party in a secret sharing system, who divides and distributes a secret and has therefore, as the only one, knowledge of the secret.}
     27 }
     28 
     29 \newglossaryentry{zero knowledge proof}{
     30   name={zero knowledge proof},
     31   description={Proof of knowing a secret, without revealing any information of it. Also known under the term proof of knowledge.}
     32 }
     33 
     34 \newglossaryentry{salt}{
     35   name={salt},
     36   description={A salt is used in hashing as an additional high-entropy input to prevent brute-forcing of e.g. a low-entropy value.},
     37   plural={salts}
     38 }
     39 
     40 \newglossaryentry{brute-force}{
     41   name={brute-force},
     42   description={Brute-forcing is a exhaustive search, in which every possible value is checked for example to crack a password.},
     43 }
     44 
     45 \newglossaryentry{struct}{
     46   name={struct},
     47   description={In the programming language C, structs are a way to group several related variables into one object.},
     48   plural={structs},
     49 }
     50 
     51 \newglossaryentry{authentication hash}{
     52   name={authentication hash},
     53   description={In Frosix, the authentication hash is stored in the database from a Frosix service provider. It is used to authenticate a user.}
     54 }
     55 
     56 \newglossaryentry{authentication data}{
     57   name={authentication data},
     58   description={Authentication data includes data like a phone number or an email address (where to send a challenge-code).}
     59 }
     60 
     61 \newglossaryentry{authentication method}{
     62   name={authentication method},
     63   description={The authentication method describes the method which is used to authenticate a user.}
     64 }
     65 
     66 \newglossaryentry{authentication nonce}{
     67   name={authentication nonce},
     68   description={In order to hash the authentication data, which normally has a low-entropy value as input, another high-entropy input is needed.}
     69 }
     70 
     71 \newglossaryentry{context string}{
     72   name={context string},
     73   description={A context string is similar to a seed or a nonce. It serves as high-entropy input for hashing or key derivation.}
     74 }
     75 
     76 \newglossaryentry{seed}{
     77   name={seed},
     78   description={A seed is used in a function which outputs pseudorandom data, e.g. a key derivation function, to achieve the same output several times.}
     79 }
     80 
     81 \newglossaryentry{commitment}{
     82   name={commitment},
     83   description={With a commitment, it is possible to fix a specific value without revealing it. Useful in multiparty computation, if each participant should contribute a value, without knowing beforehand what the other values are.}
     84 }
     85 
     86 \newglossaryentry{challenge-code}{
     87   name={challenge-code},
     88   description={In order to use authentication with different devices and over different channels, a challenge-code is used. If the user can present the correct challenge-code, he is authorized to issue a signature.}
     89 }