Gentoo Archives: gentoo-user

From: Miroslav Rovis <miro.rovis@××××××××××××××.hr>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] SHA-1 has just been broken
Date: Tue, 28 Feb 2017 01:12:37
Message-Id: 20170228011051.GA20415@g0n.xdwgrp
In Reply to: Re: [gentoo-user] SHA-1 has just been broken by Andrew Savchenko
1 Apologies for my not being able to reply sooner!
2
3 On 170227-18:18+0300, Andrew Savchenko wrote:
4 > On Sun, 26 Feb 2017 12:00:50 +0100 Miroslav Rovis wrote:
5 >
6 > > But, when we talk crypto being broken,
7 >
8 > Git is not in the immediate threat due to SHA1 collision being
9 > practical. See Linux blog about this:
10 >
11 > https://plus.google.com/+LinusTorvalds/posts/7tp2gYWQugL
12 Will read it. (it's 02:00 past midnight CET)
13
14 > Note that git devs are working on moving to a more secure hash
15 > function.
16 Good to hear!
17
18 > Also note that git can handle several files in the repo with the
19 > same hash function. While this doesn't protect from the possible
20 > repo forgery, it protects from accidental file collision where
21 > subversion fails badly:
22 > https://www.bleepingcomputer.com/news/security/sha1-collision-attack-makes-its-first-victim-subversion-repositories/
23 Pretty sad!
24 > I do not want to offence subversion devs, but they haven't even
25 > considered the possibility that hash function may collide. Huge
26 > blunder on their side.
27 >
28 > > I can help thinking of other
29 > > threats to Gentoo and other FOSS GNU Linux that I fear are perfectly
30 > > feasible (for the resourceful subjects)
31 > >
32 > > Gentoo distro is increasingly served the insecure way, IMO, that is: via
33 > > git, without the repositories being, for end users, PGP-verifiable.
34 >
35 > It is verifiable for end users, but not in an easy way. You can
36 > either use web rsync or verify git commits yourself using gpupg and
37 > gkeys.
38 I'll try and do that. I have been trying to figure it out, a few times
39 already, but I would always get lost in the volume of new stuff to
40 digest... Will need more time to do it.
41
42 However I am already using signed portage snapshots via emerge-webrsync,
43 and I use local mirror. I am pretty safe, but on obsolete technology.
44
45 > > And via a new private big business, the Github. Giving over all users to
46 > > big Github brother.
47 >
48 > ???
49 > Github is entirely optional and is only for those who want to use it
50 > (we have both users and devs willing so), but in no way anyone
51 > demands its usage.
52 Yeah! Still, it would be great if git was used in distributed way, and
53 not from a central private business...
54
55 > If you want to have sync-friendly git repo, Gentoo infra provides
56 > one for you:
57 > https://gitweb.gentoo.org/repo/sync/gentoo.git/
58 Harder to use than Github. Github is foolproof, extremely easy for
59 newbies, compared to any other git server. The reason for their
60 success...
61
62 > > And, in the trasition all the history got lost. Git started remembering
63 > > only from 2015.
64 >
65 > No, it isn't. Full historical git repo is available:
66 > https://gitweb.gentoo.org/repo/gentoo/historical.git/
67 Great to know! Sorry for wrong claims that I made.
68
69 > One may use git graft to join historical and actual repo together.
70 Which is advanced usage for me at this stage.
71
72 > > I have asked a question about getting git-served repository verifiable
73 > > for end users, but I didn't get any replies:
74 >
75 > Do not forget that all devs are volunteers.
76 I know that. Always keep that in mind.
77
78 > User-transparent
79 > GnuPG tree verification is indeed important. You can help!
80 If I get that savvy in git/portage/other I will... That time is still
81 distant yet, I'm afraid.
82
83 > Join gkeys project, get in touch with infra, discuss what needs to be
84 > done.
85 I'll look gkeys up...
86 > Don't just rattle about how insecure data is provided,
87 You're right.
88 > help to make it secure! (And as I shown above actual state is not that
89 > bad and some options are already available.)
90 I'm busy figuring how to deploy virtualization on my sans-dbus system,
91 and have spent months on things like that... and only lately finally
92 getting there.
93
94 Also, practical verifiability in Gentoo is something I have been keen on
95 for pretty long now.
96
97 But you having showed to me (I haven't digested it yet, too late in the
98 night right now) that verifiability is possibly does make it the next
99 big wish of mine to apply for my Gentoo
100 (
101 and my dream is to help test it, so everybody can use git for verifiable
102 installations!
103 ).
104
105 >
106 > Best regards,
107 > Andrew Savchenko
108
109 Your email means a lot to me! Thank you!
110
111 Good night! (I see other emails, but have to go to sleep now first)
112 --
113 Miroslav Rovis
114 Zagreb, Croatia
115 https://www.CroatiaFidelis.hr

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
Re: [gentoo-user] SHA-1 has just been broken Rich Freeman <rich0@g.o>