#reproduceablebuilds

Kevin Karhan :verified:<a href="https://101010.pl/@centopus" class="u-url mention" rel="nofollow noopener" target="_blank">@centopus</a> well, feel free to port <a href="https://social.treehouse.systems/@AsahiLinux" class="u-url mention" rel="nofollow noopener" target="_blank">@AsahiLinux</a> 's patches to <a href="https://infosec.space/tags/C" class="mention hashtag" rel="nofollow noopener" target="_blank">#C</a>.As for <a href="https://infosec.space/tags/Rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rust</a>, IDGAF in general.<ul><li>All I care about are easy <a href="https://infosec.space/tags/reproduceableBuilds" class="mention hashtag" rel="nofollow noopener" target="_blank">#reproduceableBuilds</a> for <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a> ...</li></ul>

Kevin Karhan :verified:<a href="https://udongein.xyz/users/lispi314" class="u-url mention" rel="nofollow noopener" target="_blank">@lispi314</a> <a href="https://mk.absturztau.be/@enigmatico" class="u-url mention" rel="nofollow noopener" target="_blank">@enigmatico</a> <a href="https://transfem.social/@bunnybeam" class="u-url mention" rel="nofollow noopener" target="_blank">@bunnybeam</a> <a href="https://ublog.kimapr.net/users/kimapr" class="u-url mention" rel="nofollow noopener" target="_blank">@kimapr</a> nodds in agreement<ul><li>I think having a proper <a href="https://infosec.space/tags/API" class="mention hashtag" rel="nofollow noopener" target="_blank">#API</a> is a way to facilitate that, cuz worst-case one just slaps together some <a href="https://infosec.space/tags/aliases" class="mention hashtag" rel="nofollow noopener" target="_blank">#aliases</a> in <a href="https://infosec.space/tags/bash" class="mention hashtag" rel="nofollow noopener" target="_blank">#bash</a>, <a href="https://infosec.space/tags/fish" class="mention hashtag" rel="nofollow noopener" target="_blank">#fish</a>, <a href="https://infosec.space/tags/zsh" class="mention hashtag" rel="nofollow noopener" target="_blank">#zsh</a> or whatever <a href="https://infosec.space/tags/shell" class="mention hashtag" rel="nofollow noopener" target="_blank">#shell</a> and just uses <a href="https://infosec.space/tags/curl" class="mention hashtag" rel="nofollow noopener" target="_blank">#curl</a> to query stuff manually as this solves the whole <a href="https://infosec.space/tags/WebApp" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebApp</a> - issue.</li></ul>And I do prefer <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FLOSS</a> as it works fine for an ever increasing audience!<ul><li>Even if we choose to point at bad <a href="https://infosec.space/tags/UX" class="mention hashtag" rel="nofollow noopener" target="_blank">#UX</a> / <a href="https://infosec.space/tags/UI" class="mention hashtag" rel="nofollow noopener" target="_blank">#UI</a> combos like <a href="https://infosec.space/tags/GnuPG" class="mention hashtag" rel="nofollow noopener" target="_blank">#GnuPG</a>, we've to also acknowledge better existing alternatives like <a href="https://infosec.space/tags/enc" class="mention hashtag" rel="nofollow noopener" target="_blank">#enc</a> that <a href="https://github.com/life4/enc" rel="nofollow noopener" target="_blank">just work</a>!</li></ul>Personally, I think that everything people are expected to use if not forced to use should be <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> as licensed in a <a href="https://infosec.space/tags/OSI" class="mention hashtag" rel="nofollow noopener" target="_blank">#OSI</a> accredited license and be released with <a href="https://infosec.space/tags/SourceCode" class="mention hashtag" rel="nofollow noopener" target="_blank">#SourceCode</a> and <a href="https://infosec.space/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a> to make <a href="https://infosec.space/tags/reproduceableBuilds" class="mention hashtag" rel="nofollow noopener" target="_blank">#reproduceableBuilds</a> and thus facilitate <a href="https://infosec.space/tags/audits" class="mention hashtag" rel="nofollow noopener" target="_blank">#audits</a> by truly independent parties...<ul><li>And if that's not possible any requirement to using said things should be outlawed no matter the context! </li></ul>A unsarcastically good example is <a href="https://infosec.space/tags/S3" class="mention hashtag" rel="nofollow noopener" target="_blank">#S3</a>, even tho I hate <a href="https://infosec.space/tags/amazon" class="mention hashtag" rel="nofollow noopener" target="_blank">#amazon</a>, they wanted <a href="https://infosec.space/tags/developers" class="mention hashtag" rel="nofollow noopener" target="_blank">#developers</a> to integrate their <a href="https://infosec.space/tags/ObjectStorage" class="mention hashtag" rel="nofollow noopener" target="_blank">#ObjectStorage</a> which necessitated an <a href="https://infosec.space/tags/open" class="mention hashtag" rel="nofollow noopener" target="_blank">#open</a> source'd API to the point that it's <a href="https://infosec.space/tags/backend" class="mention hashtag" rel="nofollow noopener" target="_blank">#backend</a> is inherently reproduceable, and now every halfassing <a href="https://infosec.space/tags/Webhoster" class="mention hashtag" rel="nofollow noopener" target="_blank">#Webhoster</a> offers S3 <a href="https://infosec.space/tags/storage" class="mention hashtag" rel="nofollow noopener" target="_blank">#storage</a>, sometimes with bit & second-precise billing.

Kevin Karhan :verified:<a href="https://rubber.social/@dragonarchitect" class="u-url mention" rel="nofollow noopener" target="_blank">@dragonarchitect</a> <a href="https://meemu.org/@Siph" class="u-url mention" rel="nofollow noopener" target="_blank">@Siph</a> also just using <a href="https://infosec.space/tags/Rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rust</a> isn't automatically make shit good.<ul><li>And I doubt it can be as compact and efficient as <a href="https://infosec.space/tags/C" class="mention hashtag" rel="nofollow noopener" target="_blank">#C</a> when it comes to a minimalist <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> distro...</li></ul>But then again I care more about <a href="https://infosec.space/tags/ReproduceableBuilds" class="mention hashtag" rel="nofollow noopener" target="_blank">#ReproduceableBuilds</a> and <a href="https://infosec.space/tags/Maintainablility" class="mention hashtag" rel="nofollow noopener" target="_blank">#Maintainablility</a> than the languague.

Kevin Karhan :verified:<a href="https://hachyderm.io/@lucasmz" class="u-url mention" rel="nofollow noopener" target="_blank">@lucasmz</a> <a href="https://front-end.social/@estelle" class="u-url mention" rel="nofollow noopener" target="_blank">@estelle</a> It is proprietary in that to this day there are neither <a href="https://infosec.space/tags/ReproduceableBuilds" class="mention hashtag" rel="nofollow noopener" target="_blank">#ReproduceableBuilds</a> nor is it <a href="https://infosec.space/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosting</a>-capable... Which makes <a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@signalapp</a> a <a href="https://infosec.space/tags/liability" class="mention hashtag" rel="nofollow noopener" target="_blank">#liability</a> and <a href="https://infosec.space/tags/incapable" class="mention hashtag" rel="nofollow noopener" target="_blank">#incapable</a> of complying with <a href="https://infosec.space/tags/GDPR" class="mention hashtag" rel="nofollow noopener" target="_blank">#GDPR</a> & <a href="https://infosec.space/tags/BDSG" class="mention hashtag" rel="nofollow noopener" target="_blank">#BDSG</a> due to <a href="https://infosec.space/tags/CloudAct" class="mention hashtag" rel="nofollow noopener" target="_blank">#CloudAct</a> making that impossible!

Kevin Karhan :verified:<a href="https://girlboss.gaslight.love/users/eemmaa" class="u-url mention" rel="nofollow noopener" target="_blank">@eemmaa</a> personally, I do intent to copy that with <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a> because <a href="https://infosec.space/tags/ReproduceableBuilds" class="mention hashtag" rel="nofollow noopener" target="_blank">#ReproduceableBuilds</a> are as much of an important step in having an <a href="https://infosec.space/tags/auditable" class="mention hashtag" rel="nofollow noopener" target="_blank">#auditable</a> system as having unrestricted (<a href="https://infosec.space/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> licensed!) <a href="https://infosec.space/tags/sourcecode" class="mention hashtag" rel="nofollow noopener" target="_blank">#sourcecode</a> availability & access...

