Hacker Newsnew | past | comments | ask | show | jobs | submit | more lambda's commentslogin

Squeeze isn't vulnerable to heartbleed; the OpenSSL version is too old; heartbeat was introduced in 1.0.1, while Squeeze ships 0.9.8o.


https://packages.debian.org/squeeze/openssl

Oops, the strange decisions at Tails saves the day.

I still don't understand their reluctance to patch grsecurity and/or pax. It's been on their roadmap for ages. Liberte Linux included it since their first release too bad the guy abandoned the project last year. Probably the same thing happened to Maxim as the creators of Anonym.OS they were hired to make secure builds for companies and stopped maintaining them.

Of course anybody here can roll their own live distro of BSD/Nix and just review both projects design documents to see the kinds of security decisions made to implement them as well but the vast public is stuck with Tails which keeps ballooning in size. They need a light version without tons of codecs and video editing software, collaborative editors or full office suites.


Maintaining a Linux distro is a lot of work, even if it's a variant of another distro. The more you diverge from the upstream, the more work it is.

Note that your examples of distros that adopted PaX/grsecurity are also your examples of distros that have been abandoned.

You need to pick your battles. Being based on Debian oldstable, which is still receiving security support while being a stable base to work on, is a fine decision. Not introducing a big change like grsecurity which will inevitably lead to having to tweak dozens of packages to continue to work properly (and thus have to maintain your own forks of said packages, without being able to easily pull security updates from upstream), is also a reasonable decision.

I invite you to create your own distro if you disagree. Please show me your up to date, privacy and security oriented distro; I'd love to see a comparison of how your style of maintainership will differ from that of Tails.


As an almost daily Tails user that closely follows its development and knows one of its developers, my impression is that the Tails team is seriously understaffed, which I believe explains all your concerns. There are only two persons that more or less regularly write code and prepare releases.

> hasn't updated the release since March so a dozen known Debian security advisories are not patched

It could be that none of the current vulnerabilities seriously affect Tails' stated use cases. Do they? We know that Heartbleed does not affect Tails. Only CVE-2014-2653 looks remotely relevant to me but I'm no expert. An out-of-schedule Tails release would steal a lot of development time which instead could be used to improve Tails permanently so they are not done unnecessarily.

> it took them years to even add a macchanger on boot for wireless

Judging by their design document it seems like a pretty big undertaking to do properly without causing a huge user support mess and giving a false sense of security. I for one understand if they chose to deprioritize it for some years in favor of other lower hanging fruit of similar importance. Personally I used to run macchanger manually when needed as the tool itself has been included in Tails for as long as I have been using it (four years).

> Oops, the strange decisions at Tails saves the day.

Since Debian Squeeze still receives security updates this does not seem very strange at all. I believe the "decision" is another consequence of their lack of man power. While slightly annoying at times I can live with out-dated packages that lack features I would like to have as long as they receive security upgrades.

> I still don't understand their reluctance to patch grsecurity and/or pax.

The Tails team has explicitly stated that they do not have the human resources available to afford maintaining all that themselves. Hopefully the Debian kernel team will get their shit together and provide a hardened kernel flavor some time soon.

> [...] the vast public is stuck with Tails which keeps ballooning in size. They need a light version without tons of codecs and video editing software, collaborative editors or full office suites.

One danger with a lightweight Tails distribution is that users are forced to mix data and activities with their normal, insecure OS, which potentially can hurt their anonymity and leave a data trail, thus countering Tails' two main points. Another danger is that the users get tired of Tails' inability to do basic, expected activities and stop using it completely, switching back to their normal, insecure OS for activities that they really should use Tails for.

That said, I do agree that fringe use cases like video editing should be removed since Tails' size is becoming a real concern. The "additional software" feature available when running Tails from a USB drive should be promoted more actively for such edge cases. Shipping less packages in Tails should also decrease the Tails team's maintenance burden so this actually looks like something worthwhile issuing a feature request for.


Actually, they do generally discriminate.

Software which is easy to set up initially, but hard to upgrade, tends to be much more likely to be out of date than software which is easier to upgrade.

Things that consist of "a big blob of PHP plus a lot of extensions" tend to fall into this camp. PHP apps are generally very easy to get set up the first time, and popular ones like Wordpress have lots of extensions you can add on; but then once you've been running that for a while, you discover that if you upgrade, these n extensions all break, and rather than bothering to find replacements, you just don't bother upgrading.

How do you fix this? Make upgrading easy, don't rely on extensions, or make sure you have bulletproof, stable APIs so that no one worries "if I upgrade, all these things are going to break."


Since 3.7 WordPress auto-upgrades itself in the background (for minor versions), like Chrome does. So not sure what are you talking about.


But the problem is that there are people who have been coding C++ for 20 years, who never quite got all of these newfangled smart pointer things and just want the "C with classes" parts of C++.

Or you have the cargo cult programmers, who don't know the language very well, so just pick up idioms from random internet postings or from some old part of the codebase that's been working for a while, so it must be a good source of design tips.

Remember, any time you talk about the safety of a language, you have to think about its safety in the hands of a mediocre programmer who's in a hurry to meet a deadline. Because that's where the bulk of the problems slip in; not when people are actively and deliberately coding defensively.


