diff options
author | Joey Hess <joey@kitenet.net> | 2012-09-08 15:42:12 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2012-09-08 15:42:12 -0400 |
commit | e6e0877378af85293356b1c7d644a6df6cc40415 (patch) | |
tree | 498f7f3791a7187b6755c715463be9194e9ce2bb /doc | |
parent | 317ab14da283e8ff88a45b036fb3aee9f5b4083f (diff) |
blog for the day
Diffstat (limited to 'doc')
-rw-r--r-- | doc/design/assistant/blog/day_76__pairing.mdwn | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/design/assistant/blog/day_76__pairing.mdwn b/doc/design/assistant/blog/day_76__pairing.mdwn new file mode 100644 index 000000000..0ebf55090 --- /dev/null +++ b/doc/design/assistant/blog/day_76__pairing.mdwn @@ -0,0 +1,16 @@ +About half way done with implementing [[pairing]]. The webapp's interface +to prompt for a secret and start pairing is done; the protocol is +implemented; broadcasting of pairing requests is working; added Yet Another +Thread to listen for incoming pairing traffic. + +Very happy with how this came together; starting with defining the protocol +with data types let me rapidly iterate until I had designed a simple, clean, +robust protocol. The implementation works well too; it's even possible to +start pairing, and only then bring up the network interface to the machine +you intended to pair with, and it'll detect the new interface and start +sending requests to it. + +Next, I need to make alerts have a button that performs a stored +IO action. So that the incoming pair request alert can have a button to +respond to the pair request. And then I need to write the code to actually +perform the pairing, including ssh key setup. |