simon-git: putty (main): Simon Tatham

[Commits to Tartarus hosted VCS]

TL;DR:
  1bcab77e Upgrade random_setup_special to use SHA-3.

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:           2020-12-27 08:33:40

commit 1bcab77eb1cda3db12ed457448c2bddf13127222
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=1bcab77eb1cda3db12ed457448c2bddf13127222;hp=79de16732a3ed0f8538840afd4a0bc6e26f538a7
Author: Simon Tatham <anakin at pobox.com>
Date:   Sun Dec 27 08:30:51 2020 +0000

    Upgrade random_setup_special to use SHA-3.
    
    The idea of the especially large RNG that we use in key generation is
    that it should have as much actual entropy as possible. The reason I
    based it on SHA-512 previously was that that was the hash function in
    our collection with the largest output. But that's no longer true!
    Among the SHA-3 family that I added for Ed448 purposes, we have a
    ready-made variant of SHAKE-256 that outputs a whopping 114 bytes of
    hash. I see no reason not to upgrade to that from SHA-512's 64 bytes.
    
    (I could probably extend it even further by manually making another
    SHA-3 variant specially for the purpose, but I don't know that it
    would be worth it. This is a one-line change which I think is already
    a positive step.)

 putty.h | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)