Mathstodon

0 posts0 participants0 posts today

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 noreferrer" 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 noreferrer" target="_blank">#tarsnap</a> <a href="https://wikis.world/tags/backup" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#tarsnap</a> <a href="https://wikis.world/tags/backup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#backup</a>

Kevin Karhan :verified:<a href="https://mastodon.social/@xerxespersrex" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@xerxespersrex</a> nodds in agreement...<ul><li>Shit like <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a> & <a href="https://infosec.space/tags/RSAL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RSAL</a> is IMHO even <a href="https://www.youtube.com/watch?v=5v72pNaincM" rel="nofollow noopener noreferrer" target="_blank">worse</a> than <a href="https://infosec.space/tags/SourceAvailable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SourceAvailable</a> as it's literally "<a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AssholeLicensing</a>"...</li></ul>At least most source available products like <a href="https://infosec.space/tags/Tarsnap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tarsnap</a> are <a href="https://www.tarsnap.com/open-source.html" rel="nofollow noopener noreferrer" target="_blank">honest</a> that they are not <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a>!

Kevin Karhan :verified:<a href="https://mastodon.social/@shoppingtonz" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@shoppingtonz</a> <a href="https://social.labmonkeys.space/users/indigo" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@indigo</a> I mean, <a href="https://infosec.space/tags/FakeFLOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FakeFLOSS</a> is a problem...<ul><li>Because unlike say <a href="https://infosec.space/tags/SourceAvailable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SourceAvailable</a> (i.e. <a href="https://infosec.space/tags/Tarsnap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tarsnap</a>) where it's an act of <a href="https://infosec.space/tags/transparency" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#transparency</a>, it's an actual act of <a href="https://infosec.space/tags/AssetDenial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AssetDenial</a> and hinderance to honest <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FLOSS</a> whilst also being more hostile than <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CCSS</a>...</li></ul>

Martin PughAfter creating an account, almost a decade ago and depositing $5 of credit, I've finally started making use of Tarsnap - "Online backups for the truly paranoid".Most of my stuff is either ephemeral, or simple enough to rebuild, but a few new things recently made me realise they would be a right pain in the backside to have to recreate so it's time I started getting things backed up properly.Setup one machine this morning and got my first backup in place. I'll wait until tomorrow to make sure the overnight cron job also works and of course make sure I can recover the backups before I start celebrating.Now, where did I put that <a href="https://io.mwl.io/@mwl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mwl</a> book?<a href="https://www.tarsnap.com/" rel="nofollow noopener noreferrer" target="_blank">https://www.tarsnap.com/</a><a href="https://bsd.network/tags/tarsnap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tarsnap</a> <a href="https://bsd.network/tags/backup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#backup</a>

Jason Tubnor 🇦🇺So many discussions at <a class="hashtag" href="https://soc.feditime.com/tag/eurobsdcon2024" rel="nofollow noopener noreferrer" target="_blank">#EuroBSDCon2024</a> we had to make a second episode. Kick back, relax and enjoy the discussions with <a class="u-url mention" href="https://bird.makeup/users/cperciva" rel="nofollow noopener noreferrer" target="_blank">@cperciva</a> <a class="u-url mention" href="https://bsd.network/@AFresh1" rel="nofollow noopener noreferrer" target="_blank">@AFresh1</a> <a class="u-url mention" href="https://tilde.zone/@notthebee" rel="nofollow noopener noreferrer" target="_blank">@notthebee</a> and Liam Proven from <a class="hashtag" href="https://soc.feditime.com/tag/theregister" rel="nofollow noopener noreferrer" target="_blank">#theregister</a> . This week on <a class="hashtag" href="https://soc.feditime.com/tag/bsdnow" rel="nofollow noopener noreferrer" target="_blank">#BSDNow</a> <a href="https://www.bsdnow.tv/580" rel="nofollow noopener noreferrer" target="_blank">https://www.bsdnow.tv/580</a> presented by <a class="hashtag" href="https://soc.feditime.com/tag/tarsnap" rel="nofollow noopener noreferrer" target="_blank">#Tarsnap</a> the backups for truely paranoid people (and me) <a href="https://tarsnap.com" rel="nofollow noopener noreferrer" target="_blank">https://tarsnap.com</a>

Jason Tubnor 🇦🇺Just an <a class="hashtag" href="https://soc.feditime.com/tag/openbsd" rel="nofollow noopener noreferrer" target="_blank">#OpenBSD</a> PSA for <a class="hashtag" href="https://soc.feditime.com/tag/tarsnap" rel="nofollow noopener noreferrer" 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://chaos.social/@kasiandra" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@kasiandra</a> ja, das ist allenfalls "<a href="https://infosec.space/tags/SourceAvailable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SourceAvailable</a>", kein <a href="https://infosec.space/tags/OpenSourxe" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSourxe</a> (vgl. <a href="https://infosec.space/tags/Tarsnap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tarsnap</a>)...

