00:05:03sralracer quits [Client Quit]
00:09:01<immibis>c3manu: browsers always do syscalls directly... so does every other program...
00:09:19<immibis>even with glibc you can do direct syscalls by calling syscall(SYS_open, whatever...)
00:09:33<immibis>and the glibc wrappers around most syscalls are basically direct wrappers anyway
01:35:36BlueMaxima joins
01:36:08etnguyen03 (etnguyen03) joins
01:43:45Naruyoko5 quits [Quit: Leaving]
01:53:42useretail quits [Quit: Leaving]
02:34:38wickedplayer494 quits [Remote host closed the connection]
02:39:21Gadelhas5625 joins
02:42:33Gadelhas5623 joins
02:42:50Gadelhas562 quits [Ping timeout: 260 seconds]
02:42:50Gadelhas5623 is now known as Gadelhas562
02:45:53<pabs>c3manu that_lurker - James Mickens is another great speaker https://mickens.seas.harvard.edu/wisdom-james-mickens
02:46:20Gadelhas5625 quits [Ping timeout: 260 seconds]
02:46:36<pabs>(scroll down)
02:54:17lukash98 joins
03:06:54<pabs>https://firesky.tv/ - Bluesky firehose site
03:07:26<pabs>websocket: wss://firesky.tv
03:07:48<pabs>rss site, needs a filter parameter https://rss.firesky.tv
03:07:57SootBector quits [Ping timeout: 240 seconds]
03:08:42SootBector (SootBector) joins
03:14:40etnguyen03 quits [Client Quit]
03:15:16etnguyen03 (etnguyen03) joins
03:17:37sec^nd quits [Remote host closed the connection]
03:18:10sec^nd (second) joins
03:22:43wickedplayer494 joins
03:39:40etnguyen03 quits [Remote host closed the connection]
03:40:09sec^nd quits [Remote host closed the connection]
03:40:27sec^nd (second) joins
03:41:12<pabs>in case anyone is using puppet: https://www.puppet.com/blog/open-source-puppet-updates-2025
03:41:23<pabs>now might be the time to switch away from it
03:44:15<steering>"it's because supply chain attacks, even though it has nothing to do with them. just trust us!"
03:45:13<steering>and "same license" but then "The new development license is an EULA"?? what are they actually saying? that they're not going to do development under Apache so it's just going to rot?
03:46:24<pabs>the binaries will be under the EULA, they will be doing dev in a private git repo and the public git repo will get some lower amount of commits
03:47:14<pabs>and anarcat mentioned something about no longer publishing ruby gems
03:53:06<pabs>(anarcat and other Tor folks are maintaining the puppet source+binary packages uploaded to Debian)
03:53:44<steering>ah the good ol' "we still want you to do unpaid work for us but we're not going to give anything back"
03:54:18BlueMaxima quits [Read error: Connection reset by peer]
04:11:47FartWithFury (FartWithFury) joins
04:14:21<nulldata>https://wordpressenginetracker.com/
04:16:29<FartWithFury>Yeah wp admin is going nuts
04:34:31<@OrIdow6^2>"ship any new binaries and packages developed by our team to a private, hardened, and controlled location"
04:34:38<@OrIdow6^2>What I imagine: concrete bunker
04:35:10<@OrIdow6^2>What it probably actually is: a webpage with a single checkbox
05:40:27FartWithFury quits [Read error: Connection reset by peer]
05:58:12<that_lurker>pabs: Could maybe be a good idea to create external link grabber for the bluesky firehose and run them in #//
05:59:04<pabs>sounds good to me, I didn't manage to get anything from the websocket yet. focused on #wikibot for a bit
05:59:22<pabs>I'm not familiar with #// very much btw
06:34:25pixel (pixel) joins
07:11:03pixel leaves
07:24:20Dango360_ (Dango360) joins
07:27:18Dango360 quits [Ping timeout: 240 seconds]
07:35:05MetaNova quits [Ping timeout: 260 seconds]
07:38:45midou quits [Remote host closed the connection]
07:42:20MetaNova (MetaNova) joins
08:00:19midou joins
09:06:33ducky quits [Ping timeout: 260 seconds]
09:07:31lennier2_ quits [Quit: Going offline, see ya! (www.adiirc.com)]
09:15:17nulldata quits [Client Quit]
09:16:11nulldata (nulldata) joins
09:23:00Doranwen quits [Ping timeout: 260 seconds]
09:59:45driib quits [Quit: The Lounge - https://thelounge.chat]
10:00:05driib (driib) joins
11:05:36sralracer joins
11:14:47Dango360_ quits [Read error: Connection reset by peer]
11:23:56ducky (ducky) joins
12:00:03Bleo182600722719623 quits [Quit: The Lounge - https://thelounge.chat]
12:02:48Bleo182600722719623 joins
12:05:24Dango360 (Dango360) joins
12:15:03Doranwen (Doranwen) joins
12:22:18Doranwen quits [Ping timeout: 240 seconds]
12:23:03Doranwen (Doranwen) joins
13:18:28<that_lurker>"How to self-host all of Bluesky (except the AppView (for now))" https://alice.bsky.sh/post/3laega7icmi2q
13:21:00Doranwen quits [Ping timeout: 260 seconds]
13:21:30Doranwen (Doranwen) joins
13:26:48midou quits [Remote host closed the connection]
13:26:55midou joins
13:29:30Doranwen quits [Read error: Connection reset by peer]
13:29:52Doranwen (Doranwen) joins
13:54:58xDEADBEEF quits [Ping timeout: 240 seconds]
13:55:49th3z0l4 joins
13:57:20<immibis>steering: developers are champing at the bit to do unpaid labour for mega corporations, if you hadn't noticed. It's why everything is MIT licensed these days
14:00:40th3z0l4 quits [Ping timeout: 260 seconds]
14:00:59<Harzilein>immibis: that's a very simplistic view
14:01:00th3z0l4 joins
14:51:07<immibis>the simplest explanation is usually the correct one
14:54:32Chris50100 (Chris5010) joins
14:56:18Chris5010 quits [Ping timeout: 240 seconds]
14:56:18Chris50100 is now known as Chris5010
16:56:42qwertyasdfuiopghjkl18 joins
17:00:22qwertyasdfuiopghjkl quits [Ping timeout: 255 seconds]
17:05:35katocala quits [Ping timeout: 260 seconds]
17:06:21katocala joins
17:27:38katocala quits [Ping timeout: 240 seconds]
17:28:09katocala joins
18:04:11<c3manu>immibis: welp, sounds like understand even less of that stuff than i thought ^^
18:04:48ducky quits [Read error: Connection reset by peer]
18:04:53ducky (ducky) joins
18:05:21<immibis>you should be worried if they say JAVASCRIPT can do syscalls directly. If it's just the browser itself, that's fine.
18:05:50<immibis>it's actually useful for sandboxing to know exactly what syscalls your process makes, bypassing glibc
18:07:14<nicolas17>or for setting up the sandbox, which may involve newly-introduced syscalls that are not exposed by glibc
19:13:05<immibis>glibc always had a bypass mechanism to make direct syscalls, and it knows the sandboxing syscalls (seccomp, prctl, bpf)
19:13:25<immibis>the problem is if you whitelist the open syscall, but when you call the open wrapper, it actually makes an openat syscall
19:13:49<immibis>you have to know things like that, and they can change. Making syscalls directly makes a more reliable sandbox because you know which ones they are.
19:15:58Aoede_ is now known as Aoede
19:26:38ThreeHM quits [Ping timeout: 240 seconds]
19:28:58ThreeHM (ThreeHeadedMonkey) joins
20:12:59Dango360_ (Dango360) joins
20:16:46DigitalDragons quits [Read error: Connection reset by peer]
20:16:47Exorcism quits [Read error: Connection reset by peer]
20:16:55Dango360 quits [Ping timeout: 260 seconds]
20:17:02DigitalDragons (DigitalDragons) joins
20:17:11Exorcism (exorcism) joins
20:39:09BlueMaxima joins
20:51:07DigitalDragons quits [Client Quit]
20:51:07Exorcism quits [Client Quit]
20:52:26Exorcism (exorcism) joins
20:53:01DigitalDragons (DigitalDragons) joins
21:26:10Dango360_ quits [Read error: Connection reset by peer]
21:27:05useretail joins
21:28:14etnguyen03 (etnguyen03) joins
21:32:33Dango360 (Dango360) joins
21:59:19BearFortress quits [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
22:30:08etnguyen03 quits [Client Quit]
22:40:02BearFortress joins
22:40:29revi quits [Changing host]
22:40:29revi (revi) joins
22:47:22<kpcyrd>the puppet.com blogpost sounds like they are completely lost and have no idea what they are doing. if you want good supply-chain security you try to be as transparent as possible and deploy reproducible builds, what they are doing is the polar opposite
22:49:37<kpcyrd>I don't understand the connection to javascript and syscalls
22:49:51<kpcyrd>if you squint hard enough html can do syscalls
22:50:08<immibis>javascript and syscalls have nothing to do with puppet - they have to do with javascript and syscalls
22:51:42<kpcyrd>the trick to Linux is understanding everything is assembly interfaces that happen to use the C calling convention
22:51:51<kpcyrd>seccomp is infamous for being painful
22:52:11<kpcyrd>not just because of libc, but also because of dynamic linking, and downstream patches
22:53:02<kpcyrd>Debian patches their libc in ways that requires additional syscalls, so if you develop on Arch Linux the program may not work when compiled on Debian
22:53:49<kpcyrd>(when using hand-rolled syscall seccomp allow-lists)
22:59:14revi quits [Quit: Updating details, brb]
22:59:21revi (revi) joins
23:00:35<kpcyrd>(the catch with dynamic linking is that "use of new syscall" is not considered a breaking change, but with seccomp it may, potentially leaving your program in a broken state until somebody notices and a new update is rolled out)
23:09:53etnguyen03 (etnguyen03) joins
23:10:48superkuh quits [Remote host closed the connection]
23:44:38<steering>kpcyrd: everything everywhere in computers is "assembly interfaces" :)
23:46:23<nicolas17>I read of an Intel engineer who said "oh assembly is too high level for me"
23:46:35<kpcyrd>steering: good luck putting assembly into /bin/sh :)
23:46:36<steering>ok, fine, except maybe microcode :D
23:47:10<nicolas17>obligatory https://gist.github.com/nicolas17/966a03ce49f949dd17b0123415ef2e31