4 ms·
Thanks for the feedback! I'm actually a FreeBSD guy and I wrote this post so I have a URI to give to clients who primarily use Windows. I'm not sure what you m
by delano 17y ago
Thanks for the feedback! I'm actually a FreeBSD guy and I wrote this post so I have a URI to give to clients who primarily use Windows.
I'm not sure what you mean when you say I "don't seem to understand what the software is actually doing". Could you elaborate?
- tortilla 17y agoot, but I love the design of your site.
- delano 17y agoThanks! This site taught me to never settle for my own designs again.
- ajross 17y agoYeah. I should apologize for the tone, I guess. But the criticism was basically one of misplaced audience. As a guide for a typical windows-only IT wonk to install an sshd, it's really not bad. But I like to believe (or at least pretend) that a typical HN reader is a little above that level. To folks here, the critical information is that (1) openssh works under cygwin and (2) there's a simple installable distro for it. That information is conveyed just fine by the link to the upstream package, without the need for a tutorial. Add that to the fact setting up a remote access (!) mechanism on a host is an inherently security-critical operation that requires a clear low-level understanding of the software (i.e. more than can be taught with screenshots), and I guess I got a little cranky.
- delano 17y agoYa, I mostly agree with you. But there's a fine line between being a good consultant and being a good hacker. Running an SSH server was a quick solution for automating some basic tasks in Windows. Incidentally, I had a great conversation today with a Windows guy and I'll probably look further into solving these problems with Powershell.