#Tarsnap

Lucas Werkmeisternew blog post: Reduce The Size Of Your Tarsnap Backups With This One Weird Trick (the trick is “pay attention to the size of your backups”) <a href="https://lucaswerkmeister.de/posts/2024/12/10/tarsnap-backup-size/" rel="nofollow noopener" translate="no" target="_blank">https://lucaswerkmeister.de/posts/2024/12/10/tarsnap-backup-size/</a><a href="https://wikis.world/tags/tarsnap" class="mention hashtag" rel="nofollow noopener" target="_blank">#tarsnap</a> <a href="https://wikis.world/tags/backup" class="mention hashtag" rel="nofollow noopener" target="_blank">#backup</a>

Lucas WerkmeisterHere’s a small but useful shell function to analyze the size of tarsnap backups according to your current --exclude config without the overhead of creating and extracting the backups: <a href="https://github.com/lucaswerkmeister/home/blob/master/.bashrc.d/ncdu-tarsnap" rel="nofollow noopener" translate="no" target="_blank">https://github.com/lucaswerkmeister/home/blob/master/.bashrc.d/ncdu-tarsnap</a><a href="https://wikis.world/tags/tarsnap" class="mention hashtag" rel="nofollow noopener" target="_blank">#tarsnap</a> <a href="https://wikis.world/tags/backup" class="mention hashtag" rel="nofollow noopener" target="_blank">#backup</a>

Jason Tubnor 🇦🇺Just an <a class="hashtag" href="https://soc.feditime.com/tag/openbsd" rel="nofollow noopener" target="_blank">#OpenBSD</a> PSA for <a class="hashtag" href="https://soc.feditime.com/tag/tarsnap" rel="nofollow noopener" target="_blank">#Tarsnap</a> users. There has been an ABI change in OpenBSD and previous builds of tarsnap will not work. You'll need to rebuild tarsnap from ports after upgrading to 7.6. Tarsnap is not packaged by the project because of licensing issues.

Kevin Karhan :verified:<a href="https://grapheneos.social/@GrapheneOS" class="u-url mention" rel="nofollow noopener" target="_blank">@GrapheneOS</a> It doesn't change the fact that <a href="https://infosec.space/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> requires <a href="https://infosec.space/tags/transparency" class="mention hashtag" rel="nofollow noopener" target="_blank">#transparency</a> and thus full access & reproduceability from source.To give you a good example, source-available <a href="https://infosec.space/tags/Tarsnap" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tarsnap</a> demonstrates that stuff is truly securely encrypted by enabling <a href="https://infosec.space/tags/SelfCustody" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfCustody</a> of keys and thus show they can't decrypt anything!<ul><li>You may call me paranoid, but having 'massive trust issues' saved not only my own life more often than I'd be able to disclose so you may see this as a 'survivorship bias', but we'll only see <a href="https://infosec.space/tags/MassSurveillance" class="mention hashtag" rel="nofollow noopener" target="_blank">#MassSurveillance</a> becoming impossible when people ain't just users of some big-ass platform that can be easily targeted once it becomes inconvenient for it's host nation, but actually push for <a href="https://infosec.space/tags/decentralization" class="mention hashtag" rel="nofollow noopener" target="_blank">#decentralization</a> and <a href="https://infosec.space/tags/TechLiteracy" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechLiteracy</a>.</li></ul>"Just use A, B, C & D, E, F" is the real threat as it sugfests people a <a href="https://grapheneos.social/@GrapheneOS/113047066349052609" rel="nofollow noopener" target="_blank">false sense if security</a>.<ul><li>Just like a dresh <a href="https://infosec.space/tags/TechInspection" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechInspection</a> doesn't prevent one to hose an engine due to lack of oil!</li></ul>Collecting any <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener" target="_blank">#PII</a> <a href="https://grapheneos.social/@GrapheneOS/113047045993549018" rel="nofollow noopener" target="_blank">IS the illicit activity</a> NO MATTER the excuse...<ul><li>You may <a href="https://grapheneos.social/@GrapheneOS/113047083361853248" rel="nofollow noopener" target="_blank">choose ignorance</a> but like with <a href="https://infosec.space/tags/LavaBit" class="mention hashtag" rel="nofollow noopener" target="_blank">#LavaBit</a>, <a href="https://infosec.space/tags/EncroChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#EncroChat</a> & <a href="https://infosec.space/tags/AN%C3%98M" class="mention hashtag" rel="nofollow noopener" target="_blank">#ANØM</a> I tend to turn out to be right all along.</li></ul>Sooner or later the <a href="https://infosec.space/tags/Enshittification" class="mention hashtag" rel="nofollow noopener" target="_blank">#Enshittification</a> of <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signal</a> will reach a point where you'd rethink and consider apologizing...

Kevin Karhan :verified:<a href="https://grapheneos.social/@GrapheneOS" class="u-url mention" rel="nofollow noopener" target="_blank">@GrapheneOS</a> I think both apps are shit as *both <a href="https://infosec.space/tags/Telegram" class="mention hashtag" rel="nofollow noopener" target="_blank">#Telegram</a> and <a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@signalapp</a> demand <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener" target="_blank">#PII</a> in the form of <a href="https://infosec.space/tags/PhoneNumbers" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhoneNumbers</a>.<ul><li><a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signal</a> at least has their <a href="https://infosec.space/tags/client" class="mention hashtag" rel="nofollow noopener" target="_blank">#client</a>'s source code published so similar to like <a href="https://infosec.space/tags/Tarsnap" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tarsnap</a> it's more trustworthy by virtue of better <a href="https://infosec.space/tags/transparency" class="mention hashtag" rel="nofollow noopener" target="_blank">#transparency</a>...</li></ul>OFC Telegram is (by my personal observation) almost exclusively being used by <a href="https://infosec.space/tags/Scammers" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scammers</a> and other <a href="https://infosec.space/tags/TechIlliterate" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechIlliterate</a> criminals.<ul><li>Trusting Telegram is like trusting <a href="https://infosec.space/tags/EncroChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#EncroChat</a> or <a href="https://infosec.space/tags/AN%C3%98M" class="mention hashtag" rel="nofollow noopener" target="_blank">#ANØM</a> aka. <a href="https://infosec.space/tags/OperationIronside" class="mention hashtag" rel="nofollow noopener" target="_blank">#OperationIronside</a> aka. <a href="https://infosec.space/tags/OperationTr%C3%B8janShield" class="mention hashtag" rel="nofollow noopener" target="_blank">#OperationTrøjanShield</a>: It literally has <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Govware</a> <a href="https://infosec.space/tags/Backdoors" class="mention hashtag" rel="nofollow noopener" target="_blank">#Backdoors</a> because the <a href="https://infosec.space/tags/UAE" class="mention hashtag" rel="nofollow noopener" target="_blank">#UAE</a> of all plaves would've swatted their "HQ" if not forved <a href="https://infosec.space/tags/Durov" class="mention hashtag" rel="nofollow noopener" target="_blank">#Durov</a> at gunpoint to integrate it into it if it wasn't there...</li></ul>

Recent searches

Search options

Administered by:

Server stats: