3 ms·

Interestingly, Windows actually did exactly what's proposed at the end when MS added them in Vista. To minimize the security issues with symlinks, you had to el

by ziml77 4y ago

Interestingly, Windows actually did exactly what's proposed at the end when MS added them in Vista. To minimize the security issues with symlinks, you had to elevate to admin to create them. It was only during the life of Windows 10 that they even added the option to not have to elevate to create them. It was done specifically because symlinks are often shared across systems since they end up in places like git repos and npm packages: https://blogs.windows.com/windowsdeveloper/2016/12/02/symlinks-windows-10/ https://blogs.windows.com/windowsdeveloper/2016/12/02/symlin...

faragon 4y ago
You could create symlinks since Windows Vista without permission elevation, if having disabled the UAC ("User Account Control").
- ziml77 4y ago
  Disabling UAC meant there was nowhere to elevate to because you just had admin rights all the time.
  - faragon 4y ago
    You're right, thank you.
alerighi 4y ago
There is an option (that is proposed when you install git) to allow normal users to create symlinks. The fact is that symlinks are very useful to a developer, and a lot of development tools make use of them.
kasabali 4y ago
> It was only during the life of Windows 10 that they even added the option to not have to elevate to create them Nah it was available from the start in local security policy settings. https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-vista/cc766301(v=ws.10)?redirectedfrom=MSDN#create-symbolic-links https://docs.microsoft.com/en-us/previous-versions/windows/i...
- ziml77 4y ago
  Thanks for the correction. I actually think I did use this option way back, but just completely forgot about it.