111–120 of 228 posts
With the original open sourcing license of nginx in doubt, it is prudent for open source projects to look into alternatives?
There is also Caddy, a go based webserver, which is Apache licensed I think. [2]
Then there is also lighttpd, which is small and fast, but 3-clause bsd. [3]
My bad translation of a related part from Sysoev's interview to a russian journal "Hacker"[0] made in 2012: - Interesting: you were working at Rambler while developing nginx. Did Rambler had any rights? That's a subtle question. How did you manage to keep the rights for project? Yes, that is a subtle question. It interests others beside you, and we thoroughly worked on that. Russian law works this way: the company ha…
The Rambler Internet Holding (edit: it's legal name is Rambler Group LLC) company found that it's exclusive rights on NGINX web server, which was developed by it's employees with use of corporate resources, were violated by third parties. The company gave the right for infringment claims to Lynwood Investments CY Ltd (named A&NN Holdings Limited at the time of the deal), which has a competence in this type of cases.
Lynwood Investments CY Ltd had appealed to law enforcement bodies for the evalution of this situation. They recognized Rambler Internet Holding as victim of actions by unidentified violators (sic!) and initiated a criminal case.
Lynwood Investments CY Ltd would not comment the case until the court's decision. Wherein we would try to restore the justice with all ways possible and we reserve right to file lawsuits in any jurisdiction where it's needed to protect our interests.
[0]https://t.me/thebell_io/4315 (NB: yes, Telegram)
Best practices for side projects (US): - Never give work full rights to everything you make on your own time. - Never use company hardware, software, time or offices to develop a side project you might want to monetize commercially later. - Charge work a "1 node license fee" of $1 with an invoice and a standard commercial software EULA if you intend to try your creation at work. Also specify that it includes maintena…
The thing is I am not sure if Igor was developing Nginx on his own time. IANAL as well, but I am not sure if it counts if part of the work was done from his Rambler workplace.
Earlier quoted context omitted.
This is what's really concerning. If FSB was able to actually implement something and shell all nginx boxes (and thusly obtain SSL certs, intercept communications, etc..) imagine how much access they'd have.
that's not going to happen, too many security experts constantly monitoring nginx. That's the beauty of it being a high profile open source project.
Oh my, I still see people in the comments who naively think this is a copyright issue. Seriously? 15 years after the alleged event? With physical violence against software developers? It's only one among thousands of cases when putinists rob successful companies. The world must put more pressure on putinism, because eventually all the stolen resources turn into imprisonments of people in the country and deaths of peo…
So whether or not the claim was unjustified, it might become a huge problem not just for the individual developers of Nginx but for everybody distributing it or using it. And that has a lot to do with how copyright works.
Earlier quoted context omitted.
"It's open source, someone surely is doing regular thorough security audits."
Auditing one of the world's most used pieces of internet facing software that also isn't "a huge codebase"? Yes I do think nginx will be just fine. Security experts are constantly combing through that sort of software looking for holes, as well as AI tools. duh. It ups your brand to find holes.
always wondered, is it pronounced 'en-gin-ex' or 'N-ginx', there was a debate in my office
I was told that N-ginx is a curse word in Chinese, so I pronounce it En-Gin-Ex. I think the former is more intuitive though
Don't know that many swear words in Chinese, but I know that that "ginks" isn't really pronouncable in Chinese. You could do "ging", but the "k" and the "s" would then need to be separate syllables; the best you could get is "en ging ke se", which isn't really close enough to "N-ginks" to be dangerous.
(Similarly, "golf" ends up as three syllables: "gao er fu", plus "qiu" added to the end to clarify that it's a game involving a ball.)
always wondered, is it pronounced 'en-gin-ex' or 'N-ginx', there was a debate in my office
From the official FAQ[1]: > How do you pronounce “NGINX”? > Correct: en-juhn-eks, Engine-X > Incorrect: en-jingks I wouldn't be surprised if it's actually an abbreviation of "engine-x", but I can't find any better source that explains how they came up with the name. Still, this source pretty much implies it. [1] https://www.nginx.com/resources/wiki/community/faq/#how-do-y...
> nginx [engine x] is an HTTP and reverse proxy server, a mail proxy server, and a generic TCP/UDP proxy server, originally written by Igor Sysoev.
With the original open sourcing license of nginx in doubt, it is prudent for open source projects to look into alternatives?
Even if Russian court voids the license (which can easily happen because there's no justice in Russia), it won't affect any other jurisdiction.
always wondered, is it pronounced 'en-gin-ex' or 'N-ginx', there was a debate in my office
I was told that N-ginx is a curse word in Chinese, so I pronounce it En-Gin-Ex. I think the former is more intuitive though
It was "engine-x" from the very start.