Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
bolha.us is one of the many independent Mastodon servers you can use to participate in the fediverse.
We're a Brazilian IT Community. We love IT/DevOps/Cloud, but we also love to talk about life, the universe, and more. | Nós somos uma comunidade de TI Brasileira, gostamos de Dev/DevOps/Cloud e mais!

Administered by:

Server stats:

252
active users

bolha.us: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.6

#cacert

0 posts0 participants0 posts today
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.ar.al/@aral" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>aral</span></a></span> <span class="h-card" translate="no"><a href="https://ec.social-network.europa.eu/@EUCommission" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>EUCommission</span></a></span> <span class="h-card" translate="no"><a href="https://social.nlnet.nl/@nlnet" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>nlnet</span></a></span> call me weird but the developments of <span class="h-card" translate="no"><a href="https://infosec.exchange/@letsencrypt" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>letsencrypt</span></a></span> vs. <span class="h-card" translate="no"><a href="https://mastodon.social/@cacert" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>cacert</span></a></span> shows everything wrong with the way <a href="https://infosec.space/tags/SSL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SSL</span></a> works.</p><p>We would've had a superior alternative to <a href="https://infosec.space/tags/LetsEncrypt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LetsEncrypt</span></a> if <a href="https://infosec.space/tags/GAFAMs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GAFAMs</span></a> weren't able or even allowed to cockblock <a href="https://infosec.space/tags/CACert" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CACert</span></a> by refusing to import it's <em>ROOT-CA</em>, whilst every commercial <a href="https://infosec.space/tags/CA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CA</span></a> gets their keys imported, no matter how shit they are or that they are essentially a hostile state actor!</p>
Colin Cogle :verified:<p><span class="h-card" translate="no"><a href="https://gaygeek.social/@vlpatton" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>vlpatton</span></a></span> The classic method is a cryptoparty. Get a bunch of people in the same room with legal photo identification and their fingerprints, and go around the room checking everyone else’s ID. Then, go home and sign everyone’s keys. Send the signed key to the key owner. Import signed keys and collect signatures!</p><p>Key servers sharing signatures haven’t been a thing since the attacks years ago. Any modern keyserver will strip the signatures, so you’ll have to distribute your key with signatures some other way (WKD, DNS, a file on your web site, etc.).</p><p>CAcert will do PGP key endorsements if you get enough assurances on their platform. Everyone with a signed key has had two forms of ID checked by two people. However, their infrastructure can only work on old-school RSA keys right now (they’re working on modernizing).</p><p><a href="https://mastodon.colincogle.name/tags/PGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PGP</span></a> <a href="https://mastodon.colincogle.name/tags/GnuPG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GnuPG</span></a> <a href="https://mastodon.colincogle.name/tags/CAcert" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CAcert</span></a> <a href="https://mastodon.colincogle.name/tags/cryptoparty" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cryptoparty</span></a> <a href="https://mastodon.colincogle.name/tags/WebOfTrust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WebOfTrust</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://ciclista.social/@thomas" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>thomas</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@BjornW" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>BjornW</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@letsencrypt" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>letsencrypt</span></a></span> we had that one (minus LE involvement).</p><ul><li>It was called <span class="h-card" translate="no"><a href="https://mastodon.social/@cacert" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>cacert</span></a></span> / <a href="https://infosec.space/tags/CACert" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CACert</span></a>!</li></ul><p>It merely got cockblocked by <a href="https://infosec.space/tags/GAFAMs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GAFAMs</span></a> who refused to accept it as <a href="https://infosec.space/tags/CA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CA</span></a>...</p>
ExploreLive feeds
About