simon-git: putty-wishlist (master): Simon Tatham
Commits to Tartarus CVS repository.
tartarus-commits at lists.tartarus.org
Mon May 18 12:34:08 BST 2015
TL;DR:
7933b28 Reorganise Pageant-related bug records.
Repository: git://git.tartarus.org/simon/putty-wishlist.git
On the web: http://tartarus.org/~simon-git/gitweb/?p=putty-wishlist.git
Branch updated: master
Committer: Simon Tatham <anakin at pobox.com>
Date: 2015-05-18 12:34:07
commit 7933b28fdb8a579b467d99e61a20a2e38d13c5cb
web diff http://tartarus.org/~simon-git/gitweb/?p=putty-wishlist.git;a=commitdiff;h=7933b28fdb8a579b467d99e61a20a2e38d13c5cb;hp=ae53f81472e430b4d044cd55dbcfdc5c15caa021
Author: Simon Tatham <anakin at pobox.com>
Date: Mon May 18 12:23:16 2015 +0100
Reorganise Pageant-related bug records.
I've removed 'pageant-key-mgmt' completely, and split it up into the
separate features 'pageant-deferred-decrypt' and 'pageant-timeout', as
well as adding 'pageant-forwarding-path' which I don't think we had a
record of before.
Also, 'pageant-async' has been deleted and replaced with
'pageant-named-pipe' and a completely new writeup, since most of the
old discussion was obsolete, I've had some new thoughts on possible
implementation strategies, and also I want to make it clearer that
this is a Windows-side problem only.
Finally, I've downgraded 'pageant-logging' from tricky to fun, on the
grounds that the new cross-platform Pageant code already has code to
generate log messages, so now it's just a matter of hooking that
existing code up to a Windows front end of some sort.
data/pageant-async | 111 -----------------------------------------
data/pageant-deferred-decrypt | 23 +++++++++
data/pageant-forwarding-path | 73 +++++++++++++++++++++++++++
data/pageant-key-mgmt | 28 -----------
data/pageant-logging | 10 ++--
data/pageant-named-pipe | 88 ++++++++++++++++++++++++++++++++
data/pageant-timeout | 18 +++++++
7 files changed, 208 insertions(+), 143 deletions(-)
More information about the tartarus-commits
mailing list