Commit f6ac460a authored by Sietse Ringers's avatar Sietse Ringers
Browse files

docs: mention estimated cpu, memory and time costs in keyproof help texts

parent 86589cb8
......@@ -25,7 +25,11 @@ var issuerKeyproveCmd = &cobra.Command{
The keyprove command generates a proof that an issuer private/public keypair was generated
correctly. By default, it acts on the newest keypair in the <path>/PrivateKeys and <path>/PublicKeys
folders, and then stores the proof in the <path>/Proofs folder. If not specified, <path> is taken to
be the current working directory.`,
be the current working directory.
For 2048 bit keys, keyprove will output a proof of about 700 MB. On machines of 2 - 3 GHz generating
will take some 5 - 15 minutes, during which CPU usage will be 100% most of the time. Up to 8 GB RAM
may be used.`,
Args: cobra.MaximumNArgs(1),
Run: func(cmd *cobra.Command, args []string) {
flags := cmd.Flags()
......
......@@ -23,7 +23,10 @@ var issuerKeyverifyCmd = &cobra.Command{
The keyverify command verifies a proof of validity for an IRMA issuer private/public keypair. By
default, it verifies the newest proof in the <path>/Proofs folder, matching it to the corresponding
key in <path>/PublicKeys. If not specified, <path> is taken to be the current working directory.`,
key in <path>/PublicKeys. If not specified, <path> is taken to be the current working directory.
On machines of 2 - 3 GHz verification will take some 5 - 15 minutes, during which CPU usage will be
100% most of the time. Up to 8 GB RAM may be used.`,
Args: cobra.MaximumNArgs(1),
Run: func(cmd *cobra.Command, args []string) {
flags := cmd.Flags()
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment