Linux Mint downloads (briefly) compromised
1–10 of 236 posts
Re: Linux Mint downloads (briefly) compromised
#2Re: Linux Mint downloads (briefly) compromised
#3Re: Linux Mint downloads (briefly) compromised
#4Whos using Mint these days anyway ?
Re: Linux Mint downloads (briefly) compromised
#5Could [Linux] be added before Mint? I thought it was about Mint.com
Linux Mint downloads (briefly) compromised
Re: Linux Mint downloads (briefly) compromised
#6There was recently an article on HN about the "Web of Hashes" and this article got me thinking about it. Why not give each application an UUID and let that be it's name space? Give the user an option to still use- they're example- xedit while having another xedit installed along side?
I can see how this could also get messy. Just spit balling here.
Re: Linux Mint downloads (briefly) compromised
#7Re: Linux Mint downloads (briefly) compromised
#8There's something interesting to be said here. "They make {{ package }} unusable by hijacking it's name space", well who gave them that name space? I understand the whole first come first serve and all but if we played that way things could get messy real fast. There was recently an article on HN about the "Web of Hashes" and this article got me thinking about it. Why not give each application an UUID and let that be…
Re: Linux Mint downloads (briefly) compromised
#9This is interesting because Debian itself encourages derivative projects to use their binary packages[1]:
> For those derivatives that re-use Debian binary packages, add some source packages and modify some source packages, where possible we encourage them to use standard Debian mirrors and add a second repository containing only the source and binary packages that have been added or modified.
Or maybe they don't encourage that behaviour but still give guidelines in case you want your derivative to work that way? I'm not 100% sure.
Re: Linux Mint downloads (briefly) compromised
#10> Secondly, they are mixing their own binary packages with binary packages from Debian and Ubuntu without rebuilding the latter. This creates something that we in Debian call a "FrankenDebian" which results in system updates becoming unpredictable This is interesting because Debian itself encourages derivative projects to use their binary packages[1]: > For those derivatives that re-use Debian binary packages, add so…