From: Igor <lanthruster@gmail.com>
To: "\"Paweł Hajdan, Jr.\"" <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] minimalistic emerge
Date: Sat, 9 Aug 2014 19:25:56 +0400 [thread overview]
Message-ID: <53e63d85.68aa700a.1e9a.16eb@mx.google.com> (raw)
In-Reply-To: <53E5EB25.5060500@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 3359 bytes --]
Hello Paweł,
Saturday, August 9, 2014, 1:34:29 PM, you wrote:
> Possibly relevant article would be
> <http://www.site-reliability-engineering.info/2014/04/what-is-site-reliability-engineering.html>
>>> The number of bugs is the same. It's more difficult to hack into 1996 system
>>> than in 2012.
> Do you have any evidence to back that claim? There are tons of known
> vulnerabilities in '96-era software, and automated exploits for them.
> By the way, I can see a point in your thread. Our updates and package
> manager could be improved. They have improved greatly in the last few
> years. I think I can safely say we welcome further contributions of
> patches, packaging and testing effort, especially helping automate many
> of these tasks.
In my experience - hacking into 96 system with a 0 door is much harder
than in 2014. In most cases unless you're an expert on 96 software which
is difficult nowadays due to human memory. To really break in you need to
reproduce server environment as close as possible or/and have a clear
understanding how this particular software works. Try to assemble a
96 system on modern hardware or assemble it as they were back in 96,
not all sources are online any longer, that is a hard job. 2014 systems
are much easier to assemble and get a peek to the sources is a trifle.
As Linux software is open-source it's often easier to break in Linux
than in Windows systems. The open source is only theoretically safer.
Many belive that because the code is open - it's reviewed and checked
and the number of critical bugs is low. But the reality is that there
is usually no time to review code. Many modern software is very complex
with millions lines and it's not realistic to check or
understand how it works before you use it in your project. Tell me
how many libraries that you use right now are reviewed by you personally?
Not many. And that is a door that is NEVER going to be closed. There are
bugs, rest assured, if you pull any soft right now and spend time
you will find them. If you have an expertise on cross platforms - you
will find even more as developers used to focus on one platform the birth
platform.
If you compare the number of bugs you find in 1996 software and in 2014
- the numbers would approximately be the same.
Usually 1996 system is patched or protected against known issues and you
have to deal with "unknown" which in case of 1996 is much harder.
Another weak link with open source is software developers. Many of them
spend a lot of time on their software not always getting a fair monetary
reward. So if you a very shrewd and have resources - you go to developers
and offer them money to introduce a subtle bug into the main tree. After
the software is adopted then you have open doors in EVERY "updated"
linux on the planet.
Personally I belive Heart Bleed bug is one of such. You can never proof
if the bug is artificial or not - how?
The same true for Microsoft soft. You can basically go to a ntkernel
developer offer him 500 000$ if have them and he would add a bug and
explain you how to use it and you're everywhere :-) but this is usually
the government's methods. They used to keep them secret.
--
Best regards,
Igor mailto:lanthruster@gmail.com
[-- Attachment #2: Type: text/html, Size: 4649 bytes --]
next prev parent reply other threads:[~2014-08-09 15:26 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 13:12 [gentoo-dev] minimalistic emerge Igor
2014-08-08 13:22 ` Ciaran McCreesh
2014-08-08 15:23 ` Igor
2014-08-08 15:36 ` hasufell
2014-08-08 15:53 ` Igor
2014-08-08 15:45 ` Ian Stakenvicius
2014-08-08 16:27 ` Igor
2014-08-08 16:40 ` Homer Parker
2014-08-08 17:26 ` Igor
2014-08-08 17:32 ` Homer Parker
2014-08-08 17:30 ` Ian Stakenvicius
2014-08-09 9:34 ` "Paweł Hajdan, Jr."
2014-08-09 15:25 ` Igor [this message]
2014-08-13 7:54 ` [OT] " Tom Wijsman
2014-08-08 16:31 ` Rich Freeman
2014-08-08 13:23 ` hasufell
2014-08-08 13:32 ` Jeroen Roovers
2014-08-08 15:14 ` Alan McKinnon
2014-08-13 8:13 ` Tom Wijsman
2014-08-08 15:51 ` Kent Fredric
2014-08-08 16:58 ` Igor
2014-08-08 17:29 ` Kent Fredric
2014-08-08 20:52 ` Igor
2014-08-08 21:33 ` Kent Fredric
2014-08-08 21:39 ` Ian Stakenvicius
2014-08-08 21:43 ` Kent Fredric
2014-08-09 14:56 ` Igor
2014-08-09 15:12 ` Chris Reffett
2014-08-09 17:10 ` Ciaran McCreesh
2014-08-13 8:20 ` Tom Wijsman
2014-08-13 13:17 ` hasufell
2014-08-09 19:30 ` Jeroen Roovers
2014-08-09 15:44 ` Chris Reffett
2014-08-09 15:46 ` Chris Reffett
2014-08-09 15:58 ` Chris Reffett
2014-08-08 19:34 ` Peter Stuge
2014-08-08 19:47 ` Ian Stakenvicius
2014-08-08 19:56 ` Kent Fredric
2014-08-08 20:16 ` Ian Stakenvicius
2014-08-09 2:14 ` Rich Freeman
2014-08-09 8:30 ` Peter Stuge
2014-08-08 21:04 ` Johannes Huber
2014-08-13 8:25 ` Tom Wijsman
2014-08-09 3:07 ` [gentoo-dev] " Duncan
2014-08-09 8:34 ` Peter Stuge
2014-08-09 11:03 ` Duncan
2014-08-09 11:06 ` hasufell
2014-08-09 12:16 ` Ambroz Bizjak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53e63d85.68aa700a.1e9a.16eb@mx.google.com \
--to=lanthruster@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox