• 0 Posts
  • 12 Comments
Joined 2 years ago
cake
Cake day: August 19th, 2023

help-circle


  • Someone made a mistake here. It’s not getting your IP address. An IP address is assigned by the gateway when you’re connected to an access point. An IP address is not an identity. They are always changing and can be shared. This has already been tested and upheld in court.

    It’s actually collecting your MAC address. Which is exchanged when your phone or tablet scan nearby WiFi points or Bluetooth devices. However, this can already be defeated. By default iOS and Android both have the option to randomise the MAC address in intervals. Making it extremely difficult to prove anything. This feature exists because the devices real MAC address never changes. It is unique. Alternatively, users can disable WiFi and Bluetooth scanning entirely. However, your device no longer participates in the Find My Devices program by Apple and Google, location does take longer to acquire in some scenarios, and accuracy may take longer to triangulate.



  • so much for track day, I guess?

    Stuff like this is likely planned in advance with sports and super cars. Since this technology has existed for a while. Assuming you visit a recognized track, wherever it may be, the limiter simply turns off. For example, the 2009 and later Nissan GTR is sold in Japan with a 112 MPH artificial limiter in the software. The limit is there by law. GPS / Sat Nav is standard on this car. If you visit say, Fuji or Laguna Seca, the car knows where it is and turns the limiter off. Allowing you to achieve the ~200 MPH top speed. Examples sold for other markets such as US and EU need not worry. The redline in 6th gear is your physical limiter.

    On a slightly related note, clever people have figured out ways around limiters. Such as tricking the GPS or modifying the ECU. Unfortunately, these days it gets harder to do this as manufacturers like Mercedes, BMW, VW, and a few others, are encrypting the communication network physically located in the car. It’s not the traditional low and high speed CAN Bus. FlexRay is becoming more commonplace unfortunately.





  • It can be very stupid. Depends on the software though as the registry is meant for saving user and system settings to a degree. Like Windows File Explorer makes perfect sense. As does settings for audio.

    It’s generally advised to not bloat the registry wherever possible. WinSCP is a great piece of software. Unfortunately it defaults to saving to the user registry. You can change it to save to an ini file instead. By using the registry to save settings it can be jarring for the user when they’re trying to troubleshoot something. Only to find out after uninstalling and reinstalling it doesn’t start over fresh. Or if they’re trying to backup settings and data to restore with later. The registry isn’t typically included for good reason.




  • Once you agree to letting friends and family access your hosted services, you become the tech support for any problems. Whether that be your fault, user error, etc. You should absolutely limit who you give access to. In my case, only three people can and that’s immediate family. No friends, no extended family. I don’t wanna deal with all that mess when I deal with it at work. Don’t over extend yourself by being nice.

    Using Cloudflare is against the ToS when used for services like Jellyfin. Your account can be limited, closed, or find yourself getting a several hundred dollar bill for data usage because you’ve breached the terms of service. Additionally, streaming content on free accounts incurs higher latency which I’ve confirmed myself Argo smart routing massively reduces. https://github.com/jellyfin/jellyfin/issues/9295 - Don’t abuse what’s free or you may lose it.

    Google shouldn’t be indexing your domains anyway. If it’s flagged your domain, it’s been indexed and scanned. Alternatively, it could indicate you have a weak point somewhere on your server and you’ve been breached. Google’s scan picked up whatever it was. Though I doubt this is the case and just a false positive. Double check your robots.txt files and disallow everything. Most index bots respect this. You can use a community sourced bot blocker. https://github.com/mitchellkrogza/nginx-ultimate-bad-bot-blocker

    I’ve been running my own self hosted services for almost a decade. Though I have a background in IT directly doing this kind of stuff daily at work. As long as you have a strong firewall, modern TLS, relevant security headers, automatic tools like fail2ban, and have a strong grasp on permissions, you should be fine. Before I moved everything to non-root docker, it was given its own service user and SELinux policy. Using direct DNS isn’t so much of a problem. You shouldn’t have any issues. Feel free to reach out if you have any questions.