ownCloud 9 is Here
-
NSS is from January. You say that there are details as to why this is outdated (sorry, it's current again) and insecure. But I see no details on that one either. Here are the RPM details. NSS 3.19.1-19 is only a few weeks old. And it is the most current version for RHEL.
rpm -qi nss-3.19.1-19.el7_2.x86_64 Name : nss Version : 3.19.1 Release : 19.el7_2 Architecture: x86_64 Install Date: Fri 15 Jan 2016 03:26:22 PM UTC Group : System Environment/Libraries Size : 2609903 License : MPLv2.0 Signature : RSA/SHA256, Thu 07 Jan 2016 10:18:33 PM UTC, Key ID 24c6a8a7f4a80eb5 Source RPM : nss-3.19.1-19.el7_2.src.rpm Build Date : Thu 07 Jan 2016 08:31:16 PM UTC Build Host : worker1.bsys.centos.org Relocations : (not relocatable) Packager : CentOS BuildSystem <http://bugs.centos.org> Vendor : CentOS URL : http://www.mozilla.org/projects/security/pki/nss/ Summary : Network Security Services Description : Network Security Services (NSS) is a set of libraries designed to support cross-platform development of security-enabled client and server applications. Applications built with NSS can support SSL v2 and v3, TLS, PKCS #5, PKCS #7, PKCS #11, PKCS #12, S/MIME, X.509 v3 certificates, and other security standards. -
So, now that we've covered that ALL of the alerts are incorrect and that this is clearly very confusing to anyone who isn't a confident Linux admin... why are we getting these errors? They cannot help someone who isn't an expert, and they aren't useful to us. They would be very harmful to normal users trying to just run the system.
-
So just to recap:
- Internet Access Not Working: False. Internet access is just fine.
- cURL / NSS Out of Date: False. Current and patched. Latest from Red Hat.
- PHP Unsupported: False / Tricky. Unsupported by someone who is not the support vendor, so very misleading to anyone that isn't an expert and worthless to anyone who is.
- CentOS 7 Out of date: False Turns out that the concept of the target platform is misunderstood and is actually fully up to date.
Does this make it clear why we see these are problematic?
-
@scottalanmiller said:
@jospoortvliet said:
Look, these are warnings. If you're confident there is no problem, you can ignore them.
This is not a professional response to being informed clearly that there is a bug.
You just told me to ignore a bug. Are we 100% clear that that's what's going on? Is that how ownCloud feels about security issues? Sweet them under the rug? Be wrong and hope that users ignore them?
YOU say they are bugs. I don't. I believe they are real issues a sysadmin should fix. You claim our security guy is incompetent and you trust Red Hat. Fine. Just two links then about PHP:
https://access.redhat.com/solutions/641423
https://bugzilla.redhat.com/show_bug.cgi?id=662707Here's the cURL bug, yes, related to a NSS issue: https://bugzilla.redhat.com/show_bug.cgi?id=1241172
As I said - before I take your input as 'bugreports' I need some proof that these warnings are wrong. For now, I have some reason to think it is GOOD to warn of projects no longer supported by upstream: clearly, distributions don't do a good job keeping up with issues in them and clearly, our warnings (no matter how annoying) are helpful.
Ok, let me give you one more then: https://statuscode.ch/2016/02/distribution-packages-considered-insecure so you can read a bit from the guy we're talking about. There's a reason Lukas is pretty well known in the security world - he knows his stuff. And works for us. These warnings are there because these ARE issues. Perhaps not today because RH just fixed one - but again next week as they are 'maintaining' something which isn't easy to maintain and they don't do such a great job. Wait, wasn't that what you said yourself about LTS earlier? Ah!
Oh and really, if you're right about our security guy, you can make loads of money: https://hackerone.com/owncloud
If you don't mind, I'll retreat from this conversation. If the three links above is not enough proof that these warnings are useful - nothing will be. I honestly think you're barking up the wrong tree - we are careful to warn when there's a serious potential for trouble. Maybe that's zealous - overzealous even. But better safe than sorry.
-
@jospoortvliet said:
If you don't mind, I'll retreat from this conversation. If the three links above is not enough proof that these warnings are useful - nothing will be.
Then I hope you don't mind if I quit recommending ownCloud as a viable solution to my clients.
-
@jospoortvliet said:
YOU say they are bugs. I don't. I believe they are real issues a sysadmin should fix.
Okay, whatever. Clearly I'm taking your platform way too seriously.
-
@JaredBusch said:
@jospoortvliet said:
If you don't mind, I'll retreat from this conversation. If the three links above is not enough proof that these warnings are useful - nothing will be.
Then I hope you don't mind if I quit recommending ownCloud as a viable solution to my clients.
I certainly no longer see them as a business class solution. What a joke.
-
@scottalanmiller said:
@jospoortvliet said:
YOU say they are bugs. I don't. I believe they are real issues a sysadmin should fix.
Okay, whatever. Clearly I'm taking your platform way too seriously.
Seriously? You didn't read the links? Wow. Good night...
-
@jospoortvliet said:
You claim our security guy is incompetent and you trust Red Hat. Fine.
Correct.
-
@jospoortvliet said:
@scottalanmiller said:
@jospoortvliet said:
YOU say they are bugs. I don't. I believe they are real issues a sysadmin should fix.
Okay, whatever. Clearly I'm taking your platform way too seriously.
Seriously? You didn't read the links? Wow. Good night...
I did. That's CentOS 6 from 2013. It's important why?
-
@jospoortvliet said:
@scottalanmiller said:
@jospoortvliet said:
YOU say they are bugs. I don't. I believe they are real issues a sysadmin should fix.
Okay, whatever. Clearly I'm taking your platform way too seriously.
Seriously? You didn't read the links? Wow. Good night...
Maybe because I cannot? Also this is talking about RHEL 6.4
-
-
the other is from 2010. Again, why did you link it? Are these just misdirection hoping that we wouldn't follow the links?
-
@jospoortvliet said:
Here's the cURL bug, yes, related to a NSS issue: https://bugzilla.redhat.com/show_bug.cgi?id=1241172
More misdirection. This isn't a security problem. Yes it has a bug, so? So does ownCloud and they wont even admit it. Red Hat takes this so seriously they are actually working on it. Big difference. They don't pretend that that's okay that there are bugs.
Why is this is a reason to stop using Red Hat's repos and go to rolling out own? That's insane. You can't actually expect us to take this seriously?
-
@scottalanmiller said:
@jospoortvliet said:
@scottalanmiller said:
@jospoortvliet said:
YOU say they are bugs. I don't. I believe they are real issues a sysadmin should fix.
Okay, whatever. Clearly I'm taking your platform way too seriously.
Seriously? You didn't read the links? Wow. Good night...
I did. That's CentOS 6 from 2013. It's important why?
Because it shows exactly what I said - these warnings are useful. They were in those cases and by your own account (not trusting LTS releases), they are now. Also note when they were opened and when they were fixed.
What more do you want? That we, real-time, update these warnings based on existing vulnerabilities that aren't disclosed or fixed? That would be awesome, don't get me wrong - but rather ambitious.
-
@jospoortvliet said:
As I said - before I take your input as 'bugreports' I need some proof that these warnings are wrong. For now, I have some reason to think it is GOOD to warn of projects no longer supported by upstream: clearly, distributions don't do a good job keeping up with issues in them and clearly, our warnings (no matter how annoying) are helpful.
WTF. You've got your proof. Prove to me they are right! We've shown why they are wrong. You've explained how ownCloud didn't understand the platform so we know why you got them wrong. Now you expect us to do your homework for you? We've been doing that all day.
I realize that ownCloud is open source, but you have paid people whose jobs it is to make this system work, right? But you expect us to do this for free?
-
@scottalanmiller said:
@jospoortvliet said:
Here's the cURL bug, yes, related to a NSS issue: https://bugzilla.redhat.com/show_bug.cgi?id=1241172
More misdirection. This isn't a security problem. Yes it has a bug, so? So does ownCloud and they wont even admit it. Red Hat takes this so seriously they are actually working on it. Big difference. They don't pretend that that's okay that there are bugs.
Why is this is a reason to stop using Red Hat's repos and go to rolling out own? That's insane. You can't actually expect us to take this seriously?
Apparently, his security guy does. That is what the link he posted is all about. not trusting the repos.
https://statuscode.ch/2016/02/distribution-packages-considered-insecure/ -
@jospoortvliet said:
Because it shows exactly what I said - these warnings are useful.
No, it does nothing of the sort. It shows that someone, a while ago, thought that one warning was useful. Maybe it was. We didn't say that your security team could never get one right, we just said that they got all of these wrong and that you can't trust them (or by extension, ownCloud.)
-
@JaredBusch said:
@scottalanmiller said:
@jospoortvliet said:
Here's the cURL bug, yes, related to a NSS issue: https://bugzilla.redhat.com/show_bug.cgi?id=1241172
More misdirection. This isn't a security problem. Yes it has a bug, so? So does ownCloud and they wont even admit it. Red Hat takes this so seriously they are actually working on it. Big difference. They don't pretend that that's okay that there are bugs.
Why is this is a reason to stop using Red Hat's repos and go to rolling out own? That's insane. You can't actually expect us to take this seriously?
Apparently, his security guy does. That is what the link he posted is all about. not trusting the repos.
https://statuscode.ch/2016/02/distribution-packages-considered-insecure/Um, okay. Certainly no point continuing this conversation then. I'll just start building my own operating system that ownCloud doesn't support and running that.
You are just making it so that ownCloud never has to be responsible for anything. We've asked for any way to run a system that ownCloud wouldn't blame us for the decisions and you've made it crystal clear why no such recommendation will ever be forthcoming - this is all setting up excuses so that OC never has to accept responsibility.
-
@jospoortvliet said:
What more do you want? That we, real-time, update these warnings based on existing vulnerabilities that aren't disclosed or fixed? That would be awesome, don't get me wrong - but rather ambitious.
How can you POSSIBLE ask this again. I want accurate, truthful errors and bugs fixed. No false errors.
You are constantly arguing that false errors are better than no errors. I'm telling you, that's wrong. But, it's your product. Don't listen to me.
