News for hackers. Stuff that matters.
Re:Critical security updates for Git, Subversion and Mercurial by innocenat on Friday August 11, 2017 @07:27AM (#14988514)
Just a note for everyone on Ubuntu, the fixed version for Ubuntu 16.04 is git v2.7.4-0ubuntu1.2 [0].

[0]: https://people.canonical.com/~ubuntu-security/cve/2017/CVE-2...

Re:Critical security updates for Git, Subversion and Mercurial by lotsoflumens on Friday August 11, 2017 @08:34AM (#14988973)
Does anybody understand Ubuntu releases?

The update this morning for Ubuntu 17.04 installs git 2.11.0

.. NOT the patched 2.11.3 NOR the latest 2.14.1

Why isn't Ubuntu fully up to date?

Re:Critical security updates for Git, Subversion and Mercurial by 0x0 on Friday August 11, 2017 @09:20AM (#14989336)
Almost all linux distros that use the concept of a "release" will stay on the version numbers they originally released for. Security fixes are backported but no other functionality is imported, thereby keeping the feature set fixed to the version numbers in the original release.

If you are maintaining or developing any kind of server and services where you need an uptime guarantee above 0%, you will appreciate this. Otherwise you will need staff on standby 24/7 being ready to develop fixes for breaking backwards compatibility changes. Imagine if you had to deal with funky errors like these every minute of the day - https://gitlab.com/gitlab-org/gitlab-ce/issues/36028

For Ubuntu, you should follow their "usn" security notices and you would stay informed: https://usn.ubuntu.com/usn/

For Debian, likewise there is a "debian-security-announce" mailing list https://lists.debian.org/debian-security-announce/

Also for Debian, you can check up on the status for known vulnerabilities on their security tracker. For example, for this particular git exploit, you could look up https://security-tracker.debian.org/tracker/CVE-2017-8386

Re:Critical security updates for Git, Subversion and Mercurial by CiPHPerCoder on Friday August 11, 2017 @08:44AM (#14989055)
They backport patches and lie about the version number, to maintain the illusion of stability. It really pisses off the PHP community.

https://github.com/ircmaxell/password_compat/issues/90

Re:Critical security updates for Git, Subversion and Mercurial by cperciva on Friday August 11, 2017 @09:07AM (#14989238)
I can't speak for Ubuntu, but when I was FreeBSD Security Officer we would regularly backport patches because importing an entire new release would regularly break existing functionality or even add new security vulnerabilities. It annoyed the heck out of vulnerability scanning tools, but I decided that giving users a system which didn't randomly break when they applied security patches was far more important.
Re:Critical security updates for Git, Subversion and Mercurial by CiPHPerCoder on Friday August 11, 2017 @09:30AM (#14989421)
That was years ago, IIRC.

PHP has gotten better about "no BC breaks in patch versions" over the years, but the Debian/Ubuntu teams still insist on making people effectively run e.g. 7.1.8 while the version indicator says 7.1.1.

It makes feature detection a nightmare.

Re:Critical security updates for Git, Subversion and Mercurial by rlpb on Friday August 11, 2017 @11:11AM (#14990438)
Ubuntu developer here. Huh? No, we don't. Can you provide a more specific and current example to make sure I don't misunderstand you?

For example, the current package for Ubuntu 16.04 LTS is 7.0.22-0ubuntu0.16.04.1. How does this mismatch 7.0.22 from the PHP upstream project?

Re:Critical security updates for Git, Subversion and Mercurial by CiPHPerCoder on Friday August 11, 2017 @12:33PM (#14991536)
Okay, maybe Ubuntu stopped being stupid and only Debian is still guilty of this?

This used to be a huge problem. I've since convinced [most PHP devs I talk to] to stop using distro-provided packages, in favor of deb.sury.org.

Re:Critical security updates for Git, Subversion and Mercurial by rlpb on Friday August 11, 2017 @02:22PM (#14992748)
Ubuntu and Debian's PHP packages are largely the same.

> I've since convinced [most PHP devs I talk to] to stop using distro-provided packages, in favor of deb.sury.org.

You do realise that Ondřej Surý (of sury.org) is the primary Debian PHP maintainer? The point of his repositories (AIUI) is to allow users to mix and match PHP versions. The downside is that he's one person with (AFAIK) a bus factor of 1 when it comes to security updates. That's irresponsible to use in production.

In contrast, Debian and Ubuntu's PHP packages, essentially provided by the same person, has in addition teams (both in Debian and Ubuntu) who can pitch in when required.

Re:Critical security updates for Git, Subversion and Mercurial by eikenberry on Friday August 11, 2017 @02:29PM (#14992816)
AFAIK neither Debian nor Ubuntu lie about version numbers. They have stable versions that they backport security patches to, but they don't change the version number. That issue you link to doesn't contradict this.
Re:Critical security updates for Git, Subversion and Mercurial by piquadrat on Friday August 11, 2017 @08:48AM (#14989094)
The version is actually 2.11.0-2ubuntu0.2, with the fix backported, as can be seen in the changelog:

http://changelogs.ubuntu.com/changelogs/pool/main/g/git/git_...

It's somewhat confusing if you run `git --version` and it reports back 2.11.0, despite being fully patched against this vulnerability.

Re:Critical security updates for Git, Subversion and Mercurial by lotsoflumens on Friday August 11, 2017 @08:53AM (#14989135)
Thanks for the info!

I've added the git-core PPA now which installs 2.14.1 .

I just don't understand this screwing with version numbers and not being on the latest code.

Re:Critical security updates for Git, Subversion and Mercurial by richardwhiuk on Friday August 11, 2017 @09:06AM (#14989231)
The point of having stables releases is that you have a consistent set of versions of packages including git, otherwise how is it stable?
Re:Critical security updates for Git, Subversion and Mercurial by lotsoflumens on Friday August 11, 2017 @09:25AM (#14989385)
Yes, it makes a lot of sense to ignore the real world and pretend that software will always be stable.
Re:Critical security updates for Git, Subversion and Mercurial by 0x0 on Friday August 11, 2017 @12:14PM (#14991316)
Why don't you just run Debian Sid then? You'll get new packages every day and get all the fun of chasing changing features all the time :D
Re:Critical security updates for Git, Subversion and Mercurial by radarsat1 on Friday August 11, 2017 @08:38AM (#14989000)
Came here to ask the same thing, running 17.04. I just did an update && dist-upgrade, still have git-2.11.0.

Edit: The package is actually 2.11.0-2 which contains the security patch.

Re:Critical security updates for Git, Subversion and Mercurial by pawadu on Friday August 11, 2017 @09:04AM (#14989216)
This question is brought up every time this happens. Ubuntu uses stable (old) versions and does not upgrade to latest (unstable) releases very often. However, they do back port and apply security patches to these old versions.

Point in case: 16.04 TLS is still on 2.7.4 but it is fully patched and secure.

Re:Critical security updates for Git, Subversion and Mercurial by radarsat1 on Friday August 11, 2017 @10:08AM (#14989778)
Yes, you're right. I was expecting to see the update by checking "git --version" and seeing 2.11.0-1 or something like that, but it's not visible that way.

Indeed if I check with "apt-get show git", the package is on version 2.11.0-2, and then I have to browse to the package web page at https://packages.ubuntu.com/zesty/git and click on the changelog and finally I get to the update information, which clearly contains the text, "SECURITY UPDATE: Arbitrary code execution on clients through malicious ssh URLs."

So it was patched as expected, it just wasn't easy for me to see that without going through a few extra steps.

Re:Critical security updates for Git, Subversion and Mercurial by masterleep on Friday August 11, 2017 @01:14PM (#14992098)
Try "apt changelog git" on the box.
Re:Critical security updates for Git, Subversion and Mercurial by eikenberry on Friday August 11, 2017 @02:32PM (#14992850)
Or you can read the changelog on the filesystem at...

/usr/share/doc/git/changelog.Debian.gz

Re:Critical security updates for Git, Subversion and Mercurial by lotsoflumens on Friday August 11, 2017 @09:16AM (#14989303)
This practice is seriously bad.

It means that one group of developers is busy improving and fixing packages, and another different group is cherry-picking commits in order to maintain the illusion of stability (as mentioned above).

That second group has to duplicate all the testing work done by the first group, and additionally ensure that there are no new problems introduced.

It's very vulnerable to human error and adds a lot of unnecessary work.

Re:Critical security updates for Git, Subversion and Mercurial by 0x0 on Friday August 11, 2017 @09:24AM (#14989373)
It's better to have a competent "second group" do the backport job rather than every single user of a distro having their rug pulled out under them every time they patch. New versions of software can quickly break your environment. For example, https://gitlab.com/gitlab-org/gitlab-ce/issues/36028 . If you have to re-test every script and web service to ensure compatibility with the daily churn of vulnerability fixes you would get nothing done and you could almost never be sure your service is stable.
Re:Critical security updates for Git, Subversion and Mercurial by lotsoflumens on Friday August 11, 2017 @09:40AM (#14989517)
I agree, this is a problem, but it's not being solved by this practice.

The example you gave is specifically about a client application of git that wasn't updated to work with the current version of git - probably because of some twisted logic that they didn't have to worry about it until some future date.

Re:Critical security updates for Git, Subversion and Mercurial by 0x0 on Friday August 11, 2017 @12:04PM (#14991144)
It's an example of how things break if you upgrade to new versions of software. If you avoid going to new versions of software, and instead just backport the essential security fixes, there will be much fewer surprises like this.

Imagine you had a daily backup script that uses git to commit and push to a remote server perhaps managed by someone else. You then upgrade to the latest and greatest version of git to try to patch this vulnerability, and surprise, your backup script fails! Hope you weren't planning on spending the rest of the day getting the guys running the git server to implement a workaround, who might have already left for the weekend, leaving you with no backups or having to manually try to fix your git to work with that server again.

Re:Critical security updates for Git, Subversion and Mercurial by lotsoflumens on Friday August 11, 2017 @05:56PM (#14994682)
Well then, I guess with that line of reasoning we should just turn off the computers and go live in the woods. There's obviously too much risk in doing anything.
Re:Critical security updates for Git, Subversion and Mercurial by 0x0 on Friday August 11, 2017 @06:12PM (#14994780)
That's up to you. I find the current system of stable releases to work just right.
Re:Critical security updates for Git, Subversion and Mercurial by boot13 on Friday August 11, 2017 @09:36AM (#14989486)
Yeah, well, that's just, like, your opinion, man.

I see it differently. Where do new bugs and vulnerabilities come from? When the main developers add features or make changes to existing features that go beyond fixing bugs.

From the point of view of many server administrators, using the latest versions of everything is inherently risky. What they want to use is a stable, solid version that has all the latest security fixes.

It's unlikely that these opposing viewpoints will ever be reconciled.

Re:Critical security updates for Git, Subversion and Mercurial by lotsoflumens on Friday August 11, 2017 @10:15AM (#14989844)
It's important for package developers to be aware of other software that depends on their interfaces or functionality.

Some cases will slip through sometimes, but over a couple of releases these should be gone.

>> Where do new bugs and vulnerabilities come from? When the main developers add features or make changes to existing features that go beyond fixing bugs.

Do you have stats for that?

Semantic versioning was supposed to be the fix for that, but as Rich Hickey has pointed out, that is also broken.

Everyone is their own server admin these days. We all want "a stable, solid version that has all the latest security fixes" but it's difficult accept that that might be impossible.

Re:Critical security updates for Git, Subversion and Mercurial by boot13 on Friday August 11, 2017 @12:25PM (#14991432)
No stats needed. Just go through the bug list for any software. How many of the bugs were introduced by the people who maintain stable packages?
Re:Critical security updates for Git, Subversion and Mercurial by mcny on Friday August 11, 2017 @09:36AM (#14989475)
I agree with this sentiment a lot of the time but consider this:

https://bugs.kde.org/show_bug.cgi?id=382911

it is a duplicate of

https://bugs.kde.org/show_bug.cgi?id=378854

which is fixed by https://cgit.kde.org/konversation.git/commit/?id=783dc0f595e...

but upstream for some reason does not think this is important enough to tag and bag into a release.

as much hate as Fedora gets, rdieter has taken the time to backport the changes that we need in Fedora.

https://bodhi.fedoraproject.org/updates/FEDORA-2017-9c3e2138...

Ideally, we'd rather see upstream release this fix but we've all read https://news.ycombinator.com/item?id=14051106 and I don't want to be too impatient with software that upstream has graciously provided for free (in both senses of the word!)

I guess my point is backporting might make sense if there are small changes we can make to enhance release. However, I agree that there is too much duplication of effort going on.

Re:Critical security updates for Git, Subversion and Mercurial by lotsoflumens on Friday August 11, 2017 @09:58AM (#14989701)
I've seen that bug!

And, I'm not too surprised, KDE has a broken development and maintenance process. I'm sure they think they're doing a great job - but that's because they don't even see or receive most bug reports.

Re:Critical security updates for Git, Subversion and Mercurial by mcny on Friday August 11, 2017 @10:57AM (#14990272)
> And, I'm not too surprised, KDE has a broken development and maintenance process. I'm sure they think they're doing a great job - but that's because they don't even see or receive most bug reports.

KDE actually fixed the bug but it hasn't gone to a tagged release after two months. Maybe they think this small change doesn't warrant a release? I asked if KDE neon can pick it up but they (understandably) seem to see this as feature creep. KDE applications means something different for the neon folks (only the things they ship with neon from what I understand).

I agree. I have no doubt we are all trying to do our best. =)

Re:Critical security updates for Git, Subversion and Mercurial by rlpb on Friday August 11, 2017 @11:13AM (#14990466)
You're welcome to use Debian testing, or the development release of Ubuntu. Both update packages as they are released from upstream developers.
Re:Critical security updates for Git, Subversion and Mercurial by lotsoflumens on Friday August 11, 2017 @12:00PM (#14991068)
Thanks, but that means I'm doing the testing. I wish I could do that - maybe someday.
Re:Critical security updates for Git, Subversion and Mercurial by rlpb on Friday August 11, 2017 @02:15PM (#14992692)
I don't follow. What do you want exactly? The newest stuff pushed straight to users, or not?