• 0 Posts
  • 904 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle





  • Put your reverse proxy in a DMZ, so that only it is directly facing the intergoogles

    So what? I can still access your application through the rproxy. You’re not protecting the application by doing that.

    Install a single wildcard cert and easily cover any subdomains you set up

    This is a way to do it but not a necessary way to do it. The rproxy has not improved security here. It’s just convenient to have a single SSL endpoint.

    There’s even nginx configuration files out there that will block URL’s based on regex pattern matches for suspicious strings. All of this (probably a lot more I’m missing) adds some level of layered security.

    If you do that, sure. But that’s not the advice given in this forum is it? It’s “install an rproxy!” as though that alone has done anything useful.

    For the most part people in this form seem to think that “direct access to my server” is unsafe but if you simply put a second hop in the chain that now you can sleep easily at night. And bonus points if that rproxy is a VPS or in a separate subnet!

    The web browser doesn’t care if the application is behind one, two or three rproxies. If I can still get to your application and guess your password or exploit a known vulnerability in your application then it’s game over.


  • My reverse proxy setup allows me to map hostnames to those services and expose only 80/443 to the web,

    The mapping is helpful but not a security benefit. The latter can be done with a firewall.

    Paraphrasing - there is a bunch of stuff you can also do with a reverse proxy

    Yes. But that’s no longer just a reverse proxy. The reverse proxy isn’t itself a security tool.

    I see a lot of vacuous security advice in this forum. “Install a firewall”, “install a reverse proxy”, etc. This is mostly useless advice. Yes, do those things but they do not add any protection to the service you are exposing.

    A firewall only protects you from exposing services you didn’t want to expose (e.g. NFS or some other service running on the same system), and the rproxy just allows for host based routing. In both cases your service is still exposed to the internet. Directly or indirectly makes no significant difference.

    What we should be advising people to do is “use a valid ssl certificate, ensure you don’t use any application default passwords, use very good passwords where you do use them, and keep your services and servers up-to-date”.

    A firewall allowing port 443 in and an rproxy happily forwarding traffic to a vulnerable server is of no help.











  • Quick pros/cons from what I’ve read (correct me if I’m wrong - I’ve not used syncthing myself):

    syncthing

    Pros:

    • Easy to setup and use.
    • No infrastructure to maintain
    • Will sync directories between computers

    Cons:

    • Uses third party resources to sync by default (can setup direct sync if needed/wanted however)
    • Only does directory synchronization

    Nextcloud

    Pros:

    • Can synchronize directories
    • Entire synchronization pipeline is under your control
    • Offers a lot more functionality if you want it (WebDAV, Calendars, public shares with “anyone with URL can view” permission, etc.)

    Cons:

    • You need to setup/maintain your Nextcloud server
    • Can be fiddly to setup for some (wasn’t for me - but lots of people do complain about it).

  • Do you think webdav somehow dumps you database? No it’s just a protocol to save your files on your webserver. It’s just a middelman.

    Umn. It allows the application to do its own synchronization and diff resolution. It’s why they recommend it.

    Directory synchronization is a “best effort” to copy files back and forth without considering the application’s needs. Copying database files while they’re being written can be problematic for example.

    Both Nextcloud and syncthing will synchronize a folder. And it will probably work if you aren’t making lots of changes on both systems. But there is increased risk.

    Yeah it’s my recommendation from my personal experience. Is that wrong?

    Yes - absolutely. “I’ve been lucky so far” and recommending against what the product you’re using says you should do is TERRIBLE advice.

    The point is, syncthing is rock solid, never had any issue being it with my zotero database or syncing files between my devices. If you’re a Nextcloud advocate or are against my personal opinion so be it :).

    Why are you getting defensive towards syncthing? It seems fine. It’s the wrong tool for what you’re using it for.