281–290 of 501 posts
Earlier quoted context omitted.
They could take the Postgres naming approach. Ingress was forked; the Post fork version of Ingress was called "Post"gres. So maybe name this new project "PostX" (for Post + nginx). Though that might sound too similar to posix.
"Postginx" has a nice ring to it, could be an alcoholic beverage, a name of a generation, or even a web server.
Earlier quoted context omitted.
Yeah, I've been with F5 since 2010 - gotta love those old PortMasters though, Livingston was good times, until Lucent took over. I was there 95-98. I don't know what else there is to say really. The QUIC/HTTP/3 vuln was found in NGINX OSS, which is also the basis for the commercial NGINX+ product. We looked at the issue and decided that, by our disclosure policies, we needed to assign a CVE and make a disclosure. And…
Oh my god, the Internet is such a small place. Good to hear you're doing well - we interacted a bit when I was running an ISP in the 90s as well. (Dave Andersen, then at ArosNet -- we ran a lot of PM2.5e and then PM3s). And appreciate the clarification about the CVE disagreement.
And the customers were, by and large, great.
It is scary to think about how much of web relies on projects maintained by 1 or 2 people.
Earlier quoted context omitted.
SSH was a replacement for Telnet. But any weaknesses at the TTY level is orthogonal to that, right? Unless you mean, having thin clients use SSH as opposed to directly running serial cables throughout a building to VT100 style hardware terminals, and therefore being vulnerable to eavesdropping and hijacking? But I think when we talk about TTY we mostly don’t refer to that kind of situation. If someone talks about TTY…
SSH was a replacement for RSH, not telnet.
rsh was common on internal networks, but almost never used on the wider Internet. telnet was everywhere all across the net.
ssh was a revelation and it replaced telnet and authenticated/non-anonymous ftp primarily.
And also sometimes rsh, but less importantly.
Nginx loves to pretend it’s 1995. It barely has http3 support and does insanely stupid things by default.
No wonder people move to haproxy, Traefik, caddy, etc. Cloudflare doesn’t use it anymore for good reason.
Earlier quoted context omitted.
This surely is the question. Why not Angie?
The main criticism is that it requires signing a CLA, so they might switch to a non-free license any day now.
It is scary to think about how much of web relies on projects maintained by 1 or 2 people.
IME, the best software is written by "1 or 2" people and the worst software is written by salaried teams. As an end user, it's only the encroachment by the later that scares me.
Too bad every team I've ever worked on as a consultant does the opposite. The biggest piles of shit I've ever seen created have all been the product of 10 people doing 2 people's worth of work...
>freenginx.org IANAL, but i strongly recommend reconsidering the name as the current one contains a trademark.
>freenginx.org IANAL, but i strongly recommend reconsidering the name as the current one contains a trademark.
Not necessary. It’s not like F5 is going to go to Russia and file suit against any of them.