{"push_id":857474730,"size":123,"distinct_size":58,"ref":"refs/heads/putty-rdb","head":"af41db017bf13f110a598ca1729e4f1a6fda1302","before":"5ad17ba8f3431a6c577bb9c62eeb9eb887d88745","commits":[{"sha":"557a99e78e51e791eac0216aa5a4b01005ac5115","author":{"email":"7951276d108732f685ad39766351430a193de32d@pobox.com","name":"Simon Tatham"},"message":"Post-0.65 release checklist updates.\n\nThe -F option is no longer needed to bob in this situation; that\nhasn't been the directory I keep release announcements in for a long\ntime; the Docs page needs adjusting for pre-release retirement as well\nas the Downloads page.\n\n(cherry picked from commit 9bea08a298580c98889834cbaffe289301753989)","distinct":false,"url":"https://api.github.com/repos/rdebath/PuTTY/commits/557a99e78e51e791eac0216aa5a4b01005ac5115"},{"sha":"1f7f422d7aef019a6e17526f97ba9d15b56e78d3","author":{"email":"7951276d108732f685ad39766351430a193de32d@pobox.com","name":"Simon Tatham"},"message":"New centralised helper function dup_mb_to_wc().\n\nPuTTY's main mb_to_wc() function is all very well for embedding in\nfiddly data pipelines, but for the simple job of turning a C string\ninto a C wide string, really I want something much more like\ndupprintf. So here is one.\n\nI've had to put it in a new separate source file miscucs.c rather than\nthrowing it into misc.c, because misc.c is linked into tools that\ndon't also include a module providing the internal Unicode API (winucs\nor uxucs). The new miscucs.c appears only in Unicode-using tools.\n\n(cherry picked from commit 7762d7122609207059cf5cf58fb2b9c2de98dd36)","distinct":false,"url":"https://api.github.com/repos/rdebath/PuTTY/commits/1f7f422d7aef019a6e17526f97ba9d15b56e78d3"},{"sha":"3dfb9ac8851fda0599b32495099cb91c2bbf4a62","author":{"email":"7951276d108732f685ad39766351430a193de32d@pobox.com","name":"Simon Tatham"},"message":"Turn the Windows PuTTY main window into a Unicode window.\n\nThis causes WM_CHAR messages sent to us to have a wParam containing a\n16-bit value encoded in UTF-16, rather than an 8-bit value encoded in\nthe system code page.\n\nAs far as I can tell, there aren't many other knock-on effects - e.g.\nyou can still interact with the window using ordinary char-based API\nfunctions such as SetWindowText, and the Windows API will do the\nnecessary conversions behind the scenes. However, even so, I'm half\nexpecting some sort of unforeseen bug to show up as a result of this.\n\n(cherry picked from commit 67e5ceb9a8e6bc20fa0e0cf82ee9f89582e94112)","distinct":false,"url":"https://api.github.com/repos/rdebath/PuTTY/commits/3dfb9ac8851fda0599b32495099cb91c2bbf4a62"},{"sha":"d4e5b0dd1c2fbdc49bc5196918a489972349dc93","author":{"email":"7951276d108732f685ad39766351430a193de32d@pobox.com","name":"Simon Tatham"},"message":"Handle the VK_PACKET virtual key code.\n\nThis is generated in response to the SendInput() Windows API call, if\nthat in turn is passed an KEYBDINPUT structure with KEYEVENTF_UNICODE\nset. That method of input generation is used by programs such as\n'WinCompose' to send an arbitrary Unicode character as if it had been\ntyped at the keyboard, even if the keyboard doesn't actually provide a\nkey for it.\n\nLike VK_PROCESSKEY, this key code is an exception to our usual policy\nof manually translating keystrokes: we handle it by calling\nTranslateMessage, to get back the Unicode character it contains as a\nWM_CHAR message.\n\n(If that Unicode character in turn is outside the BMP, it may come\nback as a pair of WM_CHARs in succession containing UTF-16 surrogates;\nif so, that's OK, because the new Unicode WM_CHAR handler can cope.)\n\n(cherry picked from commit 65f3500906c38ee3cf66cc75a015058e5bc6e56d)","distinct":false,"url":"https://api.github.com/repos/rdebath/PuTTY/commits/d4e5b0dd1c2fbdc49bc5196918a489972349dc93"},{"sha":"d61c6cad0bb2854f88ced9bf7f347d81e33ec7a3","author":{"email":"7951276d108732f685ad39766351430a193de32d@pobox.com","name":"Simon Tatham"},"message":"Don't try to load GSSAPI libs unless we'll use them.\n\nA user reports that in a particular situation one of the calls to\nLoadLibrary from wingss.c has unwanted side effects, and points out\nthat this happens even when the saved session has GSSAPI disabled. So\nI've evaluated as much as possible of the condition under which we\ncheck the results of GSS library loading, and deferred the library\nloading itself until after that condition says we even care about the\nresults.\n\n(cherry picked from commit 9a08d9a7c10458356b934af54206f0b642ecf715)","distinct":false,"url":"https://api.github.com/repos/rdebath/PuTTY/commits/d61c6cad0bb2854f88ced9bf7f347d81e33ec7a3"},{"sha":"f59445004e8748d4be12066bb0511f7d06d4806a","author":{"email":"7951276d108732f685ad39766351430a193de32d@pobox.com","name":"Simon Tatham"},"message":"Work around a failure in Windows 10 jump lists.\n\nWe've had several reports that launching saved sessions from the\nWindows 10 jump list fails; Changyu Li reports that this is because we\ncreate those IShellLink objects with a command line string starting\nwith @, and in Windows 10 that causes the SetArguments method to\nsilently do the wrong thing.\n\n(cherry picked from commit 8bf5c1b31f1a1449d694e3604e293b0831eb2657)","distinct":false,"url":"https://api.github.com/repos/rdebath/PuTTY/commits/f59445004e8748d4be12066bb0511f7d06d4806a"},{"sha":"417421caced7a133a66a3a7bcd1e427457c85db3","author":{"email":"7951276d108732f685ad39766351430a193de32d@pobox.com","name":"Simon Tatham"},"message":"New formatting directive in logfile naming: &P for port number.\n\nUsers have requested this from time to time, for distinguishing log\nfile names when there's more than one SSH server running on different\nports of the same host. Since we do take account of that possibility\nin other areas (e.g. we cache host keys indexed by (host,port) rather\nthan just host), it doesn't seem unreasonable to do so here too.\n\n(cherry picked from commit 0550943b51c538400e31ce18483032e446178120)","distinct":false,"url":"https://api.github.com/repos/rdebath/PuTTY/commits/417421caced7a133a66a3a7bcd1e427457c85db3"},{"sha":"0eb3bf07fc3f89a7cec499f1730f48fa89a7d37f","author":{"email":"7951276d108732f685ad39766351430a193de32d@pobox.com","name":"Simon Tatham"},"message":"'pterm --display' should set $DISPLAY inside the terminal.\n\nIf you open a pterm on a different display via the --display\ncommand-line option rather than by setting $DISPLAY, I think (and\nother terminals seem to agree) that it's sensible to set $DISPLAY\nanyway for processes running inside the terminal.\n\n(cherry picked from commit dc16dd5aa4a3fb2e367bc6303963321e628594ac)","distinct":false,"url":"https://api.github.com/repos/rdebath/PuTTY/commits/0eb3bf07fc3f89a7cec499f1730f48fa89a7d37f"},{"sha":"14464764da5d86934169d17188534fbdc5fd4b5b","author":{"email":"7951276d108732f685ad39766351430a193de32d@pobox.com","name":"Simon Tatham"},"message":"Performance: cache character widths returned from Pango.\n\nProfiling reveals that pterm in Pango rendering mode uses an absurd\namount of CPU when it's not even actually _drawing_ the text, because\nof all the calls to pango_layout_get_pixel_extents() while\npangofont_draw_text tries to work out which characters it can safely\ndraw as part of a long string. Caching the results speeds things up\ngreatly.\n\n(cherry picked from commit c3ef30c883e3657ff57679fb611f1f6ee6f33dba)","distinct":false,"url":"https://api.github.com/repos/rdebath/PuTTY/commits/14464764da5d86934169d17188534fbdc5fd4b5b"},{"sha":"eb319f9b6e960b6c00a10c31c747ee484aad6ee1","author":{"email":"7951276d108732f685ad39766351430a193de32d@pobox.com","name":"Simon Tatham"},"message":"pterm: set IUTF8 on pty devices depending on charset.\n\nIn a UTF-8 pterm, it makes sense to set the IUTF8 flag (on systems\nthat have one) on the pty device, so that line editing will take\naccount of UTF-8 multibyte characters.\n\n(cherry picked from commit 1840103c05d10ba1c45353282b4ad7f742a75b92)","distinct":false,"url":"https://api.github.com/repos/rdebath/PuTTY/commits/eb319f9b6e960b6c00a10c31c747ee484aad6ee1"},{"sha":"a063e522970946bf7d5dc052079d7773c0dee76d","author":{"email":"7951276d108732f685ad39766351430a193de32d@pobox.com","name":"Simon Tatham"},"message":"Key rollover: rewrite the PGP keys manual appendix.\n\nThis gives pride of place to the new set of keys we've recently\ngenerated, and relegates the old ones to an afterthought.\n\n(cherry picked from commit bb68baf53bacfc71bb0144780cf0b2b63bd76f98)","distinct":false,"url":"https://api.github.com/repos/rdebath/PuTTY/commits/a063e522970946bf7d5dc052079d7773c0dee76d"},{"sha":"43865aa1615bf0ca65914344dbef85199d3130d0","author":{"email":"7951276d108732f685ad39766351430a193de32d@pobox.com","name":"Simon Tatham"},"message":"Key rollover: switch to signing using the new keys.\n\nsign.sh's command-line syntax has changed, so I've updated the sample\ncommand line in CHECKLST as well. Also the file extensions of the\nsignatures have changed, so I've updated the pre-release verification\ncommand line in CHECKLST too.\n\n(cherry picked from commit 11eb75a260ca1c6e48a19afe241d423f6e7b0e4e)","distinct":false,"url":"https://api.github.com/repos/rdebath/PuTTY/commits/43865aa1615bf0ca65914344dbef85199d3130d0"},{"sha":"aaeaae00a9e652afe5bf1300f00f45ef1904033d","author":{"email":"7951276d108732f685ad39766351430a193de32d@pobox.com","name":"Simon Tatham"},"message":"Key rollover: put the new Master Key fingerprint in the tools.\n\nFor the moment we're also retaining the old ones. Not sure when will\nbe the best time to get rid of those; after the next release, perhaps?\n\n(cherry picked from commit e88b8d21f2f7a73cd9e2f21bcb408b2abebd0667)","distinct":false,"url":"https://api.github.com/repos/rdebath/PuTTY/commits/aaeaae00a9e652afe5bf1300f00f45ef1904033d"},{"sha":"6c041657199a000e26b983c283648f080dae9f03","author":{"email":"7951276d108732f685ad39766351430a193de32d@pobox.com","name":"Simon Tatham"},"message":"Key rollover: add a checklist item for the Download page.\n\nNext time I do a release, I'll have to remember to adjust the download\npage links to the GPG signature files.\n\n(cherry picked from commit 7524da621b1689b3384020cd6d83c990ef86bfa1)","distinct":false,"url":"https://api.github.com/repos/rdebath/PuTTY/commits/6c041657199a000e26b983c283648f080dae9f03"},{"sha":"4252cdbd82605f8860b6914b7b158b9d4d68b9e5","author":{"email":"7951276d108732f685ad39766351430a193de32d@pobox.com","name":"Simon Tatham"},"message":"Key rollover: cut and paste errors in pgpkeys.but.\n\nWhat should have been links to the old DSA keys were actually a second\ncopy of the links to the old RSA ones. Ahem.\n\n(cherry picked from commit b62af0f40aa15c3ab79c8166c34f60f6e4192214)","distinct":false,"url":"https://api.github.com/repos/rdebath/PuTTY/commits/4252cdbd82605f8860b6914b7b158b9d4d68b9e5"},{"sha":"8c803e725e0b0071b5a454f423a805e1bd9b6be9","author":{"email":"7951276d108732f685ad39766351430a193de32d@pobox.com","name":"Simon Tatham"},"message":"Key rollover: fix the .htaccess files built by Buildscr.\n\nThe build script generates the .htaccess files that go in each\nindividual build and redirect generic names like 'putty.tar.gz' to the\nreal filenames including that build's version number. Those .htaccess\nfiles redirect the corresponding signatures as well, so they need\nupdating now that we're generating signature files with a different\nextension.\n\n(cherry picked from commit 6744387924835792147f73644e1eed10e146b5c8)","distinct":false,"url":"https://api.github.com/repos/rdebath/PuTTY/commits/8c803e725e0b0071b5a454f423a805e1bd9b6be9"},{"sha":"a815c3a8e1855e20e458571376039d36c5810642","author":{"email":"7951276d108732f685ad39766351430a193de32d@pobox.com","name":"Simon Tatham"},"message":"Fix spurious EAGAIN in Plink host key (and other) prompts.\n\nPlink sets standard input into nonblocking mode, meaning that read()\nfrom fd 0 in an interactive context will typically return -1 EAGAIN.\nBut the prompt functions in uxcons.c, used for verifying SSH host keys\nand suchlike, were doing an unguarded read() from fd 0, and then\npanicking and aborting the session when they got EAGAIN.\n\nFixed by inventing a wrapper around read(2) which handles EAGAIN but\npasses all other errors back to the caller. (Seemed slightly less\ndangerous than the stateful alternative of temporarily re-blockifying\nthe file descriptor.)\n\n(cherry picked from commit bea758a7ae0507e0d4a24b370f8401661cc1a2c8)\n\nConflicts:\n\tunix/uxcons.c\n\nCherry-picker's notes: the conflict was a trivial one. The new\nfunction block_and_read() by this commit appears just before\nverify_ssh_host_key(), which has a new prototype on the source branch,\nclose enough to disrupt the patch hunk's context. Easily fixed.","distinct":false,"url":"https://api.github.com/repos/rdebath/PuTTY/commits/a815c3a8e1855e20e458571376039d36c5810642"},{"sha":"31c5784d4b514becf0028f3b3d38d8e28305dad7","author":{"email":"7951276d108732f685ad39766351430a193de32d@pobox.com","name":"Simon Tatham"},"message":"Command-line options to log sessions.\n\nLog files, especially SSH packet logs, are often things you want to\ngenerate in unusual circumstances, so it's good to have lots of ways\nto ask for them. Particularly, it's especially painful to have to set\nup a custom saved session to get diagnostics out of the command-line\ntools.\n\nI've added options '-sessionlog', '-sshlog' and '-sshrawlog', each of\nwhich takes a filename argument. I think the fourth option (session\noutput but filtered down to the printable subset) is not really a\n_debugging_ log in the same sense, so it's not as critical to have an\noption for it.\n\n(cherry picked from commit 13edf90e0a4397088085cfcd53a4311319b708b4)","distinct":false,"url":"https://api.github.com/repos/rdebath/PuTTY/commits/31c5784d4b514becf0028f3b3d38d8e28305dad7"},{"sha":"fbea11f44b972ce48ae5912f9e30df4e0c03e8c9","author":{"email":"7951276d108732f685ad39766351430a193de32d@pobox.com","name":"Simon Tatham"},"message":"Shout more loudly if we can't open a log file.\n\nA user points out that logging fopen failures to the Event Log is a\nbit obscure, and it's possible to proceed for months in the assumption\nthat your sessions are being correctly logged when in fact the\npartition was full or you were aiming them at the wrong directory. Now\nwe produce output visibly in the PuTTY window.\n\n(cherry picked from commit e1628105163135ca21abb6a841d109969d7979ec)","distinct":false,"url":"https://api.github.com/repos/rdebath/PuTTY/commits/fbea11f44b972ce48ae5912f9e30df4e0c03e8c9"},{"sha":"5c76a93a44bdd0d6d15e644176a0257d9ce7bf9b","author":{"email":"7951276d108732f685ad39766351430a193de32d@pobox.com","name":"Simon Tatham"},"message":"Sanitise bad characters in log file names.\n\nOn Windows, colons are illegal in filenames, because they're part of\nthe path syntax. But colons can appear in automatically constructed\nlog file names, if an IPv6 address is expanded from the &H placeholder.\n\nNow we coerce any such illegal characters to '.', which is a bit of a\nbodge but should at least cause a log file to be generated.\n\n(cherry picked from commit 64ec5e03d5362ed036e9de1a765085c571eaa3b7)","distinct":false,"url":"https://api.github.com/repos/rdebath/PuTTY/commits/5c76a93a44bdd0d6d15e644176a0257d9ce7bf9b"}]}