Mastodon 🐘

0 posts0 participants0 posts today

LisPiBut if all (most) CPUs are FGPAs, how does one bootstrap and assume the payload is not malicious? Programmers using discrete electronics and punched tape would be a human-auditable (if tedious) way of bootstrapping. A minimum viable target & programs for it to bootstrap everything else would be needed. I consider this analogous to the <a class="hashtag" href="https://udongein.xyz/tag/guix" rel="nofollow noopener noreferrer" target="_blank">#Guix</a> bootstrap seed endeavor. <a class="hashtag" href="https://udongein.xyz/tag/fpga" rel="nofollow noopener noreferrer" target="_blank">#FPGA</a> <a class="hashtag" href="https://udongein.xyz/tag/bootstrap" rel="nofollow noopener noreferrer" target="_blank">#Bootstrap</a> <a class="hashtag" href="https://udongein.xyz/tag/bootstrapping" rel="nofollow noopener noreferrer" target="_blank">#Bootstrapping</a> <a class="hashtag" href="https://udongein.xyz/tag/cpu" rel="nofollow noopener noreferrer" target="_blank">#CPU</a> <a class="hashtag" href="https://udongein.xyz/tag/hardware" rel="nofollow noopener noreferrer" target="_blank">#Hardware</a> <a class="hashtag" href="https://udongein.xyz/tag/security" rel="nofollow noopener noreferrer" target="_blank">#Security</a> <a class="hashtag" href="https://udongein.xyz/tag/auditability" rel="nofollow noopener noreferrer" target="_blank">#Auditability</a>

Kevin Karhan :verified:<a href="https://cosocial.ca/@virtuous_sloth" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@virtuous_sloth</a> <a href="https://beige.party/@TheBreadmonkey" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@TheBreadmonkey</a> I do agree on the fact that <a href="https://infosec.space/tags/auditability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#auditability</a> and <a href="https://infosec.space/tags/transparency" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#transparency</a> is important! <ul><li>I'll gladly migrate to a better option if there is one!</li></ul>

Kevin Karhan :verified:<a href="https://social.nitrokey.com/@nitrokey" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@nitrokey</a> <a href="https://infosec.space/tags/NOICE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NOICE</a>! After all, I'm a strong opponent of <a href="https://infosec.space/tags/blackbox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#blackbox</a>|es in terms of <a href="https://infosec.space/tags/ITsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ITsec</a> and <a href="https://infosec.space/tags/Encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Encryption</a> and I do think that <a href="https://infosec.space/tags/transparency" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#transparency</a> is necessary for real <a href="https://infosec.space/tags/auditability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#auditability</a>. <ul><li>Everything else is just <a href="https://infosec.space/tags/TrustMeBro" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TrustMeBro</a>-level of <a href="https://infosec.space/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> and I don't like that...</li></ul>

Kevin Karhan :verified:<a href="https://toot.io/@methuselah" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@methuselah</a> <a href="https://social.glitched.systems/@froge" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@froge</a> precisely...<ul><li>Same with like <a href="https://infosec.space/tags/IRC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IRC</a>: They run even on really old systems barely siphoning resources... </li></ul>To me <a href="https://infosec.space/tags/Matrix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Matrix</a> feels really undercooked and half-baked compared even to shitshows like <a href="https://infosec.space/tags/Slack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Slack</a> and <a href="https://infosec.space/tags/Discord" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Discord</a>... <ul><li>Whereas <a href="https://infosec.space/tags/Zulip" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Zulip</a> has proven itself as a good solution, which I'd rather shive behind a <a href="https://infosec.space/tags/VPN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VPN</a> to add <a href="https://infosec.space/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> since for <a href="https://infosec.space/tags/organization" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#organization</a>-based <a href="https://infosec.space/tags/chat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chat</a> infrastructure, one may have to face strict <a href="https://infosec.space/tags/logging" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#logging</a> and <a href="https://infosec.space/tags/auditability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#auditability</a> requirements (Don't let me get started on <a href="https://infosec.space/tags/GoBD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GoBD</a>)... </li></ul>OFC there is no "one solution fits all" because there are conflicting requirements for different use-cases...<ul><li>And my recommendations are based off given data like said requirements: Proper <a href="https://infosec.space/tags/E2EE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#E2EE</a> with self-custody of keys as well as per-session individual, non-persistent keys is inherently incompatible with mandatory <a href="https://infosec.space/tags/archival" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#archival</a> requirements in <a href="https://infosec.space/tags/businesses" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#businesses</a>...</li></ul>

Kevin Karhan :verified:<a href="https://hooves.social/@rayglittersoft" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@rayglittersoft</a> I mean, don't take every word of him at face value - he has some nuts loose...Personally, I don't think <a href="https://infosec.space/tags/Bitcoin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bitcoin</a> or <a href="https://infosec.space/tags/Ethereum" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ethereum</a> have a longterm future cuz they've got a very finite amount of coins and that makes them fall on their faces once the last has been mined.Needless to say that every big purchase may fall under KYC & AML and thus face the same scrutiny.Fortunately, <a href="https://infosec.space/tags/Monero" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Monero</a> does allow such <a href="https://infosec.space/tags/transparency" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#transparency</a> and <a href="https://infosec.space/tags/auditability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#auditability</a> whereever needed or desired (aka. <a href="https://infosec.space/tags/ViewKey" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ViewKey</a>) and the rest is just complying with <a href="https://infosec.space/tags/accounting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#accounting</a> and <a href="https://infosec.space/tags/bookkeeping" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bookkeeping</a> standards as relevant...

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>

Kevin Karhan :verified:<a href="https://wetdry.world/@esm" class="u-url mention">@esm</a> I digress:There are many good <a href="https://mstdn.social/tags/XMPP" class="mention hashtag" rel="tag">#XMPP</a>-Clients like <a href="https://mstdn.social/tags/Profanity" class="mention hashtag" rel="tag">#Profanity</a> (<a href="https://mstdn.social/tags/CLI" class="mention hashtag" rel="tag">#CLI</a>), <a href="https://mstdn.social/tags/monoclesChat" class="mention hashtag" rel="tag">#monoclesChat</a> (<a href="https://mstdn.social/tags/Android" class="mention hashtag" rel="tag">#Android</a>) and <a href="https://mstdn.social/tags/Gajim" class="mention hashtag" rel="tag">#Gajim</a> (<a href="https://mstdn.social/tags/Desktop" class="mention hashtag" rel="tag">#Desktop</a>-<a href="https://mstdn.social/tags/GUI" class="mention hashtag" rel="tag">#GUI</a>)...And in terms of <a href="https://mstdn.social/tags/Organizations" class="mention hashtag" rel="tag">#Organizations</a> that require <a href="https://mstdn.social/tags/Auditability" class="mention hashtag" rel="tag">#Auditability</a>, the only good option I found is <a href="https://mstdn.social/tags/Zulip" class="mention hashtag" rel="tag">#Zulip</a>, which has excellent <a href="https://mstdn.social/tags/Clients" class="mention hashtag" rel="tag">#Clients</a> for <a href="https://mstdn.social/tags/Desktop" class="mention hashtag" rel="tag">#Desktop</a> and <a href="https://mstdn.social/tags/Terminal" class="mention hashtag" rel="tag">#Terminal</a> as well - tho sadly the latter one is written in <a href="https://mstdn.social/tags/Python" class="mention hashtag" rel="tag">#Python</a> and not like a static binary... <a href="https://github.com/zulip/zulip-terminal" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://github.com/zulip/zulip-terminal</a>

Cory DoctorowThus, "open AI" is best understood as "as free product development" for large, well-capitalized AI firms, done by tinkerers who will not be able to escape these giants' proprietary compute silos and opaque training corpuses, and whose work product is guaranteed to be compatible with the giants' own systems.The instrumental story about the virtues of "open" often invoke <a href="https://mamot.fr/tags/auditability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#auditability</a>: the fact that anyone can look at the source code makes it easier for bugs to be identified. 35/

Nuno Facha :rubberduck: 🇵🇹<a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a> community, need suggestions :eyes_happy:At work there are some generic emails like general@company.com, billing@company.com and so on, This are all on <a href="https://infosec.exchange/tags/Google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Google</a> <a href="https://infosec.exchange/tags/Gsuite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gsuite</a> All have secure passwords and <a href="https://infosec.exchange/tags/twofactorauthentication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#twofactorauthentication</a> shared via <a href="https://infosec.exchange/tags/bitwarden" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bitwarden</a> with people that use themI still don't like the idea of multiple people accessing the account and reducing the <a href="https://infosec.exchange/tags/auditability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#auditability</a> of who did what, for inbound email I can setup forwarding rules, but for them to send out email they still need to access the actual account, any better way to do it then this?

Märt PõderThis individual vote verification tool for ongoing parliamentary elections in Estonia with its e-voting found its way into my digital democracy toolbox. We basically have individual verification for 30 minutes after submitting the ballot, but this tool lets you download the cryptogram, decrypt it and keep it for memory or later use. <a href="https://github.com/infoaed/kryptogramm" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://github.com/infoaed/kryptogramm</a> <a href="https://mstdn.social/tags/evoting" class="mention hashtag" rel="tag">#evoting</a> <a href="https://mstdn.social/tags/verification" class="mention hashtag" rel="tag">#verification</a> <a href="https://mstdn.social/tags/auditability" class="mention hashtag" rel="tag">#auditability</a> <a href="https://mstdn.social/tags/rk2023" class="mention hashtag" rel="tag">#rk2023</a>

Recent searches

Search options

Administered by:

Server stats:

#auditability