Live data from Hacker News

Linux under WSL2 can be leaking

mullvad.net

191–194 of 194 posts

Re: Linux under WSL2 can be leaking

#191

Earlier quoted context omitted.

> Even just owning that many is unlikely. > No I specifically said use , not own . These two verbatim quotes from you seem to be in conflict with each other.

My question was about using that many devices. And I'll quote myself here fully: > Out of curiosity, how do you even manage to use more than five devices for private use at once? Even just owning that many is unlikely. One sentence is a question, the other is a statement which I consider to be true (and explains how I arrived at that question). Also it was quite clear from my argument that I was talking about people…

> I can't imagine why you'd be arguing like this, I just hope it's not on purpose.

Seriously? OP never said just me and only me uses all five plus devices. I and others gave you multiple examples of how that could be very possible realistically, and then you shift goal posts and say it’s us being argumentative. I’m done, have a good life!

Re: Linux under WSL2 can be leaking

#192
Strange then that the WSL2 guest gets a RFC1918 private address, because that would imply that the host is NATing traffic to and from the guest. However that does not happen through the ordinary Hyper-V NAT routing machinery -- at least Get-NetNat shows nothing in Powershell and in fact multiple people have reported broken WSL2 networking because they had leftover NAT rules from old Hyper-V VM's. It would help to have some conceptual documentation here about what WSL2 is doing.

Re: Linux under WSL2 can be leaking

#193
post #90
post #63

Earlier quoted context omitted.

If you are playing games on Linux, WSL doesn't help anything for sure, it only adds overhead.

Why would you ever play games on WSL when you already are on the superior platform for playing games...

Which was exactly my point - I play them directly on Linux.

Re: Linux under WSL2 can be leaking

#194

Earlier quoted context omitted.

Visa doesn't solve the same problems as Bitcoin, so this isn't comparing apples to apples. Bitcoin isn't a centralized, credit-based payment network; it was designed as an electronic alternative to cash . (Don't forget to include the economic and social cost of global anti-counterfeiting measures necessary to maintain the USD market value in the cost of the Visa system!) Also, the reward halving schedule applies to b…

Credit-based transactions are a subset of Visa transactions. Visa Debit and V PAY were indeed designed as an electronic alternative to cash (as were MasterCard Debit and Maestro on the MasterCard side).

> Visa Debit and V PAY were indeed designed as an electronic alternative to cash …

These are not alternatives to cash, they're alternatives to checks. The actual cash is held in accounts at centralized third parties (banks) who must be trusted to maintain accurate records, remain solvant, and not interfere with transactions legitimately approved by the account holders. What we see, however, is that the records are not always accurate, and banks do interfere with account holder-approved transactions, based on either their own policies or legal constraints. As for solvency… let's just hope that particular house of cards is never really put to the test.

Bitcoin, like physical cash, does not depend on trusted third parties. There are technological measures in place to guarantee accurate record-keeping, and while the sender of an "illegal" payment may be prosecuted after the fact (if they can be identified) there is little anyone can do either to prevent the payment from going through or to claw back the funds once they have been confirmed by the network.

Post reply on HN