!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

414 Members
(Technical) development of Lix, the package manager, a Nix implementation. Please be mindful of ongoing technical conversations in this channel.139 Servers

Load older messages


SenderMessageTime
27 Jul 2025
@raitobezarius:matrix.orgraitobezariusI wonder if we should just build a test for it16:06:08
@raitobezarius:matrix.orgraitobezarius
In reply to @emilazy:matrix.org
I don't know the threat model of the CI builders but it would be really nice to have sandbox testing by way of _NIX_TEST_NO_SANDBOX=1.
CI builders lives themselves in a user namespace
16:06:21
@raitobezarius:matrix.orgraitobezariusor on the baremetal for some of them16:06:26
@emilazy:matrix.orgemilymacOS16:06:27
@emilazy:matrix.orgemilyno such thing16:06:30
@raitobezarius:matrix.orgraitobezariusah yes16:06:31
@k900:0upti.meK900 The actual problem this fixed was some convoluted symlink setup that I forgot why it's like that 16:06:33
@raitobezarius:matrix.orgraitobezariusfor macOS, they live on the baremetal16:06:42
@raitobezarius:matrix.orgraitobezariusthere's no true threat model16:06:44
@emilazy:matrix.orgemilyso every tested build runs on persistent bare metal and the Nix sandbox isn't even turned on?16:07:00
@raitobezarius:matrix.orgraitobezarius
In reply to @emilazy:matrix.org
so every tested build runs on persistent bare metal and the Nix sandbox isn't even turned on?
I'm like almost certain that the Nix sandbox isn't even turned on on these builders yep
16:07:19
@raitobezarius:matrix.orgraitobezariusBasically, all of this is blocked on Darwin sysadmin16:07:27
@emilazy:matrix.orgemilyit's not because if it was you'd have caught the UDS regression 😆16:07:33
@raitobezarius:matrix.orgraitobezariussowwy16:07:42
@emilazy:matrix.orgemilyeven ofborg insisted on the sandbox to remove the allow list of users on Darwin :P16:07:46
@emilazy:matrix.orgemilybut ok16:07:50
@raitobezarius:matrix.orgraitobezariusBut if you open an issue in Lix regarding this16:07:54
@raitobezarius:matrix.orgraitobezariusand you put the requirements for the CI16:07:59
@raitobezarius:matrix.orgraitobezariusI can take a look once I have some Darwin sysadmin to dedicate16:08:05
@emilazy:matrix.orgemilywhy does that sound like it's going to get assigned to me? :)16:08:17
@raitobezarius:matrix.orgraitobezarius(I know I make you all open issues, but I swear we close them, right?)16:08:20
@emilazy:matrix.orgemilyI put up https://gerrit.lix.systems/c/lix/+/3521 FWIW although I ran out of time box and didn't fix it16:08:26
@raitobezarius:matrix.orgraitobezarius
In reply to @emilazy:matrix.org
why does that sound like it's going to get assigned to me? :)
I doubt :P
16:08:36
@raitobezarius:matrix.orgraitobezariusRoot access to the CI builders is not a simple decision16:08:46
@emilazy:matrix.orgemilyfrankly, I am not sure what the actual desired threat model is so I'm not sure what the requirements would be to have Darwin sandbox testing without breaking it16:08:50
@emilazy:matrix.orgemily(I'm not even sure if running CI requires manual approval)16:09:18
@raitobezarius:matrix.orgraitobezariusWhat I'm planning to do to our CI builders is to have go through reinitialization daily or something16:09:21
@raitobezarius:matrix.orgraitobezariusSo I am not afraid of about an attacker getting persistence16:09:44
@raitobezarius:matrix.orgraitobezariusNetwork isolation should be fine as well16:09:51
@emilazy:matrix.orgemilyyou could just have a macOS host that only runs a macOS VM and restores it to a snapshot before every build16:09:54

Show newer messages


Back to Room ListRoom Version: 10