Basically, the display is cut off! So if I were trying to install a new OS, it wouldn’t be very efficient since I’d have to guess what was on display; e.g. As it turns out, using the correct search phrase returns the answer. HINT: it’s a compatibility issue between the client and display scaling in Windows 10; e.g. mine was set to 150%. TLDR: The solution is to set display scaling to 100%, and then log out and in for the changes to take effect.

Excerpts from her recent post that resonates so well with me of late: Create clarity. To create the best working environment for your team, you must create clarity. Ensure psychological safety. Your success as a manager is contingent on how honest people are willing to be with you. Let go. When you’re an individual contributor, you’re used to doing everything yourself. The minute you become a manager, that changes. Well, easier said than done.

… but hey, better late than never! So I was just complaining about how PuTTY doesn’t seem to handle SSH keys (e.g. AWS, Azure) very well, and then I came to (belated) realization that because rsync can be used in Windows via Cygwin, so can ssh. Now I don’t waste time in a UI managing PuTTY profiles, generating PPKs, or fidding with regedit.exe to clean up cached host fingerprints. Try Cygwin, today.

For all those of you who have been trying to clear Putty’s cache of host fingerprints (Windows) for development or testing, here is the answer: Open the registry (regedit) Go to HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys Delete the rows that you need and presto! Nice, TIL.

I was trying to compile collectd on a old CentOS 6 host, and ./configure complained that rrdtool couldn’t be found; e.g., rrdtool . . . . . . . no (rrd.h not found) I’d intended to use rrdtool to collect instance-level metrics and then graph ’em out with CGP, so it was pretty annoying. TIL that you can use -ql to list the files installed by a particular binary; e.g.

A keylogger records when a key is pressed, when it is released, and whether any shift or special keys have been pressed. It is also recorded if, for example, a password is entered even if it is not displayed on the screen. There is no evidence that this keylogger has been intentionally implemented. Obviously, it is a negligence of the developers - which makes the software no less harmful. If the developer would just disable all logging, using debug-logs only in the development environment, there wouldn’t be problems with the confidentiality of the data of any user.