[MortyWaves]

Ever since Windows gained Terminal and OpenSSH, my usage of Putty has almost entirely ceased except for serial for embedded systems work.

Then I realised Putty ships with a CLI version which I now use in Terminal for accessing serial.

[throaway920181]

I haven't used Putty since I stopped using Windows for anything serious (in the early 00s.) It was my favorite quick and dirty SSH and serial client before then though!

[sshine]

I have to say, I liked SecureCRT a lot, too.

PuTTY was just easier to get ahold of on a new install.

I think that's why it won out for me. That and its simplicity.

[ZYbCRq22HbJ2y7]

I always used mingw and similar projects. IMO, putty was always annoying (but very useful) software. The "ecosystem" seems better now though.

[MortyWaves]

Indeed, that and “git bash” were always the weird outliers. I’m glad there’s now native options.

[account42]

One nice thing about putty is that it let's you specify the password on the command line. Can't stand software that doesn't let you make your own decisions.

[Helmut10001]

I don't trust Windows with my SSH keys. Since about 2 years, I am actively preparing my final migration to Linux. There's some Windows software left that I need to replace before this move is possible, but I am close.

[gregoryl]

Just pull the trigger. A surprisingly large amount of software just works on wine.

I'm a c# dev with near 20 years experience, and I finally got the shits with advertising in the start menu. Arch Linux, because I figured why not do it properly?

I game a fair bit, and find most things on steam just work.

[Bender]

I agree with you and just wanted to add that for what it's worth one can optionally limit where ssh keys are useful by adding network restrictions on the public key / server side. e.g.

    grep AuthorizedKeysFile /etc/ssh/sshd_config
    AuthorizedKeysFile /etc/ssh/keys/%u

    cat /etc/ssh/keys/bender
    from="[192.redacted]/24,[redacted]/20" ssh-ed25519 AAAAC[snip...] comment

or wherever your system is configured to look for public keys, typically /home/username/.ssh/id_dsa.pub. I use a different location. Even being really broad like adding a /16 or /8 for a home ISP is still better than allowing the entire internet. This can also be useful where machine-to-machine ssh keys are utilized one can limit the access to that network so that should keys leak the potential blast radius of damage is reduced. For example, the keys for an Ansible account can be restricted to the Primary/Secondary Ansible server IP addresses or at very least the CIDR block(s) of the network(s) they reside in. Broad restrictions are not perfect but perfect is the enemy of good or good enough.

Example use case would be that lets say a contractor from Microsoft tries one of your keys. Your restriction limits the key validity to 24.0.0.0/8 and they are coming from 207.0.0.0/8. They will be denied Authentication refused and you now have log entries that can be shared with their fraud department, the world, whomever. Obviously the tighter the restrictions the better, at the risk of requiring a static IPv4 or IPv6 address if too tight. One can always have lighter restrictions on a fall-back account that requires additional hoops to sudo / doas / su.

[mystifyingpoi]

Is such paranoia warranted? Millions of corporate laptops run Windows 11 just fine. I know M$ is evil and spying on you, but not to such degree.

[malux85]

Can you tell us which software? (Even if it’s very niche) I’m really curious where the gaps are.

[pepa65]

On one Windows box I once put my password in for a private Github site. Never had to do that again, it just 'remembered' it... Not what I would expect or want.

[nine_k]

Why replace it? Wine works fine.

[Kwpolska]

If Windows were to steal your SSH keys (lol), would you really think using a third-party program would protect you? The evil code could just read the key you configured in PuTTY.

[oguz-ismail]

> Terminal

Have they fixed font rendering yet? cmd.exe looks better on my laptop

[Lammy]

Have they fixed it spying on you? https://github.com/MicrosoftDocs/terminal/issues/139

[perching_aix]

Are you referring to the pixel-level font smoothing they use by default (as opposed to CMD's subpixel-level font smoothing)?

You need to define the "antialiasingMode" key in the settings JSON for the default profile to hold the value "cleartype", rather than "grayscale" (which is the default value). I don't believe this is exposed in the GUI settings page.

Note that this only affects the actual terminal emulation area. The rest of the application will still be pixel-level font smoothed (so e.g. the tab titlebars, the settings, etc.).

[MortyWaves]

I’ve never noticed any issues on any computer with it…

[recursive]

The first time I ever saw it, the text already looked better than cmd.exe via conhost.

[throaway920181]

I've only used it through RDP on Wayland and it's been fine visually. Downloading it can be a challenge if you don't know where to look (Github, not Microsoft's App Store...)