That's on my list of things to do for my Audi. Apparently the system has support for fobs, and I have instructions for coding them, but I don't actually have any fobs. So I have to go through the same process. It's an old car though, so it wasn't expensive either... just leaky.

The mechanics I've talked to say pretty much all the 4.2 liter Audis they've seen have been leaky... story of my life with bored-out versions. The 7.3 Ford is the same way.

What, when the polyfuses on their motherboard flip and they don't get to use their USB ports for a while? I have yet to have smoke come out of anything I brought home except when I deserved it, putting way too much power into some speakers once.

Did you at least laugh right in their face?

This doesn't compete with PuTTY, probably: odds are it will be a console-mode ssh binary just like what cygwin users have already but without a dependency on cygwin, and a server just like what cygwin users have already but with NT auth (incl. AD) rather than /etc/passwd authentication which maps to local SIDs. PuTTY does have a command-line client, but nobody is paying for that. They're paying (if they pay at all) for the interface.

buh?

windows$ ps -aef
    UID PID PPID TTY STIME COMMAND
cyg_serv 2588 1 ? May 29 /usr/bin/cygrunsrv
cyg_serv 2672 2588 ? May 29 /usr/sbin/sshd
cyg_serv 7016 2672 ? 18:46:49 /usr/sbin/sshd
  user 8108 7016 pty0 18:46:52 /usr/bin/bash
  user 6536 8108 pty0 18:46:58 /usr/bin/ps
 
debian$ ps -aef | egrep '(sshd|bash)'
root 13792 1 0 Apr24 ? 00:00:06 /usr/sbin/sshd
root 19995 13792 0 18:48 ? 00:00:00 sshd: user [priv]
user 19997 19995 0 18:48 ? 00:00:00 sshd: user@pts/0
user 19998 19997 0 18:48 pts/0 00:00:00 -bash
user 20131 19998 0 18:50 pts/0 00:00:00 egrep (sshd|bash)

So uh, what's the difference? Looks like all cygwin is missing is proper authentication. AFAIK it maps UIDs to SIDs, but yes, is missing AD support.

I've been doing that for so long I've actually given Chameleon money (for Xoftware.) No, wait. Except the last time I actually wanted to do it was years ago, because it's been years since I had any Unix-specific machines. Now it's just PC Unix. I just threw away my last Unix machines, a POWER1 and an Indy R4400SC@200MHz. It wasn't worth dusting them off.

Uh what? I use it all the time between Windows and Unix, Windows and Android... it works fine. If there are any problems, they are abstracted away by the client and/or server and I don't notice them at all.

Almost. They need SSH compatibility to be managed by Linux boxes, yet with proper NT authentication instead of the band-aid which is Cygwin.

When you're typing, period, creating short options first makes a lot of sense. Powershell is a shell which is apparently not designed to be used by typing. Too bad it has a typing interface.

New, as in everyone who wants this already has this via cygwin. It even installs as a service. Presumably I should ssh in and use powershell, but I've never tried because if I want to do real computing, I do it on a real OS with a real shell.