Earlier quoted context omitted.
>Wishlist: tmux, emacs, vi, netcat, shell option for vi-mode, rc-file with preferences, ncurses library, something simpler than curses, zip and unzip No thankyou. I can certainly understand including SSH support, but I don't want what is pretty much the only remaining viable non-Unix platform to start bundling horribly dated and clunky Unix-like commands and bloated GNU tools.
regedit would like to have coffee with you.
Looking Forward: Support for Secure Shell
181–190 of 404 posts
Re: Looking Forward: Support for Secure Shell
#182Wonderful. I am a big supporter of Powershell, and while Powershell has supported remoting since almost day one, it will never enjoy quite as much support as SSH already receives (e.g. third party tools, firewall support, etc). It is also nice that they're looking into using something fairly "proven" secure, OpenSSH is exposed to the internet a lot (even if, yes, that is not best practice) so we can reasonably expect…
I've been historically what can be described a Microsoft hater and I have to tell you, missing official SSH support has never been a hate generator and insinuating otherwise is insulting. The first reason for which I have historically hated Microsoft is because of how they fought open standards. I can't believe that Microsoft changed in any meaningful way when I can't get a Lumia phone or Outlook to work with CalDAV…
My dislike of MS is quite simple. I simply don't like their products. That doesn't mean I automatically love OSX or Linux. IMO OSX is a mediocre product with a polished user experience and Linux as a desktop is just broken. Unfortunately, I can't say there is a single OS that I like at the moment.
Re: Looking Forward: Support for Secure Shell
#183Earlier quoted context omitted.
Fair. But I couldn't target my crappy roguelikes at cygwin - requires complicated third-party installs. I ran cygwin-with-ssh heavily for a while in 2003. It was a hell of a thing to get it going. Then I had trouble getting it to work on a new computer and gave up. Shouldn't be surprised that it got good again.
> complicated third-party installs Wait, isn't that nearly everything you ever install on Windows? Not complicated per se, but everything is third party and not signed by people maintaining Windows (as with most GNU/Linux distributions).
Re: Looking Forward: Support for Secure Shell
#184[deleted]
Re: Looking Forward: Support for Secure Shell
#185Earlier quoted context omitted.
A VPN with sshd exposed only inside the private network is a much smarter way of handling remote access. (But it's initially harder, so lots of people don't do it.)
You're just trading sshd bugs for VPN bugs, in that case. Which are more likely? From what I know, I think I'll put my lot in with sshd. Perhaps I'm not well informed, though. Also, sshd + fwknop (port knocking) is a very secure combo, IMO.
Re: Looking Forward: Support for Secure Shell
#186Earlier quoted context omitted.
Isn't ISE pretty much what you are asking for?
Powershell doesn't support interactive console apps (those that want user input), so it's really not much of a cmd.exe replacement. http://powershell.com/cs/blogs/tips/archive/2012/12/12/block...
Re: Looking Forward: Support for Secure Shell
#187Earlier quoted context omitted.
I moved away in 1999 to the Mac, and because of the incredible expensive Macs nowadays, I'm probably going to make another move, to Ubuntu. Still, Steve Jobs was not an easy guy either. I don't know if he would mock an employee for having an Android phone? Not unlikely given how anti-Android he was.
VERY good point and honestly one that I hadn't thought of. I'm not aware of any publicised cases of Jobs calling out an Android phone but I would believe it, he was an asshole. IIRC he was so anti-android b/c he saw Android as a blatant rip-off of iOS (not weighing in here on either side). As far as cost of macs I think it's still worth it even if you want to run Ubuntu as your OS b/c they hold their value better tha…
I also found it to be a huge pain to install Linux on it, which is why all my Linux computers are Thinkpads (with the exception of the old HP workstation I'm typing this from).
Re: Looking Forward: Support for Secure Shell
#188Earlier quoted context omitted.
> how they are handling Win 10 (Both in versions and cost) I'm a bit confused by this. It's free for any genuine Windows 7 or 8 user, and $99 to $199 for anyone else. There are two SKUs (Home and Pro), rather than the multitude with XP or Vista. How is this not a reasonable approach? Especially since Windows 10 is supposed to be the last Windows release of this kind.
> There are two SKUs (Home and Pro), rather than the multitude with XP or Vista Two SKUs, and then a bunch more; whole list currently is: Home, Mobile, Pro, Enterprise, Education, Mobile Enterprise, IoT core. There are also upcoming still unnamed "industrial" SKUs. Oh, and of course MS is going to offer 32 bit versions too. Also of course there will also be full suite of Windows Server SKUs, because obviously those a…
Is for an entirely different class of devices than the others.
> IoT core
Ditto
All the others are price discrimination for organizations. The typical end-user does not have to contend with the list you put forth.
Re: Looking Forward: Support for Secure Shell
#189I wish Windows just became a POSIX compliant OS. I think that would solve a lot of these smaller issues in an elegant way. Apple did a very smart job with Mac OS X, to the point where even I switched to a Mac after having Linux for so many years. It's incredible how I can install packages using homebrew and friends.. Come on Microsoft, go all the way!
It's like installing all those GNU tools on Windows to make it more like Linux, and putting Homebrew etc. on OSX to make it more like Linux. Why not just use Linux or BSD? I never understand it.
Also, the lack of proper Quartz windowing support from X11 apps makes using them painful.
Re: Looking Forward: Support for Secure Shell
#190Earlier quoted context omitted.
> bloated GNU tools If you were coming from the Unix/BSD world, I could understand this, but how is using a GUI for everything considered elegant, while GNU tools are considered "bloated?" Doesn't the GUI necessarily "bloat" the program more than a few extra command-line options would?
You don't need a GUI; PowerShell is a powerful command line scripting environment.