norden.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Moin! Dies ist die Mastodon-Instanz für Nordlichter, Schnacker und alles dazwischen. Folge dem Leuchtturm.

Administered by:

Server stats:

3.4K
active users

#proxy

5 posts4 participants0 posts today

Just released: #swad v0.3!

github.com/Zirias/swad/release

swad is the "Simple Web Authentication Daemon", your tiny, efficient and (almost) dependency-free solution to add #cookie + login #form #authentication to whatever your #reverse #proxy offers. It's written in pure #C, portable across #POSIX platforms. It's designed with #nginx' 'auth_request' in mind, example configurations are included.

This release brings a file-based credential checker in addition to the already existing one using #PAM. Also lots of improvements, see details in the release notes.

I finally added complete build instructions to the README.md:

github.com/Zirias/swad

And there's more documentation available: manpages as well as a fully commented example configuration file.

Replied in thread

@nixCraft actually this screams "#GDPR & #BDSG violation" so loudly that even demanding #PII and espechally an #ID should get them sued by @noybeu and @Bundesverband ....

  • Cuz "#OpenAI" has neither "legitimate interest" nor a mandate to even demand to see an ID, much less to store and process it!

This isn't like a contractual agreement or some finance where one could argue "#KYC" is warranted "to combat #fraud"...

  • The only thing worse I've seen is some obscure company that brokers #bandwith with a hidden #proxy feature in #apps...

Just released: #swad v0.2

SWAD is the "Simple Web Authentication Daemon", meant to add #cookie #authentication with a simple #login form and configurable credential checker modules to a reverse #proxy supporting to delegate authentication to a backend service, like e.g. #nginx' "auth_request". It's a very small piece of software written in pure #C with as little external dependencies as possible. It requires some #POSIX (or "almost POSIX", like #Linux, #FreeBSD, ...) environment, OpenSSL (or LibreSSL) for TLS and zlib for response compression.

Currently, the only credential checker module available offers #PAM authentication, more modules will come in later releases.

swad 0.2 brings a few bugfixes and improvements, especially helping with security by rate-limiting the creation of new sessions as well as failed login attempts. Read details and grab it here:

github.com/Zirias/swad/release

did a thing!

Big problem in #selfhosting is making sure you've set things up right: #dns resolution, #ports, rev/ #proxy. _Sometimes_ its helpful to query _from the outside_ of your local network.

`canuseeme` - a single binary #webservice that will query the URI you give it and see if its reachable by randos/services on the internet. A bit like a #webproxy, but can exercise it programmatically, and not limited to HTTP/S ports.

github.com/tezoatlipoca/canuse

I'm developing a Gopher-To-Web proxy in Go. It's named 'go-gopherproxy' and made for myself initially. It's in a very early state but I've already set it up on my own server. So my Gopher hole is available on the web. The repository is here:

https://codeberg.org/fab/go-gopherproxy

I also made an introductory Gopher phlog post about it, which you can view in your Gopher client of choice:

gopher://redterminal.org:70/0/phlog/2025-03-19-go-gopherproxy_-_A_Gopher-To-Web_proxy_in_Go.txt

Or on my selfhosted go-gopherproxy instance on the web:

https://redterminal.org/gopher/0/phlog/2025-03-19-go-gopherproxy_-_A_Gopher-To-Web_proxy_in_Go.txt

#Go #Golang #Gopher #Web #Smolnet #Proxy
Forgejo: Beyond coding. We Forge.go-gopherproxyGopher-To-Web Proxy

One of things I suffer on #FreeBSD using an #Iranian connection, is that all package mirrors are terribly slow.

Currently, as a workaround, I'm using #proxychains with the FreeBSD package manager. Unfortunately, setting a SOCKS5 #proxy through pkg.conf does not seem to work.

Using a proxy or a #VPN is not a big deal for a typical developer based in #Iran. But it's the first time I have to change IP(and route) to properly use an OS's first class package manager.

Maybe I could host a mirror for Iranians if FreeBSD stays as my main OS. Tho I don't see much point with only myself being the FreeBSD user in here.

Och ffs ey. Ich will #Seafile in #Docker mit einem #apache-#Proxy in einer #virtuellenMaschine installieren (weil ich das Testen will und nur Chuck Norris in Prod testet). Warum geht das nicht wenigstens halbwegs out-of-the-box?

Auch ohne den apache-Proxy klappt das nicht. (Edit: da spielt ja jetzt immer noch ein #caddy mit rum, bei dem nicht dokumentiert ist, ob ich ihn wirklich brauche, wenn hinter apache, oder wie da die Einstellungen sein müssen.)

Replied in thread

@cd0 Wow. What a horrible approach of #Digikey. If I have a #proxy, does that solve the problem ? Can I then leave all their tracker crap on and not care less? Or do I need a "quarantined" web session that I then toast? Or use #tails ? Or have I not understood? Why is this so hard? It is like when u go to a shop for cheese they say "No cheese unless you tell me the contents of your fridge and pantry". #adblockers #trackers

Continued thread

@torproject same with #obfs4 bridges: there is no option to say like ports=80,443 or similar, which makes it cumbersome to get said bridges.

And trying to get places to #DontBlockTor that criminalize the use of #Tor is foolish at best.

Wenn ihr auf einem Host Services mit und ohne Docker bereitstellt: wo lebt dann euer Reverse Proxy? Im Docker ist ätzend, weil localhost vom Host kaum erreichbar ist. Auf dem Host ist doof, weil man alle Services, die geproxied werden sollen, dem Host-Network öffnen muss. Also, welche Kröte schlucken?
Welche einfache Lösung für ein lokales Proxy-Netzwerk?