Spread the word!
From Cointelegraph.com: Bitcoin stays under $30K as LUNA gains 600% during ‘insane volatility’ https://cointelegraph.com/news/bitcoin-stays-under-30k-as-luna-gains-600-during-insane-volatility #lunaprice #BTCprice #Bitcoin
The bulk of Tarfile extraction logic involves some shared code for reading Tarfiles with callback to copy the read data into new files.
This callback involves updating the reader's scanner, determining based on options whether to skip the file for its name starting with "../", otherwise determines whether to skip the file possibly involving a prompt if requested by adjusting the scanner, possibly decodes the header to output status, possibly evaluates queued `fstat` adjustments immediately, ...
@NYC2600 welcomes all the fleeing twitter refugeelons into The Federation, and we invite you to swap the virtual metaspace you've been accosted at for a real actual meet-space that you'll grow accustomed to: the Citigroup Center Atrium.
Take the 🅔, 🅜, or ➏ trains to Lexington Av-53 Street
Station. Hacking hour starts at 5PM. Further details at http://2600.nyc
... possibly carefully renames any existing files by this name to back them up, checks the header to determine which codepath to use to generate this file falling back to skipping the entry, & possibly attempts to restore the backedup file.
Extracting a file involves carefully opening the file setting correct attributes, running through a shellcommand, or outputting to stdout before adjusting the scanner, copying each block to that file handling with fastpath for contiguous files, ...
Controlling the UK's Private Intelligence Industry
... updates scanner, possibly configures `fstat` info, & closes the file. Sparsefiles use a dispatch table presumably crossplatform portability.
For directories it validates the entry is safe & only contains files within the tarfile, decodes directory permissions, & carefully/repeatedly attempts to create it handling symlinks specially before enqueueing an operation to update the directory's `fstat` info.
For symlinks it might create placeholder file first to avoid complaints.
For hardlinks it might create a placeholder file (two conditions) or it'll repeatedly attempt to create the symlink before decoding the error if any.
For device files it syscalls `mknodat` before decoding the error & adjusting `fstat` info. For FIFOs it similarly syscalls `mkfifoat`.
Other filetypes issue warnings & are skipped. Then it validates results possibly removing the existing file, or checking timestamps.
5/? Next: reading tarfile.
Ended up dumping some thoughts about ADHD-adjacent stuff and attention dysregulation and, believe it or not, pen plotters over on birb site while plotting something earlier:
I did some more testing, and found that iOS DOES NOT provide the device name to the DHCP server if you're using a private MAC address! So they're doing the right thing and you don't have to worry about this that much with default settings.
I'm very pleased!
Here's what it looks like on the DHCP server, with private MAC address on, and off, with an iPad running iOS 15.
You can see the device name (Vitani) when it's off.
Got some remarkable music dropped on me today: https://www.youtube.com/watch?v=hbcW7nxcP3E&list=PLsSVC1G6h5e5Z8dd_0TGlaai71Rzo1bT7
We'll be on the air tonight at 19:00 EDT. Listen live on 99.5 FM in New York or at https://wbai.org/playernew.html
#DEFCON Group in New Jersey. We meet at Sub Culture, Jersey City once a month to work on hardware/software projects! CFP: info (at) defcon201 [dot] org
This service is offered by alarig.
Beer, privacy and free software lovers. Join us!