From 0c01348b65bb3d0364f90ce9785236fa05985f75 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sat, 8 Sep 2012 02:02:39 -0400 Subject: pairing passphrase entry form, validation, etc Actually 3 forms in one, this handles the initial passphrase entry, and the confirmation, and also varys wording if the same user or a different user is confirming. --- templates/configurators/pairing.hamlet | 50 +++++++++++++++++++++++++++++ templates/configurators/repositories.hamlet | 3 +- 2 files changed, 52 insertions(+), 1 deletion(-) create mode 100644 templates/configurators/pairing.hamlet (limited to 'templates') diff --git a/templates/configurators/pairing.hamlet b/templates/configurators/pairing.hamlet new file mode 100644 index 000000000..4aa1cdbb0 --- /dev/null +++ b/templates/configurators/pairing.hamlet @@ -0,0 +1,50 @@ +
+

+ Pairing with a local computer +

+ $if start + Pair with a computer on your local network (or VPN), and the # + two git annex repositories will be combined into one, with changes # + kept in sync between all paired devices. + $else + Pairing with #{username}@#{hostname} will combine the two git annex # + repositories into one, with changes kept in sync between them. +

+ $if start + For security, enter a secret phrase. This same secret phrase will # + also need to be entered on the computer you're pairing with. # + It will be used to verify you're pairing with the right computer. + $else + $if sameusername + For security, you need to enter the same secret phrase that was # + entered on #{hostname} when the pairing was started. + $else + For security, a secret phrase has been selected, which you need # + to enter here to complete the pairing. If you don't know the # + phrase, go ask #{username} ... + $if badphrase +

+ #{msg} +

+

+
+ ^{form} + ^{authtoken} +
+