Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Socket #3859

Closed
ntoskrnl-exe opened this issue Feb 18, 2019 · 0 comments
Closed

Socket #3859

ntoskrnl-exe opened this issue Feb 18, 2019 · 0 comments

Comments

@ntoskrnl-exe
Copy link

I keep getting a Permission Denied error with NMap, even though I run the command with sudo

A browse on GitHub, shows that this is a known issue, and this is a known issue going back many months. My initial enthusiasm for this has been tempered some what, given sockets is large part of what I do.

While I mean no criticism at the individual developers involved in WSL development as I am sure, the devs are working very hard - there are clearly issues and challenges integrating a Linux Subsystem into Windows.

With that in mind, I therefore intend to drop using this feature till it has reached a more mature point in the subsystem lifescycle. I will buy a second PC to run windows and turn my laptop into full Linux installation, which is what I was going to do in the first instance, till I decided to try WSL. I have up voted an issue in user voice on this as well.

Again this should not be levelled at individual devs who I am sure work very hard, to provide functionality for users. However, this is yet more of the same from Microsoft. Marketting something, where there are known issues, and in fairness something as fundamental as sockets functionality in Linux, should be provided.

Maybe this is more political than technical. Maybe this is seen as tool to migrate people from Linux to Windows. Whatever is going on with WSL - suffice to say, I will leave this beta until it has become a more mature subsystem. When functionality is clearer and technically more stable. I keep seeing people refer to it as bash - which unsettles me. You have the name of Windows Subsystem for Linux - and then have people referring to it as bash. Its unsettling as there is a lack clarity on where this is going.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants