neatchee

joined 1 year ago
[–] neatchee@lemmy.world 4 points 1 day ago (2 children)

I'm curious what you mean by "better moderation"? Are you comparing to specific instances? Or do you mean consistency, because it's more centralized?

[–] neatchee@lemmy.world 19 points 4 days ago (3 children)

Unfortunately, no, not really. They are absolutely able and willing to confiscate your devices at any time once you're on Chinese soil, and once you've lost physical control, that's the end of trust for that device. Even beyond that, it's not unheard of for there to be vulnerabilities in Wi-Fi, Bluetooth, etc that make your device susceptible to wireless attacks. IMO it's not worth the risk.

Here is just one example of this type of thing uncovered by The Guardian, New York Times, and others in a joint investigation: https://www.theguardian.com/world/2019/jul/02/chinese-border-guards-surveillance-app-tourists-phones

[–] neatchee@lemmy.world 44 points 4 days ago* (last edited 4 days ago) (5 children)

Do not bring your normal personal devices to China. They are notorious for injecting spyware on foreign devices at every opportunity. Use a freshly formatted device and create all new accounts to use with it.

Regarding services: do not use self-hosted services unless you you spin up fresh, isolated instances of your services for use while abroad and spin them down afterwards, including formatting any OS they were hosted on.

Regarding VPN: because we are assuming that any device used in China is compromised, do not connect to your VPN unless you have set up a segregated VLAN and are connecting through a VPN server instance created specifically for use while in China.

Basically, assume anything you use in China is compromised. And assume your connections are being monitored. And assume that any device you are connecting to from China is at risk of being compromised. So everything needs to be segregated from the rest of your network and set up specifically to be deleted after you're back home.

[–] neatchee@lemmy.world 1 points 3 months ago

My solution for this type of situation is MicroBin running on my home network from a non-standard port, with a port knocker to open and close the port when needed.

My router handle DDNS so I can always contact my home network easily. I port-knock to trigger an iptables command on the router to forward traffic to the MicroBin host.

I also have my phone set up to connect via openvpn to my home network so that I can remotely do things like start and stop services, set port forwarding rules, etc.

[–] neatchee@lemmy.world 6 points 3 months ago

So I'm Federated, So What?

Definitely this one lol

[–] neatchee@lemmy.world 36 points 3 months ago (5 children)

Truck-kun trying to make a new fediverse themed anime

Reincarnated to Save Social Media

[–] neatchee@lemmy.world 2 points 4 months ago

So... What you say is... Luv love Mi-do? But do Yu know Ai love Yu?

[–] neatchee@lemmy.world 54 points 4 months ago (6 children)

What is Luv?

[–] neatchee@lemmy.world 0 points 4 months ago

I mean to say that the connection attempt is failing because the traffic is never reaching the server.

[–] neatchee@lemmy.world 1 points 4 months ago (2 children)

There is no traffic on Port 8081 in those logs

[–] neatchee@lemmy.world 1 points 4 months ago (4 children)

Yeah your iptables is already set to up ACCEPT by default meaning no blocking.

My next step would be to determine whether the traffic is reaching the target machine. Look into how you can monitor inbound traffic and verify whether the server even sees the inbound connection attempt

 
 
view more: next ›