Kevin Karhan :verified:<a href="https://freiburg.social/@ditol" class="u-url mention" rel="nofollow noopener" target="_blank">@ditol</a> <a href="https://mastodon.world/@samueljohn" class="u-url mention" rel="nofollow noopener" target="_blank">@samueljohn</a> <a href="https://23.social/@linuzifer" class="u-url mention" rel="nofollow noopener" target="_blank">@linuzifer</a> THIS is where I disagree...You may think it's elitist, but if people are too lazy to learn even fundamentals like how to use <a href="https://infosec.space/tags/Tails" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tails</a> then maybe they should just not do <a href="https://infosec.space/tags/tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#tech</a> at all?<ul><li>Like: We expect people to show at the every least theoretical proficiency in terms of <a href="https://infosec.space/tags/TrafficCode" class="mention hashtag" rel="nofollow noopener" target="_blank">#TrafficCode</a> and <a href="https://infosec.space/tags/VehicleSafety" class="mention hashtag" rel="nofollow noopener" target="_blank">#VehicleSafety</a> in +every juristiction I'm aware of* and literally mandated <a href="https://infosec.space/tags/DrivingLicense" class="mention hashtag" rel="nofollow noopener" target="_blank">#DrivingLicense</a>|s for that reason.</li></ul>I'll gladly teach <a href="https://infosec.space/tags/TechIlliterates" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechIlliterates</a> but I won't waste my time on <a href="https://infosec.space/@kkarhan/113344834546549105" rel="nofollow noopener" target="_blank">people that spread disinfo</a>...It's 2024: <a href="https://venera.social/profile/tails_live" class="u-url mention" rel="nofollow noopener" target="_blank">@tails_live</a> / <a href="https://fosstodon.org/@tails" class="u-url mention" rel="nofollow noopener" target="_blank">@tails</a> has been out for over a decade and there are a shitload of guides ranging from written documentation to Zoomer-friendly TikTok-Style shorts on how to get started.<ul><li>I don't expect people to do <a href="https://infosec.space/tags/airgapped" class="mention hashtag" rel="nofollow noopener" target="_blank">#airgapped</a> <a href="https://www.youtube.com/watch?v=vdab4T_CoN8" rel="nofollow noopener" target="_blank">pffline-PGP</a> but with <a href="https://mastodon.online/@thunderbird" class="u-url mention" rel="nofollow noopener" target="_blank">@thunderbird</a> including <a href="https://infosec.space/tags/Enigmail" class="mention hashtag" rel="nofollow noopener" target="_blank">#Enigmail</a> and not requiring any external dependencies like the god-awful <a href="https://infosec.space/tags/GPG4Win" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPG4Win</a> stuff's easier than ever.</li><li>Same with <a href="https://infosec.space/tags/mobile" class="mention hashtag" rel="nofollow noopener" target="_blank">#mobile</a>: <a href="https://infosec.space/tags/Appls" class="mention hashtag" rel="nofollow noopener" target="_blank">#Appls</a> like <a href="https://monocles.social/@monocles" class="u-url mention" rel="nofollow noopener" target="_blank">@monocles</a> / <a href="https://infosec.space/tags/monoclesChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#monoclesChat</a> are so easy, I've been able to onboard literal tech-illiterates remotely with few steps and <a href="https://docs.monocles.eu/apps/chat.app/" rel="nofollow noopener" target="_blank">simple instructions</a>. </li></ul>FOR THE LAST TIME: *STOP MAKING EXCUSES TO JUSTIFY ESCALATING COMMITMENT TO EVIDENTLY BAD SOLUTIONS!"<ul><li>Cuz <a href="https://web.archive.org/web/20240000000000*/https://twitter.com/thegrugq/status/1085614812581715968" rel="nofollow noopener" target="_blank">when push comes to shove</a> <a href="https://mastodon.world/@Mer__edith" class="u-url mention" rel="nofollow noopener" target="_blank">@Mer__edith</a> herself would introduce a <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Govware</a> <a href="https://infosec.space/tags/backdoor" class="mention hashtag" rel="nofollow noopener" target="_blank">#backdoor</a> into <a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@signalapp</a> when faced with indefinite jailtime...</li></ul>Whereas with <a href="https://infosec.space/tags/SelfCustody" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfCustody</a> of all the keys as well as <a href="https://infosec.space/tags/ReproduceableBuilds" class="mention hashtag" rel="nofollow noopener" target="_blank">#ReproduceableBuilds</a> and real <a href="https://infosec.space/tags/decentralization" class="mention hashtag" rel="nofollow noopener" target="_blank">#decentralization</a>, this would be evidently impossible even if all the devs wanted to comply honestly and not just because they could be held at gunpoint.<ul><li><a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signal</a> is not your friend. It's merely a tax-exempt "non-profit" corporation, and corporations are explicitly nobodys friend - espechally when they demand <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener" target="_blank">#PII</a> like <a href="https://infosec.space/@kkarhan/111968251463697943" rel="nofollow noopener" target="_blank">phone numbers</a> for useage.</li></ul>Compare that to <a href="https://infosec.space/tags/monocles" class="mention hashtag" rel="nofollow noopener" target="_blank">#monocles</a> where you do pay like €2 p.m. but in return get <a href="https://infosec.space/tags/standard" class="mention hashtag" rel="nofollow noopener" target="_blank">#standard</a> <a href="https://infosec.space/tags/protocols" class="mention hashtag" rel="nofollow noopener" target="_blank">#protocols</a> like <a href="https://infosec.space/tags/IMAP" class="mention hashtag" rel="nofollow noopener" target="_blank">#IMAP</a>, <a href="https://infosec.space/tags/SMTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#SMTP</a> & <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#XMPP</a> and <a href="https://monocles.eu/more/#payment-section" rel="nofollow noopener" target="_blank">can pay anonymously</a> and not have to provide any PII whatsoever!<ul><li>And unlike <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signal</a> they ain't dependent on <a href="https://infosec.space/tags/VC" class="mention hashtag" rel="nofollow noopener" target="_blank">#VC</a> funding and <a href="https://infosec.space/tags/grant" class="mention hashtag" rel="nofollow noopener" target="_blank">#grant</a> money to keep the lights on.</li></ul>Make of that what you will, but just like allowing flatearthers to roam freely without caretaker supervision doesn't make the world less round, so won't the facts change about <a href="https://infosec.space/tags/ITsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#ITsec</a>, <a href="https://infosec.space/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoSec</a>, <a href="https://infosec.space/tags/OpSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpSec</a> & <a href="https://infosec.space/tags/ComSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#ComSec</a>. <ul><li>The only reason Signal is still online and not <a href="https://infosec.space/tags/pwned" class="mention hashtag" rel="nofollow noopener" target="_blank">#pwned</a> like <a href="https://infosec.space/tags/EncroChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#EncroChat</a> is because it's either a Sting op like <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> or they have already backdoored their <a href="https://infosec.space/tags/backend" class="mention hashtag" rel="nofollow noopener" target="_blank">#backend</a> so hard that all their <a href="https://infosec.space/tags/marketing" class="mention hashtag" rel="nofollow noopener" target="_blank">#marketing</a> is just <a href="https://infosec.space/tags/lies" class="mention hashtag" rel="nofollow noopener" target="_blank">#lies</a> like <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</a>... </li></ul>Because all <a href="https://infosec.space/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a>, <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleVendor</a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleProvider</a> solutions are bad, and if they don't even allow for <a href="https://infosec.space/tags/SelfCustody" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfCustody</a> then they are just a <a href="https://infosec.space/tags/grift" class="mention hashtag" rel="nofollow noopener" target="_blank">#grift</a> to <a href="https://infosec.space/tags/scam" class="mention hashtag" rel="nofollow noopener" target="_blank">#scam</a> tech-illiterates that don't know and/or don't care! <a href="https://infosec.space/tags/thxbye" class="mention hashtag" rel="nofollow noopener" target="_blank">#thxbye</a> <a href="https://infosec.space/tags/EOD" class="mention hashtag" rel="nofollow noopener" target="_blank">#EOD</a>

