• 0 Posts
  • 10 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2024

help-circle

  • True, however TLS does not encrypt the hostname/IP address of the servers that you are connecting to, so your ISP can monitor the servers you visit. A VPN provides an encrypted tunnel for your traffic, so your ISP can only see that you are communicating with the VPN server. However, the VPN provider can see the hostname/IP of the servers in order to forward the traffic to its destination.

    Ideally the VPN provider does not monitor or keep logs of the connections, but this is not always the case. A VPN offers privacy from the ISP or from other clients connected to the local network when using public WiFi.

    It can also provide some level of anonymity, because the server that you are connecting to will only be able to see the VPN IP address connecting to them, instead of your home IP address. It is possible to still be identified by other means besides your IP address, like using cookies or browser fingerpinting.








  • Yeah I’m not saying its perfect and LLMs are non-deterministic so it could give you some crap. You’re not wrong and it’s good to be aware of that. How do you verify some random stranger from the internet wasn’t an asshole and gave you malicious config? 🤷 The best answer is probably just that OP should heed the warning on the website they linked, if they have no confidence or relevant skills:

    THIS IS DELIBERATELY MALICIOUS SOFTWARE INTENDED TO CAUSE HARMFUL ACTIVITY. DO NOT DEPLOY IF YOU AREN’T FULLY COMFORTABLE WITH WHAT YOU ARE DOING.

    I pasted the OP unmodified into a local LLM and it gave me this:

    Paste this (replace  192.168.1.105 with your Acer’s local IP from Part 1.3): 
    
    server {
        listen 80;
        server_name wowsocool.com www.wowsocool.com;
    
        location / {
            proxy_pass http://192.168.1.105:8000/;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;
        }
    

    along with correct instructions on finding the IP of the laptop, port forwarding, and examples on how to set up DDNS for several popular providers. The only thing I can see that is wrong is the port should be 8893 instead of 8000 and they may want to proxy a different path to Nepenthes than /


  • Nah, they suck for programming or anything involving imperative logic, but they are pretty decent with things that are declarative, like config. I know people want to hate or deny any usefulness of LLM, and it doesn’t help that corpos insist on cramming LLMs into usecases that aren’t applicable to LLMs at all, but this is actually one of the things they are good at.