summaryrefslogtreecommitdiffstats
path: root/checks/genkey1024.test
diff options
context:
space:
mode:
authorWerner Koch <wk@gnupg.org>1998-09-14 15:02:45 +0200
committerWerner Koch <wk@gnupg.org>1998-09-14 15:02:45 +0200
commit02922b7ab8a60671fab165aeb2e45e66f8c15847 (patch)
treef4c34105c3749d218b75122f93f83fcdb61e205f /checks/genkey1024.test
parent. (diff)
downloadgnupg2-02922b7ab8a60671fab165aeb2e45e66f8c15847.tar.xz
gnupg2-02922b7ab8a60671fab165aeb2e45e66f8c15847.zip
.
Diffstat (limited to '')
-rwxr-xr-xchecks/genkey1024.test28
1 files changed, 14 insertions, 14 deletions
diff --git a/checks/genkey1024.test b/checks/genkey1024.test
index f963cf356..95093895d 100755
--- a/checks/genkey1024.test
+++ b/checks/genkey1024.test
@@ -7,7 +7,7 @@ expect - <<EOF
set timeout 5
match_max 100000
spawn ../g10/gpg --no-batch --quick-random --homedir . --gen-key
-expect {
+expect {
-exact "Please select what kind of key you want:\r
(1) DSA and ElGamal (default)\r
(2) ElGamal (sign and encrypt)\r
@@ -18,18 +18,18 @@ Your selection? " { send -- "1\r" }
timeout { exit 1 } }
expect {
-exact "1\r
-\r \rDSA keypair will have 1024 bits.\r
+\r \rDSA keypair will have 1024 bits.\r
About to generate a new ELG-E keypair.\r
- minimum keysize is 768 bits\r
- default keysize is 1024 bits\r
+ minimum keysize is 768 bits\r
+ default keysize is 1024 bits\r
highest suggested keysize is 2048 bits\r
What keysize do you want? (1024) " { send -- "\r" }
timeout { exit 1 } }
expect {
-exact "\r
-\r \rRequested keysize is 1024 bits\r
+\r \rRequested keysize is 1024 bits\r
Please specify how long the key should be valid.\r
- 0 = key does not expire\r
+ 0 = key does not expire\r
<n> = key expires in n days\r
<n>w = key expires in n weeks\r
<n>m = key expires in n months\r
@@ -38,9 +38,9 @@ Key is valid for? (0) " { send -- "1\r" }
timeout { exit 1 } }
expect {
-exact "1\r
-\r \rKey expires at " { }
+\r \rKey expires at " { }
timeout { exit 1 } }
-expect {
+expect {
-re "(.*)\r
" {}
timeout { exit 1 } }
@@ -49,7 +49,7 @@ expect {
timeout { exit 1 } }
expect {
-exact "y\r
-\r \r\r
+\r \r\r
You need a User-ID to identify your key; the software constructs the user id\r
from Real Name, Comment and Email Address in this form:\r
\"Heinrich Heine (Der Dichter) <heinrichh@duesseldorf.de>\"\r
@@ -58,29 +58,29 @@ Real name: " { send -- "Harry H.\r" }
timeout { exit 1 } }
expect {
-exact "Harry H.\r
-\r \rEmail address: " { send -- "hh@ddorf.de\r" }
+\r \rEmail address: " { send -- "hh@ddorf.de\r" }
timeout { exit 1 } }
expect {
-exact "hh@ddorf.de\r
-\r \rComment: " { send -- "a test\r" }
+\r \rComment: " { send -- "a test\r" }
timeout { exit 1 } }
expect {
-exact "a test\r
-\r \rYou selected this USER-ID:\r
+\r \rYou selected this USER-ID:\r
\"Harry H. (a test) <hh@ddorf.de> (INSECURE!)\"\r
\r
Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? " { send -- "o\r" }
timeout { exit 1 } }
expect {
-exact "o\r
-\r \rYou need a Passphrase to protect your secret key.\r
+\r \rYou need a Passphrase to protect your secret key.\r
\r
Enter pass phrase: " { sleep 1; send -- "abc\r" }
timeout { exit 1 } }
expect {
-ex "\r \rRepeat pass phrase: " { sleep 1; send -- "abc\r" }
timeout { exit 1 } }
-expect {
+expect {
-ex "\r \rWe need to generate a lot of random bytes. It is a good idea to perform\r
some other action (work in another window, move the mouse, utilize the\r
network and the disks) during the prime generation; this gives the random\r