Opensource

5531 readers

12 users here now

A community for discussion about open source software! Ask questions, share knowledge, share news, or post interesting stuff related to it!

Credits

Icon base by Lorc under CC BY 3.0 with modifications to add a gradient

⠀

founded 2 years ago

MODERATORS

pylapp@programming.dev

Nginx Proxy Manager 2.13.6 Released With Built-In Two-Factor Authentication (linuxiac.com)

submitted 1 month ago by cm0002 to c/opensource@programming.dev

8 comments fedilink hide all child comments

Nginx Proxy Manager, a popular web-based and user-friendly reverse proxy management interface for Nginx, has just released version 2.13.6. Although this is only a patch release to a minor version, it actually delivers some fairly significant improvements.

The most notable change is the addition of TOTP-based two-factor authentication, allowing administrators to protect access to the web interface with time-based one-time passwords, bringing a long-requested security feature to Nginx Proxy Manager.

Certificate management has also been expanded. When creating new certificates, users can now explicitly choose between RSA and ECDSA key types, offering greater flexibility depending on compatibility or performance requirements.

you are viewing a single comment's thread
view the rest of the comments

[–] qualia@lemmy.world 1 points 1 month ago (5 children)

I'm willing to be the dumbest member of this community. But on the off chance anyone else doesn't understand what problem Nginx Proxy Manager solves:

Many ISPs only allow traffic on ports 80 and 443. But distinct from a website where all pages are part of a single process, separate web apps (photos, blogs, calendar, etc) are all made by different people and need their own port.

Nginx Proxy Manager can therefore be the only thing listening at ports 80/443 and then can seamlessly forward the user to the correct port using HTTPS.

Smart people: constructive critiques are welcomed.

[–] cm0002 4 points 1 month ago (1 children)

That's one problem it solves, but NPM is really just a frontend for Nginx Reverse Proxy.

And a reverse proxy is one of the basic security steps you need to take when exposing something to the open Internet. You want everything forwarded through it and spend most of your time hardening it and the server it's running on (and it should be the only thing running on that server, all other services should be running elsewhere, ideally)

[–] qualia@lemmy.world 1 points 4 weeks ago (1 children)

Crap, I'm in the process of setting up a headless Ubuntu server on my desktop to eek the maximum amount of CPU/GPU/RAM out of it for AI stuff and was planning on controlling it via my laptop.

I don't particularly care about privacy on that desktop, but would my ignorance of security hardening open me up to rogue hackers using my machine for their own purposes if I were to set it up so I could control it remotely (not just hardwired)?

[–] cm0002 2 points 4 weeks ago

For just one person limited use like that, i'd just use a VPN for whenever you're away from home.

But you could learn a bit about hardening and expose it anyways if you want, I personally just want to be able to access my stuff from anywhere so I spend a decent amount of time hardening.

It's not too hard, you really just need a certain baseline to defend against script kiddies and bot mass scanners. Unless you're a business or a high value target or something that'll attract the skills of "real" hackers

load more comments (3 replies)