Kevin Karhan :verified:<a href="https://mastodontech.de/@alterelefant" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@alterelefant</a> <a href="https://eldritch.cafe/@HauntedOwlbear" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@HauntedOwlbear</a> nodds in agreement<ul><li>If you trust yourself and/or staff to properly make, test, verify, backroll and maintain 3-2-1 backups then <a href="https://infosec.space/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SelfHosting</a> is the more efficient move.</li></ul>That being said I do acknowledge the convenience that solutions like <a href="https://infosec.space/tags/Tarsnap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tarsnap</a> deliver and I think <a href="https://mastodon.social/@cperciva" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@cperciva</a> deserves the revenue he makes with this convenient, fully encrypted <a href="https://infosec.space/tags/backup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#backup</a> solution that makes <a href="https://infosec.space/tags/AmazonGlacier" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AmazonGlacier</a> easy to use...<a href="https://www.tarsnap.com" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.tarsnap.com</a><ul><li>I just can't use it for legal reasons neither he nor anyone else can fix - not even <a href="https://infosec.space/tags/Amazon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Amazon</a> - as per <a href="https://infosec.space/tags/CloudAct" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CloudAct</a>. </li></ul>Needless to say it did inspire me to consider trying my hand on building something similar but without being locked to Amazon:<ul><li>OFC I can't and won't look at tarsnap's code since it's only <a href="https://infosec.space/tags/SourceAvailable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SourceAvailable</a>, not <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FLOSS</a> and I do want it to be different and not copyright infringement!</li></ul>

bahuroopi<a href="https://newsie.social/@slcw" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@slcw</a> <a href="https://masto.lema.org/@santiago" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@santiago</a> My impression is that <a href="https://zirk.us/tags/cryptographers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cryptographers</a> and vulnerability researchers recommend NOT using <a href="https://zirk.us/tags/PGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PGP</a> for any purpose whatsoever. For example, the Latacora post I shared earlier recommends replacing PGP with<a href="https://zirk.us/tags/MagicWormhole" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MagicWormhole</a> for sharing files <a href="https://zirk.us/tags/tarsnap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tarsnap</a> for encrypted backups <a href="https://zirk.us/tags/Signify" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Signify</a> or <a href="https://zirk.us/tags/Minisign" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Minisign</a> for package signing <a href="https://zirk.us/tags/libsodium" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#libsodium</a> for encrypting application data <a href="https://zirk.us/tags/age" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#age</a> for encrypting filesI think the idea is to minimize attack surface by using purpose-built tools.(continues)

Kevin Karhan :verified:<a href="https://fosstodon.org/@carlwgeorge" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@carlwgeorge</a> <a href="https://mastodon.bsd.cafe/@vermaden" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@vermaden</a> <a href="https://fosstodon.org/@samurro" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@samurro</a> <a href="https://mastodon.bsd.cafe/@tara" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@tara</a> Well, that confirms you went <a href="https://infosec.space/tags/ReplyGuy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ReplyGuy</a> on me in the most disingenious way possible, wasting everyones' time and patience in the process.<ul><li>Gues what: Good luck with that sales.pitch, cuz I'd rather give <a href="https://ubuntu.social/@ubuntu" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ubuntu</a> or <a href="https://fosstodon.org/@opensuse" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@opensuse</a> my money cuz that nonchalant attitude is insulting.</li></ul>If you (or <a href="https://infosec.space/tags/RedHat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RedHat</a> / <a href="https://infosec.space/tags/IBM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IBM</a>) don't want to support <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> or anyone using anything they made for <a href="https://infosec.space/tags/RHEL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RHEL</a> without paying, then shure you can do that but then don't expect people to like you.<ul><li><a href="https://infosec.space/tags/grsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#grsec</a> already did that and I'm shure it resulted in 0 extra customers.</li></ul><a href="https://infosec.space/tags/CentOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CentOS</a> was in fact a "gateway distro" and had Red Hat not axed it I would've convinced my (fmr.) boss to consider paying for an RHCSA, but alas I've invested time and effort migrating from CentOS to <a href="https://infosec.space/tags/UbuntuLTS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UbuntuLTS</a> and even negotiated commercial support from <a href="https://infosec.space/tags/Canonical" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Canonical</a> instead, because they were more friendly and welcoming.<ul><li>Personally, I think that Red Hat should just be honest and just stop any <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> contributions, instead try to upsell their customers to <a href="https://infosec.space/tags/zOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#zOS</a> on z/Architecture <a href="https://infosec.space/tags/Mainframe" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mainframe</a>|s instead cuz that was such a great business...</li></ul>Even "Source Available" like <a href="https://infosec.space/tags/Tarsnap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tarsnap</a> is better - espechally in <a href="https://infosec.space/tags/finance" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#finance</a> - because having actual <a href="https://infosec.space/tags/SourceCode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SourceCode</a> available is a matter of <a href="https://infosec.space/tags/trust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#trust</a>.<ul><li>And <a href="https://infosec.space/tags/transparency" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#transparency</a> is the reason people choose <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> over <a href="https://infosec.space/tags/Solaris" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Solaris</a> and other <a href="https://infosec.space/tags/Unix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Unix</a>-esque OSes.</li></ul>But I'm not getting paid to prevent Red Hat from continuing to shoot itself in the foot...<ul><li>In fact, I'd love to short it into the ground!</li></ul><a href="https://infosec.space/@kkarhan/113065846313541796" translate="no" rel="nofollow noopener noreferrer" target="_blank">https://infosec.space/@kkarhan/113065846313541796</a><a href="https://infosec.space/tags/thxbye" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#thxbye</a> <a href="https://infosec.space/tags/next" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#next</a> <a href="https://infosec.space/tags/EOD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EOD</a>

