41–50 of 146 posts
Out of curiosity...why run this as a service? EDIT: I misread this and though it was only a client . Geez. If it's a server, then of course it should be a service.
Earlier quoted context omitted.
Was just coming here to voice my concerns over this choice as well, wondering what their reasoning is for changing crypto systems.
A crypto system is a big and complex thing, subtle and quick to anger, and I can't blame Microsoft for wanting to concentrate on the one they're already supporting, instead of having to support two. On the other hand, for the exact same reason, I expect OpenSSH probably isn't interested in supporting anything besides LibreSSL and maybe OpenSSL, at least while they're so closely related.
If they implemented a good openssl to cryptoAPI shim it could be usable by other projects linked against OpenSSL.
Earlier quoted context omitted.
It really is surprisingly bad, isn't it? I recently was involved in a continuous deployment system targeting Windows. We simply couldn't get WinRM to reliably upload fast and ended up installing SSH everywhere.
Yep definitely the worst thing ever. Not just that though; everything. I've lost so much hair in the last few months over trying to get a CD environment up on windows.
I'm interested in how this is going to work in PowerShell with the way everything works now, if there happen to be any details about that (whether here, somewhere else, or a past link)?
ssh user@windows.machine.local dir d: | lessOut of curiosity...why run this as a service? EDIT: I misread this and though it was only a client . Geez. If it's a server, then of course it should be a service.
> Leverage Windows crypto api’s instead of OpenSSL/LibreSSL and run as Windows Service Was wondering about that. I'm surprised the OpenBSD team is accepting the commits - something so fundamental and Windows specific doesn't seem like their kind of thing - but great! PS. If you're coming from a Unix background and interested in learning posh: https://certsimple.com/rosetta-stone
> Leverage Windows crypto api’s instead of OpenSSL/LibreSSL and run as Windows Service Was wondering about that. I'm surprised the OpenBSD team is accepting the commits - something so fundamental and Windows specific doesn't seem like their kind of thing - but great! PS. If you're coming from a Unix background and interested in learning posh: https://certsimple.com/rosetta-stone
I stopped reading this when I got to this part:
whois 'domain [domain name]'
$web = New-WebServiceProxy 'http://www.webservicex.net/whois.asmx?WSDL'
$web.GetWhoIs('[domain name]')
Just put none in the `whois` box and move on.
Out of curiosity...why run this as a service? EDIT: I misread this and though it was only a client . Geez. If it's a server, then of course it should be a service.
Earlier quoted context omitted.
I really don't like that there replacing an open source crypto with a closed source one. Putting on my tin foil hat but didn't Microsoft hand over a back door to the NSA already.
No.
Are you saying that you are familiar with the events that DonnyV is referring to but you are confident that they are mere legend? That you disagree with the published accounts?
Or are you saying that you are not familiar with that particular scandal, you've never heard of it, and your response is simply "Not that I know of."?