!ZRgXNaHrdpGqwUnGnj:nixos.org

NixOS Security Triage

691 Members
Coordination and triage of security issues in nixpkgs215 Servers

Load older messages


SenderMessageTime
4 Jun 2021
@r_i_s:matrix.orgris_like, versions of things all over the place, separate source trees, the security team not pushing their patches to sources.debian.org or the package maintainer's source control 😰17:53:25
@andi:kack.itandi-I still don't see our gain adding patches to old libraries instead of bumping them - as long as the dependencies don't break. We do not have to retain ABI stability as we are a) rebuilding all depenndencies b) have a proper build system that covers a) :)17:54:35
@r_i_s:matrix.orgris_well... what is "our" in this case? are "we" just a bunch of people who have self-selected as people who don't care about supporting old software? 17:56:13
@r_i_s:matrix.orgris_there is certainly a need for LTS, otherwise it wouldn't exist17:56:30
@sandro:supersandro.deSandro
In reply to @philipp:xndr.de
It's less about making it easier and more allowing for longer support intervals.
If we find more people which have an high interest in doing that or commercial support we can do that.
Or when we are bored but in my opinion we are not at that level yet. We have enough things to do and supporting more versions is a lot more work.
17:57:11
@r_i_s:matrix.orgris_otherwise my organization wouldn't be paying $x,000 to canonical for continued support of 16.0417:58:03
@r_i_s:matrix.orgris_yes i still see it as a "one day" thing17:58:27
@sandro:supersandro.deSandroAlso if I am rocking unstable or even master or Sid on the Debian side that won't work well together17:58:41
@r_i_s:matrix.orgris_i'd quite like that "one day" to be relatively sooner personally but 🤷‍♂️17:59:08
@sandro:supersandro.deSandro
In reply to @r_i_s:matrix.org
well... what is "our" in this case? are "we" just a bunch of people who have self-selected as people who don't care about supporting old software?
I personally don't care to much about old software
17:59:37
@qyliss:fairydust.spaceAlyssa Rossperhaps people this is important to could start maintaining this outside of Nixpkgs, as an alternate Nixpkgs tree or an overlay.18:00:28
@andreas.schraegle:helsinki-systems.deajs124isn't that what flying circus does?18:00:52
@sandro:supersandro.deSandro
In reply to @r_i_s:matrix.org
otherwise my organization wouldn't be paying $x,000 to canonical for continued support of 16.04
If you have a lack of monitoring, backups and testing updating can be quiet scary
18:01:11
@qyliss:fairydust.spaceAlyssa Rossthis would be different enough to Nixpkgs in its current state that it might make sense for it to be "nixpkgs-lts" or something18:01:12
@r_i_s:matrix.orgris_

If you have a lack of monitoring, backups and testing updating can be quiet scary

it's... much more complicated than that, but yes it's a bad place to be

18:02:40
@andi:kack.itandi-
In reply to @andreas.schraegle:helsinki-systems.de
isn't that what flying circus does?
Yes, they are doing something similiar. I am not sure what the scope of their "security" coverage is but perhaps most famous packages.
18:04:30
@r_i_s:matrix.orgris_i need to go shopping now... go, review some security PRs, people...18:05:53
@asymmetric:matrix.dapp.org.ukasymmetric
In reply to @andreas.schraegle:helsinki-systems.de
isn't that what flying circus does?
do you have more info about this? my company might be interested
18:06:33
@hexa:lossy.networkhexahttps://flyingcircus.io18:07:02
@asymmetric:matrix.dapp.org.ukasymmetric
In reply to @hexa:lossy.network
https://flyingcircus.io
right, couldn't find any mention of "lts support for nixpkgs" or similar
18:07:26
@hexa:lossy.networkhexalet's not kid ourselves, I don't think our security state is bad or needs changing into debians direction18:07:26
@hexa:lossy.networkhexalts support means somepone has to pay for the shitty backports to happen18:07:55
@hexa:lossy.networkhexathat can happen outside of nixpkgs, since the nixpkgs model is easy to fork, but alot of being "lts" is about having moldy versions of software, and nobody likes to work with that for free18:09:49
@hexa:lossy.networkhexain debian people are paid for maintaining things, this is especially true for the lts extensions of their releases18:10:28
@hexa:lossy.networkhexaand following debian releases would mean a change to our release cadence, as else you'd need to support multiple stable releases in parallel - not feasible18:12:35
@hexa:lossy.networkhexathe one month overlap between the old and new stable is annoying enough fwiw18:13:47
@hexa:lossy.networkhexa * the one month overlap between the old and new stable right now is annoying enough fwiw18:13:55
@sandro:supersandro.deSandro
In reply to @hexa:lossy.network
and following debian releases would mean a change to our release cadence, as else you'd need to support multiple stable releases in parallel - not feasible
right now we release two times a year a big release. Debian does once every few years.
18:32:00
@philipp:xndr.dephilippJust to be clear I never said we should change the release schedule, I just wondered whether it would be feasible to use debians patches to keep certain packages around a while longer.18:33:15
@sandro:supersandro.deSandroyou can always just pin the older version and apply the patches yourself but doing a minor or major update is a lot of times easier18:35:42

Show newer messages


Back to Room ListRoom Version: 6