Welcome to Hurricane Electric's Tunnelbroker.net forums!
Started by tjeske, April 20, 2018, 06:16:24 AM
Quote from: tjeske on May 18, 2018, 09:00:26 AMSo did someone actually login to your machine? What did they try?
Quote from: tjeske on May 18, 2018, 09:00:26 AMAnyway, there's also this thread on TechNet:https://social.technet.microsoft.com/Forums/windows/en-US/af68159a-87fc-4e39-92a9-c5f209aa4058/will-v6v4tunnel-be-fixed-in-final-version-of-april-2018?forum=win10itpronetworkingIt appears as if Microsoft acknowledges this issue. However, I am not sure how serious they treat this issue and how fast it might get resolved. The statement doesn't sound too promising, to hopefully fix it with the next release. And I hope by "release" they mean cumulative update, not Redstone 5. Maybe if more people post over there it'll spark more interest to tackle this bug.All in all it's probably really only a handful of people affected, since most will have a non-Windows upstream device serving as the local tunnel endpoint.
netcfg -s n
Quote from: tjeske on June 20, 2018, 10:57:10 AMThat sounds interesting. And quite similar to my approach. No idea why I had no success :(Anyway, I guess with this method you have to turn driver signature enforcement off with every boot? Maybe an alternative for that would be to use a self-signed driver (i.e. to sign a driver with your own certificate, that you create somewhere somehow). Then you only need to turn "testsigning" on, which is much more secure than no signature enforcement at all.
Quote from: tjeske on June 20, 2018, 10:57:10 AMAlthough I wonder what breaks the certificate of the old driver? Shouldn't it still be fine with MS old driver? Maybe if we also swap out tunnel.sys? Or does it need to be packed with the .cat-file and installed from there?