Shakedown Social

0 posts0 participants0 posts today

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>

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>

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>

Recent searches

Search options

Administered by:

Server stats:

#tarsnap