Post B7pdjcat2cvN3YDj2u by domi@donotsta.re
 (DIR) More posts by domi@donotsta.re
 (DIR) Post #B7pSEGaHiwwIJzmjiq by grawity@social.treehouse.systems
       0 likes, 0 repeats
       
       @domi I'm now curious about how the -p option in your `wall` is implemented
       
 (DIR) Post #B7pSEGqwj0Gb9fa2gy by domi@donotsta.re
       0 likes, 0 repeats
       
       @grawity wall is /usr/local/bin/wall, which is a shell wrapper that also takes care to save stuff to a backlog file (unless -g is in the cmdline), and sends it over to fedi via curl. the log file is literally world-writable, and the fedi creds are in the shell script itself, we’re being protected by a comment which says # BITTE NICHT HACKEN :^)if i were to make this “secure”: bash service listening on a socket, wrapper calling wall and writing a message to said socket
       
 (DIR) Post #B7pdgYAl1X82TUXAwK by weirdtreething@donotsta.re
       1 likes, 0 repeats
       
       @domi @grawity enterprise level security
       
 (DIR) Post #B7pdjcOplRHcSAa6G8 by grawity@social.treehouse.systems
       0 likes, 0 repeats
       
       @domi ah, I thought it was a whole patched `wall`, or something like that(I suppose `doas /usr/local/bin/yeet-it-over-the-wall $logfile` to run a non-world-readable script would probably be as secure as a socket service, with less moving parts)
       
 (DIR) Post #B7pdjcat2cvN3YDj2u by domi@donotsta.re
       0 likes, 0 repeats
       
       @grawity well, more automations would be necessary, as users are meant to be able to read the backlog with wallback :)