summaryrefslogtreecommitdiff
path: root/Assistant/Threads/PairListener.hs
Commit message (Collapse)AuthorAge
* hlintGravatar Joey Hess2012-09-13
|
* Remove trailing whitespaceGravatar Richard Hartmann2012-09-11
|
* fixed all pairing alert issuesGravatar Joey Hess2012-09-11
|
* fix combining of pairing alertsGravatar Joey Hess2012-09-11
|
* pairing works!!Gravatar Joey Hess2012-09-11
| | | | | | | | | Finally. Last bug fixes here: Send PairResp with same UUID in the PairReq. Fix off-by-one in code that filters out our own pairing messages. Also reworked the pairing alerts, which are still slightly buggy.
* keep track of the stage we're at in pairingGravatar Joey Hess2012-09-11
| | | | | This avoids us responding to our own pairing messages, as well as ignoring any out of order messages that might be received somehow.
* additional security sanity checks on pairing messagesGravatar Joey Hess2012-09-11
|
* add a UUID to pair requestsGravatar Joey Hess2012-09-11
| | | | | | | Pair requests the the same UUID are part of the same pairing session, which allows us to detect attempts to brute force the shared secret, as that will result in pair requests with the same UUID that are not verified with the right secret.
* handle stale PairAcksGravatar Joey Hess2012-09-11
|
* clean up authorized_keys handlingGravatar Joey Hess2012-09-11
| | | | | Including rollback of adding the key when a pairing response gets canceled by the user.
* pairing probably works now (untested)Gravatar Joey Hess2012-09-10
|
* responding to pair requests *almost* worksGravatar Joey Hess2012-09-10
|
* add an alert while a locally initiated pairing request is in progressGravatar Joey Hess2012-09-09
| | | | Has a button to cancel the request.
* pair request alert tweaksGravatar Joey Hess2012-09-09
|
* update pair request alert when button is pressedGravatar Joey Hess2012-09-09
|
* moved the PairStage inside the Verifiable dataGravatar Joey Hess2012-09-08
|
* add a PairDone messageGravatar Joey Hess2012-09-08
|
* first pass at alert buttonsGravatar Joey Hess2012-09-08
| | | | | | | | | They work fine. But I had to go to a lot of trouble to get Yesod to render routes in a pure function. It may instead make more sense to have each alert have an assocated IO action, and a single route that runs the IO action of a given alert id. I just wish I'd realized that before the past several hours of struggling with something Yesod really doesn't want to allow.
* add remote directory to pair requestGravatar Joey Hess2012-09-08
|
* filter out our own pairing requestsGravatar Joey Hess2012-09-08
| | | | | Due to being multicast, requests sent by one thread are received by the listener in another thread.
* fix build without pairing supportGravatar Joey Hess2012-09-08
|
* added pair listener threadGravatar Joey Hess2012-09-08