pfSense slanders OPNsense with fake domain and Nazi images, loses in court reddit / BSD ---------------------------------------------------------------------- rootwyrm · 2017-11-30 18:32 Holy. Fucking. Shit. This is the same pfSense that throws an absolute fit and sends out lawyers and death threats over anyone using anything they decided is their 'trademark.' Part of their response? > As to the bad faith registration, the Respondent states that the disputed domain name was registered prior to any notification of a dispute, and prior to the acquisition of any alleged trademark rights by the Complainant. Yeah. Complete and total lack of ethics or morals much? ---------------------------------------------------------------------- htilonom · 2017-11-30 19:50 OPNsense is a pfSense fork that's known for abusing open source and stealing pfSense code. I've been calling them out for quite some time now. It's ridiculous that OPNsense is milking this to portray themselves as good guys. It's also obvious that's all they got. I've created a sub to document most of scams they pulled, like attempt to steal pfSense trademark in Europe or constant Wikipedia abuse. Trademark theft attempt https://www.reddit.com/r/OPNscam/comments/4ocp d7/opnsense_tried_to_steal_pfsense_trademark_for/ In the blog post Jos talks about Wikipedia yet he forgets his own bad faith actions like promoting OPNsense on Wikipedia as well as editing pfSense Wikipedia page to insert OPNsense propaganda. That's of course against all Wikipedia rules. These links prove it (need to be on desktop and not mobile for links to work) Jos https://en.wikipedia.org/w/index.php?limit=50&title=Special%3ACont ributions&contribs=user&target=Joswp&namespace=&tagfilter=&start=&end= Franco (main OPNsense developer) https://en.wikipedia.org/w/index.php? limit=50&title=Special%3AContributions&contribs=user&target=Netfitch&n amespace=&tagfilter=&start=&end= Here's /u/gonzopancho predicting how OPNsense will try to create drama about opnsense.com https://twitter.com/gonzopancho/status/933447092999217152 There's many more documented events showing OPNsense developers and their associates being toxic: https://www.reddit.com/r/OPNscam/ What's happening now is that OPNsense is trying to wash their sins by using this parody website (which was awesome btw) to portray pfSense as the villain, nevermind the constant and actual open source abuse by OPNsense. **Oh and OP is obviously an OPNsense minion considering it's a single purpose account using scary words for better drama effect like "slander" (not true or even mentioned by WIPO) or "nazi images" which is hilarious to portray a meme video about downfall like that. OP also claims "court" despite the fact that WIPO is *NOT* a court.** ---------------------------------------------------------------------- fwaggle · 2017-11-30 19:50 "Nazi images" is a bit much, that meme has been used all over the place in the IT realm and at almost no point has ever indicated association with nazism. Having said that this being brought to my attention does make me reconsider that I run pfSense on my router. :| ---------------------------------------------------------------------- htilonom · 2017-11-30 19:52 Well only if you look at it from OPNsense point of view. If you see that OPNsense tried to steal pfSense trademark in EU, that remove pfSense copyrights from their code or that they started in 2015 by spreading lies about pfSense and attacking their developers... then the parody website doesn't sound that bad. And that website was awesome. **Oh and OP is obviously an OPNsense minion considering it's a single purpose account using scary words for better drama effect like "slander" (not true or even mentioned by WIPO) or "nazi images" which is hilarious to portray a meme video about downfall like that. OP also claims "court" despite the fact that WIPO is *NOT* a court. Classic OPNsense propaganda.** ---------------------------------------------------------------------- htilonom · 2017-11-30 19:54 > "Nazi images" is a bit much, that meme has been used all over the place in the IT realm and at almost no point has ever indicated association with nazism. Of course it is, but that's what OPNsense is about. They've been spreading drama since their first days. Just look at their website and BS reasons for forking pfSense (and those reasons are from 2015 so a lot of was just made up) https://wiki.opnsense.org/fork/thefork.html ---------------------------------------------------------------------- rootwyrm · 2017-11-30 19:58 Except that's a complete load of slanderous bullshit spread by pfSense. Never happened. pfSense got pissed off because they forked an allegedly open source project, leading to pfSense's bullshit of putting much of the code behind "contributor agreements." Oh, and remind me again... which was the project where a lead developer told somebody to go commit acts of beastiality, regularly? **Oh. Right. It was your coworker.** Go back to spreading your slanderous shit on that "OPNscam" sub you run. ---------------------------------------------------------------------- htilonom · 2017-11-30 20:01 > Except that's a complete load of slanderous bullshit spread by pfSense. Never happened. pfSense got pissed off because they forked an allegedly open source project, leading to pfSense's bullshit of putting much of the code behind "contributor agreements." Never happened? Here's rock solid evidence it happened. Here's Franco Fichtner, lead OPNsense developer trying to defend their attempted trademark attempt: https://i.imgur.com/BCGNzDz.png Wanna guess why he deleted his account ? >Oh, and remind me again... which was the project where a lead developer told somebody to go commit acts of beastiality, regularly? >Oh. Right. It was your coworker. What? hahaha ok got proof for that or something? ---------------------------------------------------------------------- rootwyrm · 2017-11-30 20:15 Yeah, "rock solid evidence" that totally held up in an actual court. Oh wait. An actual court said Netgate was so egregious there was absolutely no question they acted in bad faith trying to interfere with OPNsense's trademarks. Why don't you go back to fellating Jim's dog? ---------------------------------------------------------------------- htilonom · 2017-11-30 20:19 Wow you're such a nice guy. Sure, go ahead ignoring the fact that OPNsense developer defended trademark theft attempt. Or the fact that they strip pfSense copyrights from their code ;) That speaks more about your intentions really... **Oh and WIPO isn't a court ;)** ---------------------------------------------------------------------- FrozenWes · 2017-11-30 20:50 This kinda petty bullshit only makes everyone involved look like immature idiots. Going so far as taking it to court only makes it worse. I don't care who started what and who's insulting whom, they're all acting like teenagers. And people wonder why there's such a huge lack of contributors in open source... ---------------------------------------------------------------------- rootwyrm · 2017-11-30 21:50 Yeah, I'm gonna go ahead and stop you there. If you don't go to court to enforce your trademark, you lose your trademark. That's how it works. And when you have someone who's hiding behind a Domain Proxy service, and non-responsive to abuse reports? You can't ask them nicely, and they won't do anything but give you the middle-finger anyway. The only people who look like immature idiots here? Are the children at Netgate who *actually tried to claim* that because OPNsense didn't say "we don't want you to make a slanderous page about us" they could totally use their trademarks any way they liked. ---------------------------------------------------------------------- htilonom · 2017-11-30 22:22 I like how you ignore the fact that OPNsense tried to steal pfSense trademark in EU or that they have been "forgetting" to include pfSense copyrights in their code but parody website is bad, bad :) It's beautiful how you actually spin this to look like Netgate tried to take OPNsense trademark. Over a parody web site :) Despite the fact that you ignored proof of Franco Fitchner defending therefore confirming their attempt to steal pfSense trademark in EU: https://i.imgur.com/BCGNzDz.png ---------------------------------------------------------------------- lewisinc · 2017-11-30 22:27 This seems like two very toxic communities. Good going. ---------------------------------------------------------------------- NerdVsGeek · 2017-12-01 00:04 It's hard to steal something that is BSD licensed. They are freely giving credit on their website as well: https://opnsense.org/about/legal-notices/ (Note, I am a pfSense user currently but this drama is the root cause of me switching to an Ubiquiti solution for my next firewall/router purchase in January.) One question - if OPN is behind the opnsense.com "parody" site, then why is it registered through a U.S. Registrar and the name behind it is assoficated with pfSense/Netgate? ---------------------------------------------------------------------- doxavg · 2017-12-01 00:07 Genuinely curious as to which reasons you feel are BS - or are you saying the reasons are right, but the premise that those are the reasons is BS? As someone who is pretty familiar with the pfSense code and development model from the time period prior to the fork, I don't find fault in the technical, security, or quality arguments. I stopped following pfSense as closely after I stopped contributing so I can't comment on the community or transparency arguments. Don't care for, or about the OPNSense/pfSense drama, don't have time or energy to invest in that worthless discussion. ---------------------------------------------------------------------- htilonom · 2017-12-01 00:35 >It's hard to steal something that is BSD licensed. >They are freely giving credit on their website as well: https://opnsense.org/about/legal-notices/ "giving credit" is not the same as respecting copyrights. OPNsense has been stripping out almost all pfSense copyrights from the code, uploading it as their own. Example: https://pbs.twimg.com/media/CVCceq2VAAAHZ4T.png:large >One question - if OPN is behind the opnsense.com "parody" site, then why is it registered through a U.S. Registrar and the name behind it is assoficated with pfSense/Netgate? I didn't say that. However OPNsense conveniently includes pfSense in the title, to portray the whole project badly. Just as they attempt to portray WIPO as an actual court. Same is with OP, single purpose account with intention to cause damage. No slander or "nazi" imagery were used. Hilarious really. ---------------------------------------------------------------------- htilonom · 2017-12-01 00:43 No, I'm saying the reasons are bull. First, understand that those reasons are there from January 2015. They wrote all those reasons as if they already achieved it. It's classic bragging writing by Ad Schellevis from OPNsense, he also wrote the "drama" piece about opnsense.com. So let's analyze: > Technical / code quality OPNsense broke almost every feature pfSense had. Including making pfSense packages not work. They claimed they did it for code quality yet current OPNsense codebase consists mostly of hacks and patches. They broke VLAN's over 5 times. Breaking VLAN's in product you claim to be production ready is just unacceptable. >Security For security they point out how they believe the GUI should not run as root but what they don't tell you that GUI *still* runs as root in OPNsense. They never fixed that and never will. Speaking of security, starting today OPNsense is running an end of life FreeBSD version. And if that wasn't bad, they tried to downplay or hide the fact they had MANY critical CSRF vulnerabilities. >Quality I cannot accept the fact that broken VLAN's show of code quality. I just can't >Community This one is a real gem. They forked pfSense and claimed they have community. They literally had non existing community for a long time. These days is mostly just Franco's minions (main dev) who eat all the bull he serves them >Transparency They claim to be transparent yet they hide vulnerabilities or run a closed source "Supported Edition" of OPNsense. Their literally said "Since Netgate bought the majority share of pfSense and renamed the company to ESF it has been difficult to understand the direction they want the project to go". Pure propaganda. >Restore a firm open source project This one is also hilarious. Since their day one they first claimed pfSense is not open source. A pfSense fork claiming pfSense is not open source. Then they said "not true" open source because pfSense had ESF license, almost identical as Apache one. Now pfSense has Apache 2.0 license but OPNsense still did not change their views. The whole "about the fork" page just shows how malicious they are. ---------------------------------------------------------------------- doxavg · 2017-12-01 01:29 Fair enough, interesting perspective. I agree, they haven't managed to privsep the web UI - neither has pfSense (not that I'm aware of any attempt to). But let's be fair - the pfSense code base isn't exactly sparkling clean...it still contains some of my code (as does OPNSense). pfSense itself was a fork from m0n0wall - a system that used HTTP Basic for authentication and had no concept of users, let alone roles. Changing the authentication scheme to allow multiple users and subsequently multiple roles lead to the discovery/creation of a significant amount of security issues that literally weren't an issue when it was a single user system. To add to it, most of that code was worked on by folks that weren't full time developers, some of which who barely understood how PHP worked. While you aren't claiming that the pfSense code is clean, it comes across as implied when compared to the OPNSense code base (which I haven't personally looked at).   With no continuous integration or any ability to automate regression tests, it's actually a miracle that either project achieves a release that is even relatively bug free. Most of the infrastructure of the pfSense code is (was circa 2010 - and it doesn't appear to have changed in any significant since) a massive hack with little regard to architecture and a significant disregard to separation of web interface code from non-web interface code. Whether or not the reasons they posted are a correct representation of why they forked, I do feel that the technical ones weren't incorrect. Way too much of the work that Netgate has had to do in the last ~6 yrs is fix bugs instead of refactoring and making new features. I would imagine OPNSense is in much the same boat.   Sorry, staying out of the drama, so ignoring your other points. I'm assuming you have worked on the code base or for Netgate to be as passionate about it as you are. On the topic of license however...I'm not thrilled that my code has been relicensed (note - my commits all predate the CLA) as it was intended to be BSD licensed, but meh...whatever, my intent for my contributions was always "do whatever the fuck you want to do with this crap" anyway. ---------------------------------------------------------------------- NerdVsGeek · 2017-12-01 01:42 There is no stripping of copyright statements in that image. They left the copyright statements intact and removed all project names in the comments. While dubious in nature, this is perfectly legal. You stated that in your original post. > What's happening now is that OPNsense is trying to wash their sins by using this parody website (which was awesome btw) to portray pfSense as the villain, nevermind the constant and actual open source abuse by OPNsense. ---------------------------------------------------------------------- htilonom · 2017-12-01 01:56 I love a nice and pleasant discussion! Seriously, thanks for taking time to discuss about it. >Fair enough, interesting perspective. I agree, they haven't managed to privsep the web UI - neither has pfSense (not that I'm aware of any attempt to). But let's be fair - the pfSense code base isn't exactly sparkling clean...it still contains some of my code (as does OPNSense). pfSense itself was a fork from m0n0wall - a system that used HTTP Basic for authentication and had no concept of users, let alone roles. Changing the authentication scheme to allow multiple users and subsequently multiple roles lead to the discovery/creation of a significant amount of security issues that literally weren't an issue when it was a single user system. To add to it, most of that code was worked on by folks that weren't full time developers, some of which who barely understood how PHP worked. While you aren't claiming that the pfSense code is clean, it comes across as implied when compared to the OPNSense code base (which I haven't personally looked at). I agree, pfSense code and therefore OPNsense code is not exactly sparkling clean. Biggest problem is PHP (which is bad by itself) and running GUI as root. You described the issues with m0n0wall good, I don't have anything to add. However, if you compare the work on code and code quality pfSense and OPNsense it's clear pfSense is superior in every segment. Which is opposite of what OPNsense is claiming. That's my problem with that page. They appeared and claimed to be better despite being worse. On top of that, OPNsense is claiming they are better by "innovation". Code frequency graphs prove them wrong: pfSense https://github.com/pfsense/pfsense/graphs/code-frequency OPNsense https://github.com/opnsense/core/graphs/code-frequency >With no continuous integration or any ability to automate regression tests, it's actually a miracle that either project achieves a release that is even relatively bug free. Most of the infrastructure of the pfSense code is (was circa 2010 - and it doesn't appear to have changed in any significant since) a massive hack with little regard to architecture and a significant disregard to separation of web interface code from non-web interface code. Whether or not the reasons they posted are a correct representation of why they forked, I do feel that the technical ones weren't incorrect. Way too much of the work that Netgate has had to do in the last ~6 yrs is fix bugs instead of refactoring and making new features. I would imagine OPNSense is in much the same boat. I agree with difference that OPNsense listed those reasons for publicity as if they achieved them. That's just wrong. They listed the reasons but they didn't do any of the proposed changes or had any real progress. That's my issue with them. >Sorry, staying out of the drama, so ignoring your other points. I'm assuming you have worked on the code base or for Netgate to be as passionate about it as you are. On the topic of license however... No and no. Not even a developer. Closest description is occasional scam revealer. Maybe you've heard about Anonabox? ;) > I'm not thrilled that my code has been relicensed (note - my commits all predate the CLA) as it was intended to be BSD licensed, but meh...whatever, my intent for my contributions was always "do whatever the fuck you want to do with this crap" anyway. You could contact them and discuss it. I've seen many projects and products change licenses but I don't how I would feel if my code was relicensed. I'm not a dev, sorry. ---------------------------------------------------------------------- NerdVsGeek · 2017-12-01 01:58 I started to edit my earlier post, then decided otherwise. The OPNsense.org post that talks about the WIPO ADR process does not state WIPO is a court, anywhere, just the part of the OP's title is inaccurate. This is very common and is hardly unique to reddit (I see this all the time on slashdot.) My personal opinion is that while you're certainly passionate about pfSense, I don't like that someone associated with Rubicon Communications/pfSense (Jamie Thompson) owned this domain to harm or hinder another fellow open source project, no matter the bad history between the two projects and parent companies. Just so we're clear here, Rubicon Communications LLC has the copyright on the Netgate.com site, so they are the same entity from my perspective. This just harms all open source projects in the long run. ---------------------------------------------------------------------- htilonom · 2017-12-01 02:00 What do you mean there's no stripping of copyrights? >part of pfSense by Scott Ullrich is changed to >Copyright Scott Ullrich They left out "part of pfSense" deliberately. And that's just an old example, today they just upload pfSense code without any copyrights. Like this https://www.reddit.com/r/OPNscam/comments/4sk64k/opnsense_ge ts_caught_in_yet_another_code_theft/ ---------------------------------------------------------------------- NerdVsGeek · 2017-12-01 02:08 No. The full text read: > part of pfSense by Scott Ullrich > Copyright (C) 2004-2011 Scott Ullrich, All rights reserved. The Copyright notice as defined by U.S.C. 401 (Copyright Act) is defined as the following (copied from the [Wikipedia Entry](https://en .wikipedia.org/wiki/Copyright_notice#Form_of_notice_for_visually_perce ptible_copies)): > 1. The symbol © (letter C in a circle); the word “Copyright”; or the abbreviation “Copr.” > 2. The year of first publication. If the work is a derivative work or a compilation incorporating previously published material, the year date of first publication of the derivative work or compilation is sufficient. > Examples of derivative works are translations or dramatizations; an example of a compilation is an anthology. The year may be omitted when a pictorial, graphic, or sculptural work, with accompanying textual > > matter, if any, is reproduced in or on greeting cards, postcards, stationery, jewelry, dolls, toys, or useful articles. > 3. The name of the copyright owner, an abbreviation by which the name can be recognized, or a generally known alternative designation of owner > > Example: © 2012 Jane Doe The code comment "part of pfSense by Scott Ullrich" is **not** part of the copyright statement. ---------------------------------------------------------------------- htilonom · 2017-12-01 02:09 > The OPNsense.org post that talks about the WIPO ADR process does not state WIPO is a court, anywhere, just the part of the OP's title is inaccurate. This is very common and is hardly unique to reddit (I see this all the time on slashdot.) It's also very common for OPNsense to behave like this. OP is just another single purpose account by one of them. The whole blog post is used to portray themselves as good guys. WIPO is not a court and no nazi images were used (like seriously, marking famous downfall scene to be "nazi" is just malicious). Then they pile up bunch of other stuff literally abusing WIPO decision to defend their open source “principles” and attack pfSense directly for greater drama effect. Not to mention they bring up Wikipedia, in effort to portray themselves as victims, even though Jos and Franco both got caught in editing pfSense wiki and inserting OPNsense propaganda all over Wikipedia (which is against the rules). >My personal opinion is that while you're certainly passionate about pfSense, I don't like that someone associated with Rubicon Communications/pfSense (Jamie Thompson) owned this domain to harm or hinder another fellow open source project, no matter the bad history between the two projects and parent companies. Just so we're clear here, Rubicon Communications LLC has the copyright on the Netgate.com site, so they are the same entity from my perspective. I respect your opinion and I agree that OPNsense has right to opnsense.com domain. But I just don't agree with the way they want to wash their own sins by abusing this decision. >This just harms all open source projects in the long run. Well OPNsense has been harming open source for quite some time. They rely on drama from their first days. ---------------------------------------------------------------------- htilonom · 2017-12-01 02:12 But that still doesn't mean you can tailor the copyright as you please. Besides, that's just an example. Above's the link with IPsec example where they just re-use the code without any copyrights. Or this one https://www.reddit.com/r/OPNscam/comments/4sk78j/more_code _theft_opnsense_developers_steal_more/ Or this https://www.reddit.com/r/OPNscam/comments/4ocu2w/franco_gets_c alled_out_for_code_theft/ ---------------------------------------------------------------------- gonzopancho · 2017-12-01 02:20 > While dubious in nature, this is perfectly legal. actually, it isn't. ---------------------------------------------------------------------- gonzopancho · 2017-12-01 02:34 actually it is. further, it means that Deciso and/or Franco have committed copyright infringement. I'll suggest you to google for "Fraudulent Removal of Copyright Notice." ---------------------------------------------------------------------- doxavg · 2017-12-01 02:34 > don't have anything to add. However, if you compare the work on code and code quality pfSense and OPNsense it's clear pfSense is superior in every segment. Which is opposite of what OPNsense is claiming. That's my problem with that page. They appeared and claimed to be better despite being worse. On top of that, OPNsense is claiming they are better by "innovation". Code frequency graphs prove them wrong: pfSense https://github.com/pfsense/pfsense/graphs/code-frequency OPNsense https://github.com/opnsense/core/graphs/code-frequency   I'm not sure I read that much into it tbh, every marketing page is full of fluff; more so when money or ego is involved. Interesting thing about those graphs though...the commit graphs actually look better for OPNSense :)   > I agree with difference that OPNsense listed those reasons for publicity as if they achieved them. That's just wrong. They listed the reasons but they didn't do any of the proposed changes or had any real progress. That's my issue with them.   Agreed on the principle - it would be much clearer if they indicated status on where they were with the changes. Hoping both of the teams finally ditch the root run webui with access to everything architecture and implement a proper privsep architecture soon. The web ui run as root needs to die. I believe FreeNAS has made significant strides towards this recently, although there won't be much code that is relevant in the project any more to be pulled back in, maybe the mechanisms will provide value to the teams. ---------------------------------------------------------------------- NerdVsGeek · 2017-12-01 02:51 The comments were certainly altered, and while I don't like that aspect, the _copyright notice_ for Scott Ullrich was not changed. Rather than just a vague Google search, that just brings up search results that describe penalties and such, but no examples, can you actually provide any references to court documents with examples where such changes were deemed removal of a copyright notice? ---------------------------------------------------------------------- NerdVsGeek · 2017-12-01 03:24 Interesting feature on GitHub, if you click on the <> symbol out to the left of the pane it will let you view the file as it existed at the time. Looks like the copyright notices were still intact when those commits happened. Thank you very much for pointing out all of this bad acting. It's certainly reinforced my decision not to support pfSense any more and just switch to Ubiquiti instead. ---------------------------------------------------------------------- 65a · 2017-12-01 03:25 Between this clown garbage and the AESNI requirement, I think OpenBSD and a simple pf config is looking more and more reasonable. ---------------------------------------------------------------------- gonzopancho · 2017-12-01 03:34 > can you actually provide any references to court documents with examples where such changes were deemed removal of a copyright notice Yes I can. No, I'm not going to. This is reddit, and I have already wasted enough time on reddit in the past 12+ years. The larger issue is that I'm not about to file suit against a couple clowns with no resources in the Netherlands. Even if I just went for statutory damages, getting the decision and being able to collect it are two very different things. So it's true they're very (very) likely guilty of copyright infringement. But it's also true that it's very (very) unlikely they'll suffer for it. At the end of the day, what matters is they simply can't keep up. We have better talent, and more of it. We have a better and larger community. ---------------------------------------------------------------------- kcuf · 2017-12-01 06:21 > (Note, I am a pfSense user currently but this drama is the root cause of me switching to an Ubiquiti solution for my next firewall/router purchase in January.) Seriously. I use ubiquiti just for APs atm and pfSense for router/firewall. I looked into it a while back, but can't remember, is the ubiquiti solution on par with pfSense for features, performance, and security? ---------------------------------------------------------------------- daericg · 2017-12-01 06:33 Wish I could upvote more that once ---------------------------------------------------------------------- cbuechler · 2017-12-01 06:33 > I'll suggest you to google for "Fraudulent Removal of Copyright Notice." hmm... https://github.com/pfsense/pfsense/commit/81299b5c4ec66f76eea0 a0a368b586ff65b49170 ---------------------------------------------------------------------- dd3fb353b512fe99f954 · 2017-12-01 06:43 Or just use the upstream projects? ---------------------------------------------------------------------- piglit3 · 2017-12-01 06:58 Recently Ubiquiti had a really embarrassing vulnerability, I am skeptical about their approach towards security (["One of the reasons for this behaviour is the used PHP version (PHP/FI 2.0.1 from 1997)"](https://www.sec-consult.com/fxdata/seccons/ prod/temedia/advisories_txt/20170316- 0_Ubiquiti_Networks_authenticated_command_injection_v10.txt)). ---------------------------------------------------------------------- ZarK-eh · 2017-12-01 07:16 Openbsd? I believe there is securityrouter or securerouter distro based on openbsd. Unless info: A hdd dieded in my network appliance and will be distro hopping, but will probably settle on opnsense again. ---------------------------------------------------------------------- alive1 · 2017-12-01 07:42 Not ever using pfsense or opnsense ever again. Thanks. ---------------------------------------------------------------------- pyvpx · 2017-12-01 08:41 just. use. openbsd. ---------------------------------------------------------------------- pyvpx · 2017-12-01 08:44 > At the end of the day, what matters is they simply can't keep up. yes, if 3.0 looks like I think it looks, all of this discussion is moot. ---------------------------------------------------------------------- phessler · 2017-12-01 10:25 > Openbsd? I believe there is securityrouter or securerouter distro based on openbsd. yes, it's called "openbsd", and is available at www.openbsd.org. ---------------------------------------------------------------------- Zetbo1 · 2017-12-01 11:30 Thank you for helping me to make my decision to switch from pfsense to opnsense. I was torn about AES-NI bullshit and you helped me to switch to opnsense and I have never been happier. I hope other will do the same. If you are not paid slander, get mental help. If you are paid slander you should disclose who is paying you or you look like a fool...wait, you already look like a fool. ---------------------------------------------------------------------- Zetbo1 · 2017-12-01 11:49 I know that this is a BSD-subreddit, but I tought that Ubiquiti has problem not releasing their GPL modifications. I have to go to work, so I don't have time to find links. I switched to opnsense from pfsense after the aes-ni bs happened. Opnsense works fine on my APU. That troll account that you are discussing with helped my decision. ---------------------------------------------------------------------- Paspie · 2017-12-01 11:52 Probably because open source projects generally only accept decent quality code, therefore we only attract decent programmers (or 'hackers', whatever fits you best), most of the crappy ones go down the proprietary route. ---------------------------------------------------------------------- kcuf · 2017-12-01 17:29 Gross, that's pathetic, especially their time to release a fix for such a large vulnerability! ---------------------------------------------------------------------- kcuf · 2017-12-01 17:34 Any recommendations on articles/tutorials describing a good setup? Also, any recommendations for decent prebuilt hardware that I could put this on to throw in my rack? ---------------------------------------------------------------------- 65a · 2017-12-02 01:58 https://calomel.org/pf_config.html for hardware I would look for openbsd compatibility, but something like an atom or celeron board with two intel nics will usually work fine. ---------------------------------------------------------------------- NerdVsGeek · 2017-12-02 02:59 They were one of the first vendors to patch their AP's against KRACK. I'm still waiting for mine to even acknowledge KRACK. ---------------------------------------------------------------------- kcuf · 2017-12-02 04:57 Ya I saw that, I thought they handled that well. But this issue with root login is bad. ---------------------------------------------------------------------- htilonom · 2017-12-02 22:31 Enjoy running "security oriented fork" based on End of Life FreeBSD. Who looks like a fool now? ---------------------------------------------------------------------- htilonom · 2017-12-02 22:32 "Troll" account also reveals scams. It's not my first rodeo bub. Search for anonabox. ---------------------------------------------------------------------- NerdVsGeek · 2017-12-02 23:52 Background: I'm an engineer who writes data analysis tools for a software security company. It looks like 4 months for the patch? That's not unheard of for a large-ish company. It's slower than I'd really like to see, there are a lot of variables for a bug like that - especially around how hard it may be to reproduce, etc. Then there is the effort to QA each platform and try to validate that the patch is valid. This last bit can take a long time depending on how hard it is to reproduce. ---------------------------------------------------------------------- kcuf · 2017-12-03 00:34 Ya it looks like 4 months. The problem I have is the significant impact of this issue and no possible mitigation should have warranted a much more aggressive effort to address this issue. There was a lot of back and forth in the beginning, which is expected for normal bugs, but because of the severity, I think the company should have expedited their investigation. ---------------------------------------------------------------------- NerdVsGeek · 2017-12-08 04:52 Did Rubicon/Netgate purchase ESF? If they did purchase ESF, then they purchased the ESF copyrights. Is there a shareable story behind this? (Curious minds want to know, but only if it's not subject to an NDA). ---------------------------------------------------------------------- cbuechler · 2017-12-09 06:03 > Did Rubicon/Netgate purchase ESF? Nope. > Is there a shareable story behind this? Not at this time. The final chapter is still being written. Its contents determine whether the book is published, so to speak. ---------------------------------------------------------------------- NerdVsGeek · 2017-12-11 20:01 Well, now. That's interesting to say the least. Thanks! ---------------------------------------------------------------------- grahamperrin · 2023-07-25 20:00 > Goodbye everyone, Hello, Wayback Machine: https://web.archive.org/web/20230607204138/https://old.reddit.com/r/BS D/comments/7go6i6/pfsense_slanders_opnsense_with_fake_domain_and/#dql1 m3x