Kevin Karhan :verified:<a href="https://mstdn.io/@renan" class="u-url mention" rel="nofollow noopener" target="_blank">@renan</a> nodds in agreementTho <a href="https://infosec.space/tags/SimpleX" class="mention hashtag" rel="nofollow noopener" target="_blank">#SimpleX</a>, like <a href="https://infosec.space/tags/Threema" class="mention hashtag" rel="nofollow noopener" target="_blank">#Threema</a>, is also a <a href="https://infosec.space/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a>, <a href="https://infosec.space/tags/proprietary" class="mention hashtag" rel="nofollow noopener" target="_blank">#proprietary</a>, <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleVendor</a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleProvider</a> solution with neither <a href="https://infosec.space/tags/SelfCustody" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfCustody</a> of keys nor any means to <a href="https://infosec.space/tags/SelfHost" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHost</a> and have <a href="https://infosec.space/tags/reproduceableBuilds" class="mention hashtag" rel="nofollow noopener" target="_blank">#reproduceableBuilds</a>.

Kevin Karhan :verified:<a href="https://infosec.exchange/@ravirockks" class="u-url mention" rel="nofollow noopener" target="_blank">@ravirockks</a> Needless to say that only <a href="https://mstdn.social/tags/transparency" class="mention hashtag" rel="nofollow noopener" target="_blank">#transparency</a> with <a href="https://mstdn.social/tags/ReproduceableBuilds" class="mention hashtag" rel="nofollow noopener" target="_blank">#ReproduceableBuilds</a> can enshure the <a href="https://mstdn.social/tags/SourceCode" class="mention hashtag" rel="nofollow noopener" target="_blank">#SourceCode</a> is related to the <a href="https://mstdn.social/tags/binary" class="mention hashtag" rel="nofollow noopener" target="_blank">#binary</a> released.And being able to audit oneself or choose any auditor of choice to do so is also critical to the whole <a href="https://mstdn.social/tags/ITsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#ITsec</a> aspect of it.You don't want people to be able to "pull rank" but instead you want critical code to be looked at with as many eyes as possible.

Recent searches

Search options

Administered by:

Server stats:

#reproduceablebuilds