• 2 Posts
  • 60 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle













  • For starters, brave is chromium. If you care about the open web at all, you should get firefox, end of discussion. It’s also not particularly good at being private, especially considering that whenever chromium stops supporting manifestv2, brave will have to either support it themselves or use manifestv3. This is generally true of all features that enable privacy and are being eroded by google (see: cookies phaseout and ad profiles phase in, web integrity).

    If you like the idea of crypto, I suggest you watch the YouTube essay “line goes up”. If you’re still interested in crypto beyond “the idea is cool, I guess” then I still suggest you get firefox and an appropriate crypto wallet extension. Last I checked the standard was metamask but it might have changed since.

    Any youtuber you see talking about brave have been paid handsomely to tell you to use it. Do not fall for advertising, and exercise level-headed judgement.

    Is the browser good? No, not really. Any and all of its demarcating features, you can get on all others with a few extensions.

    Is it still a good idea to support it despites the ceo being a raging bigot? At this point why even do that (btw the Obama points do not stand here, because he is irrelevant to this conversation; this is textbook whataboutism).

    Similarly, you could choose to pay J.k. Rowling for her books, and support a very vocal transphobe that has stated outright that she’s using the money she makes to further her agenda, or you could buy and read better books, such as the discworld series. At this point choosing Harry Potter over a better series is choosing transphobia, and choosing brave over a better browser not made by a nutjob is choosing the nutjob’s side.




  • So to be clear, you want traffic coming out of your VPS to have a source address that is your home IP?

    let’s go back to fundamentals and assume for a second that your VPS provider allows these packets out and your VPS initiates a TCP connection like that. It sends a TCP SYN with source: home address and dest: remote.

    The packet gets routed to the remote. The remote accepts and responds SYN/ACK with source: remote and dest: home address.

    Where do you think this packet will get routed? When it gets there, do you think the receiving server (and NAT gateways in between) will accept this random SYN/ACK that doesn’t appear to have a corresponding outgoing packets sent first? If so, how?



  • Not really. Your VPS’s public IP is not yours to change, for obvious reasons, and it’s unlikely that your hosting provider will let you send packets from your VPS using a source address that is incorrect. if they let you, then any replies to those packets will evidently get routed to the actual IP, ie your home IP. If you really want to forward SMTP to your VPS (which has less chance of being on a Blocklist by virtue of not being a residential IP), I suggest declaring your VPS as your SMTP sender in SPF, instead of declaring your home IP and trying to make that work with the VPS IP. The VPS can then be configured as an SMTP relay (this is a key feature of SMTP) to your home instance, or you could forward all traffic on the appropriate ports at the TCP level, but I don’t advise doing this.

    I hope you understand that if what you’re asking was possible, I could rent a VPS, spoof your IP and receive traffic meant for your IP without any issues. For the same reasons, I think the other commenter mentioning x-forwarded-for headers is wrong if you’re not using DKIM (and even then it’s iffy). Otherwise I could just write a payload with mailto: whatever, from:you@yourdomain and x-forwarded-for: your home IP and pass SPF checks without having control over your IP.

    if you’re still confused about SMTP feel free to ask more questions