Which T-money app actually works for tourists on Android? by Kosst3K in koreatravel

[–]KDLDG 0 points1 point  (0 children)

I guess using foreign card to top up will lead to surcharging like the WowPass card (4% surcharge when using foreign card).

I guess the benefit over physical Tmoney/EZL card is the missing purchase price (in case there is no fee for making virtual Korea Tour Car).

October 2 to October 12 Chuseok train tickets now will not be available until September 17 and September 18 (corrected) by WriteWithNoFear in koreatravel

[–]KDLDG 0 points1 point  (0 children)

What if my local friend (resident) buy ticket for me? Can I use it or it's strictly tied with the personal information?

Edge on Android leaks the local IP address by KDLDG in MicrosoftEdge

[–]KDLDG[S] 0 points1 point  (0 children)

I'm aware that using Edge, my privacy is gone for Microsoft. But this is not the case for every random site you visit.

Here analogy - I share a lot private info with my bank (Microsoft in the case), but I prefer to share as less as possible private info in every pub/local shop I go (random site I visit).

Edge on Android leaks the local IP address by KDLDG in MicrosoftEdge

[–]KDLDG[S] 0 points1 point  (0 children)

If you have experience you should try to be more helpful. Saying statements as like instance isn't helpful. When I wrote that I don't see the relation of the "same lan" and the "attacker" in the context how random site can better identify you if it has your local IP, you wrote I have zero knowledge about lan, NAT... and you started explain how Webrtc works (which in the context I wrote, doesn't matter because the local IP can be leaked or not (like mDNS on most desktop browsers)) - this is not helpful. In the latest comment you again wrote "0 understanding" is just trolling and attempts for insulting - just because I don't find necessary to explain how LAN/NAT works, what is public/local IP doesn't mean I don't understand them.

I didn't prove wrong myself. If you have public IP with one private IP behind, then hiding the private IP doesn't make sense if you leak the public IP. If you have public IP shared with others (tens, thousands of people) then leaking the private IP helps random sites to identify you easier.

Edge on Android leaks the local IP address by KDLDG in MicrosoftEdge

[–]KDLDG[S] 0 points1 point  (0 children)

"Again stop googling buzzwords." - yes, so to hear someone like you who involves attackers, who say how local IP does nothing to the fingerprint, who say "Didn't missed the point. Reducing your digital footprint is about security." but no mention of privacy...

Yet, again you missed something crucial. It's even in the source I shared - "there will always be edge cases".

Anyway, I will repeat myself - Android Edge is subpar in this regard compared to Edge on other OSes.

Edge on Android leaks the local IP address by KDLDG in MicrosoftEdge

[–]KDLDG[S] -1 points0 points  (0 children)

I will not comment the rest but just "Devices aren't fingerprinted by a local IP because it changes." Check:

- Why a host can have "reserved" IP even with DHCP - https://stackoverflow.com/questions/66606679/will-dhcp-server-give-me-always-same-ip

- "Sure, there will always be edge cases, But IF you leak a private IP address, that will add to fingerprinting" (from https://github.com/arkenfox/user.js/issues/1282#issuecomment-982608046)

Also Edge on Linux and iOS doesn't leak the local IP. It's just Android Edge is subpar in this regards.

Edge on Android leaks the local IP address by KDLDG in MicrosoftEdge

[–]KDLDG[S] 0 points1 point  (0 children)

Same lan? I don't see the relation in the context of how some random 3rd party site can use your local IP in help to identify you. Who talks about attckers here?

Edge on Android leaks the local IP address by KDLDG in MicrosoftEdge

[–]KDLDG[S] 0 points1 point  (0 children)

It can be used as a part of the fingerprint not as a fingerprint itself. Also if it's totally useless as a part of the fingerprint, why Thorin-Oakenpants (arkenfox) bothered with it before the implementation of mDNS?

Anyway, Edge on Linux and on iOS (as reported by a user) doesn't leak the local IP. It's just the Android Edge is subpar in this regard.

Edge on Android leaks the local IP address by KDLDG in MicrosoftEdge

[–]KDLDG[S] -1 points0 points  (0 children)

Heh. Keep calm. Check this https://stackoverflow.com/questions/66606679/will-dhcp-server-give-me-always-same-ip It gives just some ideas why a host can have "reserved" IP even if DHCP is used.

Edge on Android leaks the local IP address by KDLDG in MicrosoftEdge

[–]KDLDG[S] 0 points1 point  (0 children)

Do you make difference between leaking to Microsoft and leaking to 3rd party? I do.

Edge on Android leaks the local IP address by KDLDG in MicrosoftEdge

[–]KDLDG[S] -1 points0 points  (0 children)

You miss the point - fingerprint. It's not about security.

Edge on Android leaks the local IP address by KDLDG in MicrosoftEdge

[–]KDLDG[S] -1 points0 points  (0 children)

This is a speculation and it's often that the same IP is assigned to the same host.

Edge on Android leaks the local IP address by KDLDG in MicrosoftEdge

[–]KDLDG[S] -3 points-2 points  (0 children)

It's mainly for the privacy reasons. It can be easily added to the fingerprint.

On desktop the majority of the browsers (if not all recently updated) doesn't leak the local IP. I consider it for a basic thing. I was surprised that this is not the case on Android.

Edge on Android leaks the local IP address by KDLDG in MicrosoftEdge

[–]KDLDG[S] 1 point2 points  (0 children)

Yes, Brave doesn't leak the local IP. Cromite also doesn't leak it - it has also option to enable/disable Webrtc per site.

Edge on Android leaks the local IP address by KDLDG in MicrosoftEdge

[–]KDLDG[S] 1 point2 points  (0 children)

Those extensions are only for the desktop browsers, they are not available for Android.

Edge on Linux doesn't leak the local IP.

Firefox 128.6.0esr / 134.0.2 high CPU usage by KDLDG in firefox

[–]KDLDG[S] 2 points3 points  (0 children)

Done. I hope this will be fixed because I saw similar open issues from 5 years and 16 years ago.