Kevin Karhan :verified:<a href="https://grapheneos.social/@GrapheneOS" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@GrapheneOS</a> It doesn't change the fact that <a href="https://infosec.space/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> requires <a href="https://infosec.space/tags/transparency" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#decentralization</a> and <a href="https://infosec.space/tags/TechLiteracy" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#PII</a> <a href="https://grapheneos.social/@GrapheneOS/113047045993549018" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">choose ignorance</a> but like with <a href="https://infosec.space/tags/LavaBit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LavaBit</a>, <a href="https://infosec.space/tags/EncroChat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EncroChat</a> & <a href="https://infosec.space/tags/AN%C3%98M" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#Enshittification</a> of <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#Telegram</a> and <a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@signalapp</a> demand <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PII</a> in the form of <a href="https://infosec.space/tags/PhoneNumbers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PhoneNumbers</a>.<ul><li><a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Signal</a> at least has their <a href="https://infosec.space/tags/client" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#Scammers</a> and other <a href="https://infosec.space/tags/TechIlliterate" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#EncroChat</a> or <a href="https://infosec.space/tags/AN%C3%98M" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ANØM</a> aka. <a href="https://infosec.space/tags/OperationIronside" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OperationIronside</a> aka. <a href="https://infosec.space/tags/OperationTr%C3%B8janShield" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OperationTrøjanShield</a>: It literally has <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Govware</a> <a href="https://infosec.space/tags/Backdoors" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Backdoors</a> because the <a href="https://infosec.space/tags/UAE" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#Durov</a> at gunpoint to integrate it into it if it wasn't there...</li></ul>

Kevin Karhan :verified:<a href="https://groupe-tazor.com/@Yuki" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Yuki</a> <a href="https://linuxrocks.online/@BrodieOnLinux" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@BrodieOnLinux</a> As shit as RMS his, he's sadly right.Needless to say, <a href="https://mastodon.social/@cperciva" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@cperciva</a> will pretty much remind people that "<a href="https://infosec.space/tags/SourceAvailable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SourceAvailable</a>" is NOT <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> and that <a href="https://infosec.space/tags/Tarsnap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tarsnap</a>'s <a href="https://infosec.space/tags/SourceCode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SourceCode</a> is merely made available for <a href="https://infosec.space/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> and <a href="https://infosec.space/tags/auditability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#auditability</a> reasons as well as enabling people to build it for their (potentially weird) machine... <a href="http://tarsnap.com/open-source.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">http://tarsnap.com/open-source.html</a>

Denys Dmytriyenko<a href="https://io.mwl.io/@mwl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mwl</a> <a href="https://floss.social/@trini" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@trini</a> thanks, nice to know. I'm still figuring out between <a href="https://society.oftrolls.com/tags/tarsnap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tarsnap</a> and amazon <a href="https://society.oftrolls.com/tags/glacier" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glacier</a> and other options for long-long-long term "cold" storage... I do have off-site "warm" backups covered for the most part, but thinking of some long-term off-site cold storage.

