Website | https://eternallybored.org/ |
Website | https://eternallybored.org/ |
I wish VPN CEOs a very merry Klämrisk
@ska @kloenk @navi Before that, the custom kernels had patches to allow for longer argv. I no longer remember what limit was set in those patches. Those were the days of /proc/bogdan
For those interested in a little fun Google history, Bogdan was a key figure in the platforms team and renowned for saying no to everything (which was, mostly, the correct call, there was a lot of outlandishness at the time). Someone added /proc/bogdan, which would just return "no" when catted.
@kloenk @navi Back when 128 kB was the limit for argv+envp, Google was hitting it too because they passed all the configuration for their whole software stack on the command line as --long-option=value switches.
Their solution? Compress the command line. So every binary started by ungzipping argv[1] and parsing it to get the configuration.
The person explaining this to me saw my horrified face, and said with the perfect Hide The Pain Harold smile: "a series of individually completely rational and reasonable decisions led to this." and I have been thinking a lot about it since.
something hands me a Google Cloud Storage signed URL with an Expires option set. I can upload stuff to it with a PUT.
if I complete the upload before the expiry time, it uploads successfully. if I start the upload before the expiry time, but it finishes after the expiry time, it fails.
anyone know if there's a trick where you can get that last case to succeed? I vaguely recall that there are some fancy alternative upload schemes (chunking?) and I'm wondering if they can trick the expiry.