{"push_id":1027252770,"size":1,"distinct_size":1,"ref":"refs/heads/putty","head":"0fadffe0cbd191c3125834a1445ebe1885a88295","before":"5c5879b99d2a0785095a384f48a2d934e1b2d4c5","commits":[{"sha":"0fadffe0cbd191c3125834a1445ebe1885a88295","author":{"email":"7951276d108732f685ad39766351430a193de32d@pobox.com","name":"Simon Tatham"},"message":"Add command-line passphrase-file options to command-line PuTTYgen.\n\nPatch due to Colin Watson.\n\nPutting the passphrase in a file avoids exposing it to 'ps' which can\nprint out every process's command line, while at the same time not\nbeing as platform-specific as the approach of providing an fd number\n(since cmdgen.c is in principle a potential cross-platform PuTTYgen,\nnot just a Unix one, which is why it's not in the 'unix' directory).\n\nOf course it introduces its own risks if someone can read the file\nfrom your disk after you delete it; probably the best approach to\navoiding this, if possible, is to point the option at a file on an\nin-memory tmpfs type file system. Or better still, use bash-style\n/dev/fd options such as\n\n  puttygen --new-passphrase <(echo -n \"my passphrase\") [options]\n\nFailing that, try a secure file-wipe utility, as the man page change\nmentions.\n\n(And a use case not to be overlooked, of course, is the one where you\nactually want to generate an unprotected key - in which case, just\npass /dev/null as the filename.)","distinct":true,"url":"https://api.github.com/repos/ranvis/putty/commits/0fadffe0cbd191c3125834a1445ebe1885a88295"}]}