Conversation

Notices

1. Embed this notice
   Jorin, Subcontra Sorceress (jorin@soc.punktrash.club)'s status on Friday, 07-Mar-2025 04:39:47 JST Jorin, Subcontra Sorceress

   You’ve heard of serverless cloud architecture :meowtired: :blobcatsleep:

   Now, get ready for… 🥁🥁🥁

   :blobcheerL: Cloudless server architecture :blobcheerR:

   We’re offering features you thought you could only dream of:

   • Hardened database security: Databases don’t have to be exposed to the network thanks to the wonders of On-System Databases™ and Unix Sockets™, hardening security tenfold!
   • Latency-free database connections: As if that wasn’t good enough, On-System Databases™ allow you to dramatically reduce latency by bypassing the need for pesky network connections!
   • On-Demand Web Worker Process Spawning™ using the Common Gateway Interface™
   • Bare-Metal Access™ to On-Server Storage™ for unparalleled Read™ and Write™ speeds
   • Predictable costs: No more surprise bills. Pay only for what you specify! Our patent-pending Hardware Limitations™ automatically throttles your cloudless server if you reach capacity
   • Documentation: tired of trying to navigate through the jungle of outdated and incorrect Azure or AWS documentation? Don’t fret! Operating systems are documented by the most dedicated gangs of nerds you can find on freenode!
   • kaia and snacks like this.
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Friday, 07-Mar-2025 04:39:46 JST feld

     in reply to
     @jorin I deploy my services in jails on FreeBSD and when they need database access I have the Postgres unix socket mounted into the jails that need it. No network access for the database == fffffast
     
     However, I've been warned that container/jail escape by abuse of the socket is somehow theorhetically possible, though I have never seen a clear explanation of how it would work. (same for syslog actually -- I mount in the socket for that)
   • Embed this notice
     Shannon Literally Persists (shannonpersists@mastodon.social)'s status on Friday, 07-Mar-2025 08:27:02 JST Shannon Literally Persists

     in reply to

     • feld

     @feld https://soc.punktrash.club/users/jorin Syslogs don't end up in jail like ever

   • Embed this notice
     feld (feld@friedcheese.us)'s status on Friday, 07-Mar-2025 08:27:02 JST feld

     in reply to

     • Shannon Literally Persists
     @shannonpersists my goal is to allow the software in the jail to emit their logs via syslog but not have to run a syslogd in the jail to then exfiltrate it out elsewhere. If I mount in the socket from outside the jail the host itself can consume the logs of all the jail processes automaticaly. Instead of solving it this way, Docker runs the service in the foreground and captures the log output that way. I'll do that as well with daemontools/runit, but then have it piped through logger(1) which will push it through syslog
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Friday, 07-Mar-2025 09:00:27 JST feld

     in reply to

     • Shannon Literally Persists
     @shannonpersists that's a good point you could use that to "stingray" a jail
   • Embed this notice
     Shannon Literally Persists (shannonpersists@mastodon.social)'s status on Friday, 07-Mar-2025 09:00:30 JST Shannon Literally Persists

     in reply to

     • Shannon Literally Persists
     • feld

     @feld @shannonpersists Do you mean you are trying to Stingray the jail? Hope so that sounds Uber-cool and as a sysadmin you'll never get in troubs!