Denys Dmytriyenko<a href="https://floss.social/@trini" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@trini</a> and anyone else interested in the discussion (it appears <a href="https://io.mwl.io/@mwl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mwl</a> wrote a book about it) - do you still use <a href="https://society.oftrolls.com/tags/tarsnap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tarsnap</a> on a regular basis? What do you have backing up there, if you don't mind me asking?Backstory: I had an email few weeks ago notifying me of my funds running low. I had some documents backed up there and I had about $50 prepaid - that was like 8+ years ago and I totally forgot about that...I sent additional $20 their way, but was wondering - is it sill worth it?

Kevin Karhan :verified:<a href="https://infosec.exchange/@nazgul" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@nazgul</a> I mean, "credit where credit is due"...Remembers the video where <a href="https://mastodon.social/@cperciva" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@cperciva</a> got interrupted at a presentation on <a href="https://infosec.space/tags/Tarsnap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tarsnap</a> and publicly honored the $2 <a href="https://infosec.space/tags/BugBounty" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BugBounty</a> for a <a href="https://infosec.space/tags/typo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#typo</a>

Kevin Karhan :verified:<a href="https://infosec.space/@sabi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@sabi</a> And I guess mounting anything to i.e. a subdirectory will also circumvent that stuff...Personally I'd prefer <a href="https://infosec.space/tags/Tarsnap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tarsnap</a> over <a href="https://infosec.space/tags/Backblaze" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Backblaze</a> but in fact I can't use either due to <a href="https://infosec.space/tags/GDPR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GDPR</a> & <a href="https://infosec.space/tags/BDSG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BDSG</a> - noncompliance of both...

Kevin Karhan :verified:<a href="https://mastodon.social/@Elucidating" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Elucidating</a> Again: tangents aside antirez quit <a href="https://infosec.space/tags/Redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redis</a> quite a while ago and even if you dislike him, redis and said YouTuber that doesn't invalidate the fact that Redis turned itself into <a href="https://infosec.space/tags/UnfreeSoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnfreeSoftware</a> and violated the <a href="https://infosec.space/tags/license" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#license</a> of the <a href="https://infosec.space/tags/code" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#code</a> contributed to them.Whereas I'd let it slide if they'd been honest about their intentions from day one!Noone's angry that <a href="https://mastodon.social/@cperciva" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@cperciva</a> released <a href="https://infosec.space/tags/Tarsnap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tarsnap</a>'s client as * <a href="https://infosec.space/tags/SourceAvailable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SourceAvailable</a> * because it never was <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FLOSS</a> nor was it * <a href="https://infosec.space/tags/rugpull" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rugpull</a>|ed * with 703 contributors and many of the most active ones not being employed by him.

Kevin Karhan :verified:<a href="https://mastodon.social/@xeraa" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@xeraa</a> <a href="https://oxytodon.com/@fuchsiii" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@fuchsiii</a> <a href="https://mk.absturztau.be/@puniko" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@puniko</a> <a href="https://fosstodon.org/@linux_mclinuxface" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@linux_mclinuxface</a> Case in point, <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a> is an <a href="https://infosec.space/tags/AssholeLicense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AssholeLicense</a> even more than <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> because it's sole purpose is to commit <a href="https://infosec.space/tags/AssetDenial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AssetDenial</a> against <a href="https://infosec.space/tags/commercial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#commercial</a> users & <a href="https://infosec.space/tags/hosters" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hosters</a>.It's worse than <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv3</a> because that one is lunacy in terms of <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IP</a> and espechally <a href="https://infosec.space/tags/Patents" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Patents</a> because it's solely ideologically motivated, but yeah...IMHO everything under <a href="https://en.wikipedia.org/wiki/Server_Side_Public_License" rel="nofollow noopener noreferrer" target="_blank">SSPL</a> is <a href="https://infosec.space/tags/UnfreeSoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnfreeSoftware</a> in that it's <a href="https://infosec.space/tags/license" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#license</a> terms are worse than a <a href="https://infosec.space/tags/SourceAvailable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SourceAvailable</a> license as used by <a href="https://infosec.space/tags/Tarsnap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tarsnap</a> because they are at least honest about the why...I really hope not just <a href="https://infosec.space/tags/GAFAMs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GAFAMs</a> like <a href="https://infosec.space/tags/Amazon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Amazon</a> with <a href="https://infosec.space/tags/aws" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aws</a> forked the pre-<a href="https://infosec.space/tags/Enshittification" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Enshittification</a> versions under <a href="https://infosec.space/tags/BSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BSD</a> and start publishing and maintaining these.<a href="https://infosec.space/tags/Redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redis</a>, like <a href="https://infosec.space/tags/Elastic" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Elastic</a> and <a href="https://infosec.space/tags/MongoDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MongoDB</a> have chosen to kick everyone in the groin out of pettyness against commercial hosters, and I hope <a href="https://mastodon.social/@Mastodon" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Mastodon</a> & <a href="https://mastodon.social/@MastodonEngineering" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@MastodonEngineering</a> as well as <a href="https://mastodon.social/@Gargron" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Gargron</a> work hard to replace Redis with a real <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FLOSS</a> alternative like <a href="https://infosec.space/tags/RabbitMQ" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RabbitMQ</a> or even hetter, allow disabling a caching-DB in lieu of helping setup a <a href="https://infosec.space/tags/Ramdisk" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ramdisk</a> with a <a href="https://infosec.space/tags/PostgreSQL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PostgreSQL</a> cache-DB on it.

Recent searches

Search options

Administered by:

Server stats:

#tarsnap