simon-git: putty (main): Simon Tatham

Commits to Tartarus hosted VCS tartarus-commits at lists.tartarus.org
Sat Apr 3 10:46:41 BST 2021


TL;DR:
  c1334f3b Unix Pageant: revise --encrypted and -E CLI options.

Repository:     https://git.tartarus.org/simon/putty.git
On the web:     https://git.tartarus.org/?p=simon/putty.git
Branch updated: main
Committer:      Simon Tatham <anakin at pobox.com>
Date:           2021-04-03 10:46:41

commit c1334f3b083a81e49639bb48125e8817e5ba0721
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=c1334f3b083a81e49639bb48125e8817e5ba0721;hp=bd5d80b4f6221a612f836b20c948163242969203
Author: Simon Tatham <anakin at pobox.com>
Date:   Sat Apr 3 10:30:27 2021 +0100

    Unix Pageant: revise --encrypted and -E CLI options.
    
    I've decided that it was a mistake to use -E as the option for adding
    keys encrypted, because it's better to use it as a fingerprint type
    selector for the Pageant client side. That way it works the same as
    command-line PuTTYgen, and also OpenSSH ssh-add (and ssh-keygen).
    
    What spelling(s) to use instead for the option to add keys encrypted?
    Obviously, the same ones I've just decided on for Windows Pageant;
    there's no sensible reason to make them different.

 unix/uxpgnt.c | 13 ++++++++++---
 1 file changed, 10 insertions(+), 3 deletions(-)



More information about the tartarus-commits mailing list