This is a fairly popular thing to do with bitcoin addresses as well; keep generating keys until you get one with a recognizable prefix in the address.


Tor hidden services also do this. (The address of a hidden service is a hash)


Not just for vanity, either - it makes phishing a hidden service harder: if users know the .onion for Agora starts with 'agora', then a phisher has to invest weeks of compute-time just to get a plausible .onion to start his phish with, rather generate than any old .onion in a millisecond.


Neat. I remember Stripe did something similar with their CTF challenge


Yep! There were a bunch of us who wrote GPU "miners" (mostly OpenCL). I was intending to open-source mine at one point but never got around to it.

At the end of the challenge, the network was hashing ten digits (i.e. 000000000 prefix) in just a few seconds. Here's one of the rounds: https://github.com/pushrax/round660/commits/master


In the article, he mentions using Evilgrade to do the backdooring. If you click though the link, you can find the README, which lists a bunch of applications that Evilgrade supports seeding backdoored versions of http://www.infobyte.com.ar/down/isr-evilgrade-Readme.txt

He likely just enabled them all, or at least enabled several which are likely candidates for his target to download.


I think they mean 4π steradians (unit of solid angle covering the surface of a sphere), not 360° (unit of angle, covering the circumference of a circle).


Learn something everyday, I've wanted to express that concept before, and never even wondered if there was a word for it. Of course, If I use it I'll have to define it much like you just did.


On one machine I tried, help('modules') actually worked successfully with no substantial delays or apparent side effects.

On another, it apparently tried to set up an MPI cluster:

  *** The MPI_Init() function was called before MPI_INIT was invoked.
  *** This is disallowed by the MPI standard.
  *** Your MPI job will now abort.
  [hostname:14114] Abort before MPI_INIT completed successfully; not 
  able to guarantee that all other processes were killed!
On a third, I get the following and then it just hangs:

  Python 2.7.6 (default, Mar 22 2014, 15:40:47)
  [GCC 4.8.2] on linux2
  Type "help", "copyright", "credits" or "license" for more information.
  >>> help('modules')
  
  Please wait a moment while I gather a list of all available modules...

  /usr/lib/python2.7/dist-packages/gobject/constants.py:24: Warning: g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed
    import gobject._gobject
  /usr/lib/python2.7/dist-packages/gi/module.py:171: Warning: cannot register existing type 'GtkWidget'
    g_type = info.get_g_type()
  /usr/lib/python2.7/dist-packages/gi/module.py:171: Warning: cannot add class private field to invalid type '<invalid>'
    g_type = info.get_g_type()
  /usr/lib/python2.7/dist-packages/gi/module.py:171: Warning: cannot add private field to invalid (non-instantiatable) type '<invalid>'
    g_type = info.get_g_type()
  /usr/lib/python2.7/dist-packages/gi/module.py:171: Warning: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed
    g_type = info.get_g_type()
  /usr/lib/python2.7/dist-packages/gi/module.py:171: Warning: cannot register existing type 'GtkBuildable'
    g_type = info.get_g_type()
  /usr/lib/python2.7/dist-packages/gi/module.py:171: Warning: g_type_interface_add_prerequisite: assertion 'G_TYPE_IS_INTERFACE (interface_type)' failed
    g_type = info.get_g_type()
  /usr/lib/python2.7/dist-packages/gi/module.py:171: Warning: g_once_init_leave: assertion 'result != 0' failed
    g_type = info.get_g_type()


Hey, the first kernel release with a patch from me in it! It's just a typo fix in a comment, but hey, it's a start.


At least you can put "Linux Kernel Contributor" on your CV now.


Ah, you've seen that comic come by on reddit too, eh?

http://i.imgur.com/6KQCx89.jpg


This is fairly reminiscent of xkcd's What If blog post series: https://what-if.xkcd.com/


This is a series of articles, and is not yet complete. It starts from a high level description of the organization of the project, and is going into more detail as it goes, but it is not yet complete; notice that at the end of the third article there is a "Next: To be published: Git internal algorithms (Tree and Diffcore API)". I presume there will be more after that, though the author doesn't provide an overview of what he expects the full series to consist of.

Also, I don't believe this is intended to be a review looking at coding practices that may cause problems, but rather a review in the sense of a description of a real-world codebase that describes how it works. Think of it in the sense of a review of the literature, a summary of what a body of work is about, not in the sense of a code review that is looking for potential problems that may need to be fixed.

As far as the issues you bring up go, Git is pretty thoroughly cross-platform if you assume a reasonable Unixy/POSIXy platform; while it can be made to work on Windows, it's a bit more cumbersome there; you need to use something that provides at least somewhat of a Unix like environment on Windows, such as MSYS or Cygwin.

As far as resource management and so on go, one of the big problems with the Git code base is that it's designed pretty heavily around a one-shot command model, rather than something which is amenable to being used as a library or in a long-running process. This is reason why the libgit2 project exists, to provide an implementation of Git that can be used as a library and integrated into other applications. Even Linus himself, who wrote the initial Git implementation, uses libgit2 when he wants something that can be used as a library[1].

[1]: https://plus.google.com/+LinusTorvalds/posts/X2XVf9Q7MfV


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: