James Fine Art (.ie)<p>G. <br>Piano Fire is a watercolour painting, initially created to have colour represent the emotion of piano music. As the flow and colour could be interpreted as flames, it was named Piano Fire.</p><p>[ Prints : <a href="https://james-mccormack.pixels.com/featured/piano-fire-james-mccormack.html?utm_source=mastodon&utm_medium=social" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">james-mccormack.pixels.com/fea</span><span class="invisible">tured/piano-fire-james-mccormack.html?utm_source=mastodon&utm_medium=social</span></a> ]</p><p><a href="https://mastodon.ie/tags/pianofire" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pianofire</span></a> <a href="https://mastodon.ie/tags/music" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>music</span></a> <a href="https://mastodon.ie/tags/key" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>key</span></a> <a href="https://mastodon.ie/tags/piano" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>piano</span></a> <a href="https://mastodon.ie/tags/fire" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fire</span></a> <a href="https://mastodon.ie/tags/pianoforte" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pianoforte</span></a> <a href="https://mastodon.ie/tags/flames" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>flames</span></a> <a href="https://mastodon.ie/tags/music" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>music</span></a> <a href="https://mastodon.ie/tags/notes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>notes</span></a> <a href="https://mastodon.ie/tags/keys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>keys</span></a> <a href="https://mastodon.ie/tags/ivories" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ivories</span></a> <a href="https://mastodon.ie/tags/buyintoart" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>buyintoart</span></a> <a href="https://mastodon.ie/tags/MastoArt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MastoArt</span></a> <a href="https://mastodon.ie/tags/MastoDaoine" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MastoDaoine</span></a> <a href="https://mastodon.ie/tags/FediGiftShop" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FediGiftShop</span></a></p>
101010.pl is one of the many independent Mastodon servers you can use to participate in the fediverse.
101010.pl czyli najstarszy polski serwer Mastodon. Posiadamy wpisy do 2048 znaków.
Administered by:
Server stats:
517active users
101010.pl: About · Status · Profiles directory · Privacy policy
Mastodon: About · Get the app · Keyboard shortcuts · View source code · v4.4.0-beta.1
#keys
1 post · 1 participant · 0 posts today
IT News<p>Building a Cyberpunk Modular Keyboard - Perhaps you have a tilt towards glowing cyberpunk peripherals. Perhaps you’ve been... - <a href="https://hackaday.com/2025/06/07/building-a-cyberpunk-modular-keyboard/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">hackaday.com/2025/06/07/buildi</span><span class="invisible">ng-a-cyberpunk-modular-keyboard/</span></a> <a href="https://schleuss.online/tags/peripheralshacks" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>peripheralshacks</span></a> <a href="https://schleuss.online/tags/splitkeyboard" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>splitkeyboard</span></a> <a href="https://schleuss.online/tags/keyboard" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>keyboard</span></a> <a href="https://schleuss.online/tags/keys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>keys</span></a></p>
sheislaurence<p>🧵 4/4: The <a href="https://mastodon.social/tags/Palestine" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Palestine</span></a> Solidarity <a href="https://mastodon.social/tags/demonstration" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>demonstration</span></a> in <a href="https://mastodon.social/tags/London" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>London</span></a> today marked 77 years since the <a href="https://mastodon.social/tags/Nakba" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Nakba</span></a> or 'great catastrophe' that saw 750k <a href="https://mastodon.social/tags/Palestinians" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Palestinians</span></a> forcibly displaced from their homes & land. Many Palestinians carry <a href="https://mastodon.social/tags/keys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>keys</span></a> of their ancestral homes, or symbolic keys, dubbed 'key of return'. <br>Seeing 'architects for Gaza' against the backdrop of the <a href="https://mastodon.social/tags/British" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>British</span></a> Parliament made the contrast with the scale of destruction in <a href="https://mastodon.social/tags/Gaza" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Gaza</span></a> all the more obvious.</p>
TechHelpKB.com 📚<p>Millions of RSA encryption keys contain major flaws, making them vulnerable to attack. New research found around 1 in 172 of all certificates found online are susceptible to compromise through a mathematical attack.</p><p><a href="https://mastodon.social/tags/rsa" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rsa</span></a> <a href="https://mastodon.social/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>encryption</span></a> <a href="https://mastodon.social/tags/keys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>keys</span></a> <a href="https://mastodon.social/tags/attack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>attack</span></a> <br><a href="https://www.itpro.com/security/rsa-encryption-keys-vulnerability" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">itpro.com/security/rsa-encrypt</span><span class="invisible">ion-keys-vulnerability</span></a></p>
Mad A. Argon :qurio:<p>Huh... maybe someone should try to stop me interpreting <a href="https://is-a.cat/tags/ssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ssh</span></a> <a href="https://is-a.cat/tags/keys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>keys</span></a> like star <a href="https://is-a.cat/tags/constellations" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>constellations</span></a> and <a href="https://is-a.cat/tags/drawing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>drawing</span></a> creatures and objects of these? :blobcatjoy: </p><p>Currently in intensive testing phase I create and destroy many VMs at work and I have almost infinite source of inspiration... :blobdevilsmile:</p>
Jakub Steiner ⭐<p>An absolute didactic marvel of a video on basic music theory. </p><p><a href="https://youtu.be/NgW3zUWVWnI?si=6hcp-6VL-1q9tUee" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">youtu.be/NgW3zUWVWnI?si=6hcp-6</span><span class="invisible">VL-1q9tUee</span></a></p><p><a href="https://mastodon.social/tags/music" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>music</span></a> <a href="https://mastodon.social/tags/ratios" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ratios</span></a> <a href="https://mastodon.social/tags/intervals" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>intervals</span></a> <a href="https://mastodon.social/tags/keys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>keys</span></a> <a href="https://mastodon.social/tags/scales" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>scales</span></a> <a href="https://mastodon.social/tags/theory" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>theory</span></a></p>
Jim "Ham on a Bike"<p>I'm a BIG Fan of Leg Straps for CW <a href="https://mastodon.radio/tags/MorseCode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MorseCode</span></a> <a href="https://mastodon.radio/tags/paddles" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>paddles</span></a> & <a href="https://mastodon.radio/tags/Keys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Keys</span></a>. Jonathan <a href="https://mastodon.radio/tags/KM4CFT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>KM4CFT</span></a> has come up with one that is perfect for my Mini <a href="https://mastodon.radio/tags/Putikeeg" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Putikeeg</span></a> <a href="https://mastodon.radio/tags/Straightkey" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Straightkey</span></a> <a href="https://mastodon.radio/tags/AmateurRadio" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AmateurRadio</span></a> <a href="https://mastodon.radio/tags/Hamradio" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Hamradio</span></a> <a href="https://mastodon.radio/tags/POTA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>POTA</span></a> <a href="https://mastodon.radio/tags/SOTA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SOTA</span></a> </p><p><a href="https://qrper.com/2025/02/new-antenna-and-leg-strap-from-km4cft/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">qrper.com/2025/02/new-antenna-</span><span class="invisible">and-leg-strap-from-km4cft/</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://chaos.social/@ck" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ck</span></a></span> <span class="h-card" translate="no"><a href="https://soc.hardwarepunk.de/profile/sven222" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>sven222</span></a></span> <span class="h-card" translate="no"><a href="https://social.tchncs.de/@kuketzblog" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>kuketzblog</span></a></span> problem is <span class="h-card" translate="no"><a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>signalapp</span></a></span> is a <a href="https://infosec.space/tags/Centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Centralized</span></a>, <a href="https://infosec.space/tags/Proprietary" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Proprietary</span></a>, <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SingleVendor</span></a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SingleProvider</span></a> solution that falls under <a href="https://infosec.space/tags/CloudAct" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CloudAct</span></a> and demands <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PII</span></a> in the form of <a href="https://infosec.space/tags/PhoneNumbers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PhoneNumbers</span></a>.</p><ul><li>So even if we'd agree that <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XMPP</span></a>+<a href="https://infosec.space/tags/OMEMO" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OMEMO</span></a> as implememented in <span class="h-card" translate="no"><a href="https://monocles.social/@monocles" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>monocles</span></a></span> / <a href="https://infosec.space/tags/monoclesChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>monoclesChat</span></a> & <span class="h-card" translate="no"><a href="https://fosstodon.org/@gajim" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>gajim</span></a></span> / <a href="https://infosec.space/tags/gajim" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gajim</span></a> is bad (and <a href="https://infosec.space/tags/PGP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PGP</span></a>/MIME over XMPP isn't good either) there are still better options than <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Signal</span></a> (i.e. <span class="h-card" translate="no"><a href="https://chaos.social/@delta" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>delta</span></a></span> / <a href="https://infosec.space/tags/deltaChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>deltaChat</span></a> which uses PGP/MIME & <a href="https://infosec.space/tags/IMAP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IMAP</span></a>-Push aka. <a href="https://infosec.space/tags/eMail" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>eMail</span></a>) that don't require a <a href="https://infosec.space/tags/PhoneNumber" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PhoneNumber</span></a>, allow <a href="https://infosec.space/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SelfHosting</span></a> and are truly <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a> with an <a href="https://infosec.space/tags/OpebStandard" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpebStandard</span></a> that allows for <em>real <a href="https://infosec.space/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>E2EE</span></a></em> as in <a href="https://infosec.space/tags/SelfCustody" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SelfCustody</span></a> of all the <a href="https://infosec.space/tags/Keys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Keys</span></a>.</li></ul><p>Cuz all the <a href="https://infosec.space/tags/advertising" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>advertising</span></a> of Signal is close to <a href="https://infosec.space/tags/TrustMeBro" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TrustMeBro</span></a> and I'd not trust in <span class="h-card" translate="no"><a href="https://mastodon.world/@Mer__edith" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Mer__edith</span></a></span> to <a href="https://web.archive.org/web/20210606070919/twitter.com/thegrugq/status/1085614812581715968" rel="nofollow noopener" target="_blank">risk jail for users</a>!</p><ul><li>But you do you... </li></ul><p><a href="https://infosec.space/tags/ITsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ITsec</span></a> <a href="https://infosec.space/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>InfoSec</span></a> <a href="https://infosec.space/tags/OpSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpSec</span></a> <a href="https://infosec.space/tags/ComSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ComSec</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.scot/@moh_kohn" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>moh_kohn</span></a></span> except <span class="h-card" translate="no"><a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>signalapp</span></a></span> too is a <a href="https://infosec.space/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>centralized</span></a>, <a href="https://infosec.space/tags/SingleVendir" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SingleVendir</span></a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SingleProvider</span></a> solution that fully falls under <a href="https://infosec.space/tags/CliudAct" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CliudAct</span></a> and thus <em>CANNOT</em> comply with <a href="https://infosec.space/tags/GDPR" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GDPR</span></a> & <a href="https://infosec.space/tags/BDSG" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BDSG</span></a> <em>as a matter of principle</em> since this <em>digital rquivalent of <a href="https://infosec.space/tags/ExtraordinaryRendition" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ExtraordinaryRendition</span></a></em> is inherently incompatible!</p><ul><li>Use <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XMPP</span></a>+<a href="https://infosec.space/tags/OMEMO" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OMEMO</span></a> & <a href="https://infosec.space/tags/PGP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PGP</span></a>/MIME with <a href="https://infosec.space/tags/SelfCustody" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SelfCustody</span></a> if all the <a href="https://infosec.space/tags/Keys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Keys</span></a> for <em>real</em> <a href="https://infosec.space/tags/EndToEndEncryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EndToEndEncryption</span></a> that doesn't rely on a <a href="https://infosec.space/tags/VC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VC</span></a> <a href="https://infosec.space/tags/MoneyBurningParty" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MoneyBurningParty</span></a>. </li></ul><p><span class="h-card" translate="no"><a href="https://monocles.social/@monocles" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>monocles</span></a></span> / <a href="https://infosec.space/tags/monoclesChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>monoclesChat</span></a>, <span class="h-card" translate="no"><a href="https://fosstodon.org/@gajim" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>gajim</span></a></span> / <a href="https://infosec.space/tags/gajim" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gajim</span></a> & <span class="h-card" translate="no"><a href="https://chaos.social/@delta" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>delta</span></a></span> / <a href="https://infosec.space/tags/deltaChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>deltaChat</span></a>, <span class="h-card" translate="no"><a href="https://mastodon.online/@thunderbird" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>thunderbird</span></a></span> / <a href="https://infosec.space/tags/Thunderbird" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Thunderbird</span></a> do support that!</p>
F3715H<p><span class="h-card" translate="no"><a href="https://mastodon.social/@MartinaNeumayer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>MartinaNeumayer</span></a></span> <span class="h-card" translate="no"><a href="https://net4sw.com/@VixenBlu" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>VixenBlu</span></a></span> <span class="h-card" translate="no"><a href="https://spookygirl.boo/@thelusciouslibra" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>thelusciouslibra</span></a></span> I do recommend people to encrypt their emails and always exercise <a href="https://noods.fun/tags/SelfCustody" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SelfCustody</span></a> of all the <a href="https://noods.fun/tags/Keys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Keys</span></a>... </p><p>- Never ever rely on a provider to safeguard you or any other users; even if we all do nothing wrong!</p><p><a href="https://web.archive.org/web/20240000000000*/https://twitter.com/thegrugq/status/1085614812581715968" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">web.archive.org/web/2024000000</span><span class="invisible">0000*/https://twitter.com/thegrugq/status/1085614812581715968</span></a></p>
xoron :verified:<p>id like to share some details about how my app works so you can discover/give me feedback on my app. id like to have wording in my app to say something like "most secure chat app in the world"... i probably cant do that because it doesnt qualify.</p><p><a href="https://github.com/positive-intentions/chat" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/positive-intentions</span><span class="invisible">/chat</span></a></p><p><a href="https://positive-intentions.com/blog/introducing-decentralized-chat" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">positive-intentions.com/blog/i</span><span class="invisible">ntroducing-decentralized-chat</span></a></p><p>im not an expert on <a href="https://infosec.exchange/tags/cyberSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cyberSecurity</span></a>. im sure there are many gaps in my knowlege in this domain.</p><p>using <a href="https://infosec.exchange/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>javascript</span></a>, i initially created a fairly basic <a href="https://infosec.exchange/tags/chatApp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chatApp</span></a> using using <a href="https://infosec.exchange/tags/peerjs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>peerjs</span></a> to create <a href="https://infosec.exchange/tags/encrypted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>encrypted</span></a> <a href="https://infosec.exchange/tags/webrtc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webrtc</span></a> <a href="https://infosec.exchange/tags/connections" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>connections</span></a>. this was then easily enhanced by exchanging additional <a href="https://infosec.exchange/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>encryption</span></a> <a href="https://infosec.exchange/tags/keys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>keys</span></a> from <a href="https://infosec.exchange/tags/cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cryptography</span></a> functions built into browsers (<a href="https://infosec.exchange/tags/webcrypto" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webcrypto</span></a> api) to add a redundent layer of encryption. a <a href="https://infosec.exchange/tags/diffieHelman" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>diffieHelman</span></a> key <a href="https://infosec.exchange/tags/exchange" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>exchange</span></a> is done over <a href="https://infosec.exchange/tags/webrtc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webrtc</span></a> (which can be considered <a href="https://infosec.exchange/tags/secure" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>secure</span></a> when exchanged over public channels) to create <a href="https://infosec.exchange/tags/serverless" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>serverless</span></a> <a href="https://infosec.exchange/tags/p2p" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>p2p</span></a> <a href="https://infosec.exchange/tags/authentication" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>authentication</span></a>.</p><p>- i sometimes recieve feedback like "javascript is inherently insecure". i disagree with this and have <a href="https://infosec.exchange/tags/openedSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openedSource</span></a> my <a href="https://infosec.exchange/tags/cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cryptography</span></a> module. its basically a thin wrapper around vanilla cryptography functions of a <a href="https://infosec.exchange/tags/browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>browser</span></a> (webcrypto api).</p><p>- another concern for my kind of app (<a href="https://infosec.exchange/tags/PWA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PWA</span></a>) is that the developer may introduce malicious code. this is an important point for which i open sourced the project and give instructions for <a href="https://infosec.exchange/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosting</span></a>. selhosting this app has some unique features. unlike many other <a href="https://infosec.exchange/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosted</span></a> <a href="https://infosec.exchange/tags/projects" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>projects</span></a>, this app can be hosted on <a href="https://infosec.exchange/tags/githubPages" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>githubPages</span></a> (instructions are provided in the readme). im also working towards having better support for running the index.html directly without a static server.</p><p>- to prevent things like browser extensions, the app uses strict <a href="https://infosec.exchange/tags/CSP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CSP</span></a> headers to prevent <a href="https://infosec.exchange/tags/unauthorised" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unauthorised</span></a> code from running. <a href="https://infosec.exchange/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosting</span></a> users should take note of this when setting up their own instance.</p><p>- i received feedback the <a href="https://infosec.exchange/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Signal</span></a>/#Simplex protocol is great. completely undertsandable and agree, but wonder if im reducing the <a href="https://infosec.exchange/tags/complexity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>complexity</span></a> by working with <a href="https://infosec.exchange/tags/webrtc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webrtc</span></a>. while it has its many flaws, i think risks can be reasonable mitigated if the <a href="https://infosec.exchange/tags/cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cryptography</span></a> functions are implemented correctly. (all data out is <a href="https://infosec.exchange/tags/encrypted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>encrypted</span></a> and all data in is <a href="https://infosec.exchange/tags/decrypted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>decrypted</span></a> on-the-fly)</p><p>- the key detail that makes this approach unique, is because as a <a href="https://infosec.exchange/tags/webapp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webapp</span></a>, unlike other solutions, users have a choice of using any <a href="https://infosec.exchange/tags/device" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>device</span></a>/#os/#browser. while a webapp can have nuanced <a href="https://infosec.exchange/tags/vulnerabilities" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vulnerabilities</span></a>, i think by <a href="https://infosec.exchange/tags/openSourcing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openSourcing</span></a> and providing instructions for <a href="https://infosec.exchange/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosting</span></a> and instructions to <a href="https://infosec.exchange/tags/build" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>build</span></a> for various <a href="https://infosec.exchange/tags/platforms" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>platforms</span></a>, it can provide a reasonable level of <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a>.</p><p>i think if i stick to the principle of avoiding using any kind of "required" service provider (myself included) and allowing the <a href="https://infosec.exchange/tags/frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>frontend</span></a> and the peerjs-server to be <a href="https://infosec.exchange/tags/hosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hosted</span></a> <a href="https://infosec.exchange/tags/independently" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>independently</span></a>, im on track for creating a <a href="https://infosec.exchange/tags/chatSystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chatSystem</span></a> with the "fewest moving parts". i hope you will agree this is true <a href="https://infosec.exchange/tags/p2p" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>p2p</span></a> and i hope i can use this as a step towards true <a href="https://infosec.exchange/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>privacy</span></a> and <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a>. <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a> might be further improved by using a trusted <a href="https://infosec.exchange/tags/VPN" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VPN</span></a>.</p><p>while there are several similar apps out there like mine. i think mine is distinctly a different approach. so its hard to find <a href="https://infosec.exchange/tags/bestPractices" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bestPractices</span></a> for the functionalities i want to achieve. in particular <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a> practices to use when using <a href="https://infosec.exchange/tags/p2p" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>p2p</span></a> technology.</p><p>(note: this app is an <a href="https://infosec.exchange/tags/unstable" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unstable</span></a>, <a href="https://infosec.exchange/tags/experiment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>experiment</span></a>, <a href="https://infosec.exchange/tags/proofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>proofOfConcept</span></a> and not ready to replace any other app or service. It's far from finished and provided for <a href="https://infosec.exchange/tags/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>testing</span></a> and <a href="https://infosec.exchange/tags/demo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>demo</span></a> purposes only. This post is to get <a href="https://infosec.exchange/tags/feedback" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>feedback</span></a> on the progress to determine if i'm going in the right direction for a secure chat app)</p>
Ben Hardill<p><strong>Sharing PGP keys</strong></p><p>A recent boosted <a href="https://social.coop/@fnat/113543896849600364" rel="nofollow noopener" target="_blank">toot</a> from <a rel="nofollow noopener" class="u-url mention" href="https://mastodon.neilzone.co.uk/@neil" target="_blank">@<span>neil</span></a> combined with the <a href="https://keybase.io/" rel="nofollow noopener" target="_blank">keybase.io </a>Linux desktop widget causing me grief (it’s virtual filesystem stuff messing with Gnome file manage) made me think about how folks could, if they needed, find a public PGP key for me.</p><p>Keybase.io was a nice idea, you could tie a PGP key to all your other web persona, this was done by publishing a signed hash e.g. as a tweet, in a DNS record, or at a known location on a web host. This meant that anybody who knew where to find you online could then “prove” that the public PGP key hosted on Keybase.io belonged to you. It was sort of like a modern take on the old <a href="https://en.wikipedia.org/wiki/Key_signing_party" rel="nofollow noopener" target="_blank">key signing parties</a>. But in the end they got <a href="https://keybase.io/blog/keybase-joins-zoom" rel="nofollow noopener" target="_blank">bought by Zoom</a>, and also started handing out crypto tokens…</p><p>Distributing encryption keys is one of the well known <strong>hard</strong> problems in computer science, public key encryption makes it easier in that bit that needs distributing is something that can be shared with everybody, but there is still the discovery problem. E.g. how do I find the right public key of somebody you have never talked to before.</p><p><strong>Public Key Servers</strong></p><p>This is a original way to share keys without having to meet up in person. You uploaded the keys to one of a few key server and tools like gpg/pgp could search for a public key using an email address.</p><p>Servers like:</p><ul><li><a href="https://keys.openpgp.org" rel="nofollow noopener" target="_blank">keys.openpgp.org</a></li><li><a href="https://pgp.mit.edu" rel="nofollow noopener" target="_blank">pgp.mit.edu</a></li><li><a href="https://keys.openpgp.org" rel="nofollow noopener" target="_blank">keys.openpgp.org</a></li></ul><p>I did find longer lists online, but many of the servers didn’t respond when I tried to reach them. There was also a <a href="https://www.vice.com/en/article/someone-is-spamming-and-breaking-a-core-component-of-pgps-ecosystem/" rel="nofollow noopener" target="_blank">concerted effort</a> to spam some of these servers submitting lots of signatures attesting the validity of existing public keys.</p><p>There are several problem with using a 3rd party server </p><ul><li>The person looking up your key needs to know which Key Server to use</li><li>If the Key Server goes down, you are unlikely to get notified</li><li>It’s hard/impossible to remove a key if you have lost access to the matching private key (removal requests need to be signed with the private key to prove you own it)</li></ul><p><strong>Self Hosting</strong></p><p>What we need is a way to self host a discoverable and verifiable public key. There are a few options out there.</p><p><strong>Autocrypt</strong></p><p>This is a little different to other options. Here your email client attaches your public key to all outbound email in the <code>Autocrypt</code> header. e.g.</p> <pre>From: Ben Hardill <ben@hardill.me.uk>X-Clacks-Overhead: GNU Terry PratchettSubject: AutoCrypt TestAutocrypt: addr=ben@hardill.me.uk; keydata= xsFNBGdE1pcBEAC0UC8+URcqTgUdn1/XkbQqZP490NmzYd3eT0skrmVXIdvfq0aANpVKk2M8 Uf9YYcEEvG3szhGlDnNpvAoua9t8M1lV81BzA3Bqqmuci60r+87JWJ9b4mNQ8vyZ6rlqmsiy 3ffZssHHfrphRFJ1CIC1gF9NbeOkQRUb9H3Jlj8z8IIJLfZJ0JvrnZkNWDkF27LiXc9qYGb6 F/vqEUwNMQhhBzR6qVFwbZFR/Lk/DjmqVIVLqfhkfvYJ25m7XTEJtfnEHeEk8Uhvklg67mUS MtFVnE0uVSht7UmHUu4ChOZiDrvrMUMvLVR7nCArcRPrMofqOfkHNeC/c1Lwgma2dUfWiAYT QTNHD0/+sCRmh4d7tb1sR7u8iNtvo+MBqWa5YAUVr+ZLNSqhWk+OIIfNfSJdVIzugxKLuTlK 7u+w2mw0Rf5rDYpIxZ+HhgD+BlvURuZ70GAxtLrVqSBtJP9S3j5uXI60TJbKKAC4JmfLYVCZ JMOGgDSgQ9tPstB+g5m2/LxG2pNSMLYf1HSwdxInaxEQrrGFEGWKK70oWpSx2w30FTsfKKoh k84UwWKt3sSA5qpsgqljQ+QdIq0uyk2uiu4UfwYmqn6Z2iGRvFp0UL6y9k2FXzsGnpylUaMg 9Z0uElWuIvSoj8HKiZynyvN5EqSCxBEn1lMYePyZc6SPo3xA7QARAQABzR9CZW4gSGFyZGls bCA8YmVuQGhhcmRpbGwubWUudWs+wsGOBBMBCgA4FiEETxnBKLtNwgql5WTY/C0/tQgM/tgF AmdE1pcCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQ/C0/tQgM/tiW5w/+PrYZVONv iV1rhqfkGpfoB9FcnkKMBuJOHmsF02cm2fKP1/9PNNvO3LWQQg2JYCvYZxaPu/jkxlOWzF+G GEeNgFotQHXpK9KVZkJhkghaHNeDGoPSBaQ7aWQAQLlHM5RwRcQEeLs+ZVYBhTqyR1AAGYPN /SLRPyjNOEavzmxegeF77k51+wngPr5E9rheoHUSTnF9W+1G0QHU28hqAdfCsKVTMt1KBJLR wLrExgKJJ9g+KiurD8qLdOGh8zr/HdM6WeCCNvKE3akqvUTgVPQxNJcyn7U5pxyxKd+js13I yhfZkW1zmbKqJiZLIsLWHfOgmtBXSBQScGuuGow/e9HhzFaNp1P5mK/qu4ZmOy6FMmcPksNI UmcNMOhpo5hwY9ZMNoX0upb+ES7QDKcj22xkXdOeRepwtcE+ORZ+hnXnSt3vZLJiEoMzskqc eG3Y07gTQW9Ffw9GQd9oYrgOLGx5qfySvY1YnIglw+lMRcPf3c5Ig9miYUKpzQBFR+3bIsan VlqpNCAMEn3/1zm1Hx+BseLzE0xB3l6/bZ/0RBM9UzhBZYJBtHFp/uRTmMVhibM91bHKmTxd cdIVwNjSbY9d5gJunl1E0H4mG+h+FA4ZuSEE7eiX89+pT9ikZ7z+pvgKLOgvvkgq7YPPL7FH PXUMLljaPEyrue++t0GYTME7iJzOwU0EZ0TWlwEQAMWC5NDhlHabqdiU3Xq0ZLIq/CzDMjrs dm4PypkNCzCs2EAcvzX6RPCny9bDzO1w3hcOIBKmxfNrTt79N+OChE26dGC8d3kxTzCFT58t 8xxKDAob0XfA++EXKD4Ys3P+7U1gc3LRW3b2xpiEgO2RtJgXtdmcaLqbApyJVfQpaAl1Mpsb gmcQOEVTmu9dLX6sINbL9C/6mxaOnPNMCe4Sn6QGWNkTUh1MMVlknUKuFa8phctLyQmYkyLf CU+PV9El83RTEOsYPmGve3/TiPSAlt6UohLRfM1Ad4x/sC7n3h5VBKYNshqzSx4WPJGlWq4O 7iqQb34ply2e5O5ZREWwYFO0YCnF4l8r7ReGCnpmWxi0VvvpGfkkvqZnqZVGlK/0MMoAa6LP lxIVrO9zg0U4p7L3MPEcDQS5pNmq/RteMd4sq9HbggIRf97Cew0eSQ55oDa+UOGzsoMId9N0 1xFEkzO12cvr9+fhcv1x9n1zLbpc6HudabvODcqR4kVKEtLksTqa4/dMCV0xMzr9i8Xkb+Ln hl+GWwnm0v2ygvjiyJkWpiWSPR+KYSQ6tWqTLykLHaxE8g3VqaaSFU7Nh3L204S0KQlp+yp6 30JUJz2qbdaHcMMQrnGZHommPW6NKsN+pqO8aNgg4EVlo9Laqcqp9hCsDhWAHWZeuhdEF2hZ ltwfABEBAAHCwXYEGAEKACAWIQRPGcEou03CCqXlZNj8LT+1CAz+2AUCZ0TWlwIbDAAKCRD8 LT+1CAz+2JDLEACLCoLEl5I18h63DBpPKKwsLSL445hTNgLkdAF6712Qam81SKHiLhrb3H1/ sGmou9NOZoMQlH/FYK6zixptQ/V0X1DCKz4kiegdsa2B9DQl5U6G2NTn7qOtBmwXsvruxVzm 0oVaSxNy8tngo+AeyNwTZllyzX9NfmARg68HEDQaBoR7qgDyaNJLRc5oEPU26xASLryl9Don +xpaue0i5M0bq5j2r+eEbX6kgkDKKGePFZerDkcUz8pGIMvW0lJ5FdslkPnBUoeYs2JkpkyU HYMHB1DsDDuc5+KRuEvsXgBPSu4S6uSUIe9TpW7yIareyzsj9zQ/PyPsODTe0NIU0ulYE0RX Dy1Vih6cwyG/EB3OAYDYxeGNSCgSY2xQhKfWJiMo2uQKt+/YO83t8W9zGICLw3IC6b4dCW20 Ym/oigWeLO4L7azaKugZSZTjqHgNuekvAAmpIb6D+hT4PjfN8DyYIzDevZYbkaJXx6gF29Kf 8cFAf1Ckl4DBC4RCy3d/NoIYoOAENoylFpI6OduOBSZtXf48GwnR4QuiZmnqWJMb9BXz4oWO si4xliJukimhQYnDKcPS6P/J5Sc4Rnii0RMrxZGauaeRZU3IGky6OQRnGbcIjc829XtvuDFt tg6vGUkw7A/Jhrjtd7hIHva3gFZiHyJ+uEK5pCVI7qpGvUtqfA==Content-Type: text/plain; charset=UTF-8; format=flowed</pre> <p>Modern versions Thunderbird supports this feature and you can pick which key to attach to each account under the “End-To-End Encryption” section of each account.</p><p>Thunderbird doesn’t automatically import these keys to the local keystore, but it can.</p><p>This also relies on protocols such as SPF and DKIM to ensure the email arrived from a trusted source for the email address in question.</p><p>More details can be found <a href="https://docs.autocrypt.org/" rel="nofollow noopener" target="_blank">here</a>.</p><p><strong>Web Key Service</strong></p><p><a href="https://wiki.gnupg.org/WKS" rel="nofollow noopener" target="_blank">Web Key Service</a> (WKS) is a way to host public keys on a web server, discovery of the web server is done via DNS and has a couple of different options.</p><p>This is what was mentioned in the <a href="https://fabionatali.com/posts/make-your-gnupg-key-discoverable-via-web-key-directory/" rel="nofollow noopener" target="_blank">post</a> linked to in the original toot, but it missed out a couple of details, so I’ll cover all the options here.</p><p>This makes use of the <code>.well-known</code> directory that is used for many other discovery protocols. In this case the location will be <code>.well-known/openpgpkey</code> what comes after that depends on which of the other options is used.</p><p>Firstly the <code>gpg-wks-server</code> tool is used to create the required files and directory structure, but there is a minor niggle with the <code>gpg-wks-server</code> tool, it will only work with a output directory that has the following permissions <code>rwxr-x---</code> which makes it accessible to the owner and people in the same group as the owner, but these files will most likely need to be world readable when deployed to the web server, especially as the intention is to make them available to anybody that needs them.</p> <pre>$ mkdir output-dir$ chmod 740 output-dir$ gpg-wks-server --directory output-dir --install-key 4F19C128BB4DC20AA5E564D8FC2D3FB5080CFED8 ben@hardill.me.uk</pre> <p>This will create a directory under <code>output-dir</code> with the domain name of the email address, in this case <code>hardill.me.uk</code>, under here there will be a <code>hu</code> directory and a policy file. Under the <code>hu</code> directory will be file with name which is a 32bit hex string. This is a SHA1 hash of the local part of the email address in <a href="https://www.rfc-editor.org/rfc/rfc6189.html#section-5.1.6" rel="nofollow noopener" target="_blank">Z-base-32</a> encoding.</p> <pre>output-dir |-hardill.me.uk | |-hu | | |-qpui546ptjbsz3rqaetbdz8wj9op6nur | |-policy</pre> <p>If you have a Web Server running on the same domain as the email domain (e.g. <code>hardill.me.uk</code>) then you can copy the <code>hu</code> directory and <code>policy</code> file to <code>.well-known/openpgpkey</code> directory</p> <pre>/var/www/html/.well-known |-openpgpkey | |-hu | | |-qpui546ptjbsz3rqaetbdz8wj9op6nur | |-policy</pre> <p>If you are not running a Web Server on the same domain, you can create a cname of <code>openpgpkey.[domain]</code> e.g. <code>openpgpkey.hardill.me.uk</code> and point that at a Web Server that will respond to that hostname and in this case you need to include the domain name in the directory structure</p> <pre>/var/www/html/.well-known |-openpgpkey | |-hardill.me.uk | | |-hu | | | |-qpui546ptjbsz3rqaetbdz8wj9op6nur | | |-policy</pre> <p>Thunderbird’s built in PGP support can use this mechanism to look up public keys for email addresses.</p><p>There is a constraint that look ups will only be done over valid HTTPS to prevent man-in-the-middle tampering.</p><p>Also I’ve not mentioned the <code>policy</code> file, this appears to be more aimed at mail service providers, as it dictates how a user should submit their keys via email to the provider for hosting on their WKS instance. It involves a 2 way encrypted email handshake. Since I have direct access to both my Web Server and the keys I want to publish, I’ve not explored setting this up.</p><p>The specification can be found <a href="https://datatracker.ietf.org/doc/draft-koch-openpgp-webkey-service/" rel="nofollow noopener" target="_blank">here</a>.</p><p><strong>DANE</strong></p><p><a href="https://en.wikipedia.org/wiki/DNS-based_Authentication_of_Named_Entities" rel="nofollow noopener" target="_blank">DNS-based Authentication of Named Entities</a> (DANE) was originally a way to do a form of HTTPS certificate pinning via DNS, which when combined with DNSSEC provides assurance that the certificate presented by a Web Server is the one the owner intended.</p><p>It has since been extended to also support providing PGP keys for email users. </p><p>This works by adding <code>OPENPGPKEY</code> records in the <code>_openpgpkey</code> sub domain e.g. <code>_openpgpkey.hardill.me.uk</code>. It uses a SHA256 hash of the local part of the email address as the hostname in the sub domain. This can be generated as follows:</p> <pre>$ echo -n 'ben' | sha256sum | head -c566700869c8ff7480e34a70a708b028700dbaa3a033b5652b903afe89f</pre> <p>(this does make it possible to pre-compute a list of local part’s and then use DNS to iterate these to generate a list of valid email addresses)</p><p>The value of the record is just the ascii armoured version of the key with the <code>-----BEGIN PGP PRIVATE KEY BLOCK-----</code> header and <code>-----END PGP PRIVATE KEY BLOCK-----</code> (and the size) removed, but also with all the line breaks removed.</p><p>The tricky bit is formatting the record correctly, I found a <a href="https://www.huque.com/bin/openpgpkey" rel="nofollow noopener" target="_blank">website</a> that would do it for bind, but this implies they you are editing the zone files by hand, rather than using something like <code>nsupdate</code> to make updates dynamically (this also helps if you have auto DNSSEC signing enabled). So I wrote the following script that will generate the correct <code>nsupdate</code> command to insert the key into DNS in the correct way.</p> <pre>#!/bin/bashMAIL=$1LOCAL=$(echo "${MAIL}" | sed 's/@.*$//')DOMAIN=$(echo "${MAIL}" | sed 's/^.*@//')FQD="$(echo -n $LOCAL | sha256sum | head -c56)._openpgpkey.${DOMAIN}."KEY=$(gpg --export --export-options export-minimal --armor $1 | head -n-2 | tail -n+3 | tr -d '\n')echo "update add $FQD 3600 IN OPENPGPKEY $KEY"</pre> <p>One thing of note is that these records will need to be accessed using DNS over TCP as all secure keys are likely to be too big to fit in a single UDP response packet.</p><p>You can search and import a key using gpg</p> <pre>$ gpg --auto-key-locate clear,nodefault,dane --locate-keys ben@hardill.me.ukgpg: checking the trustdbgpg: marginals needed: 3 completes needed: 1 trust model: pgpgpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1ugpg: key FC2D3FB5080CFED8: public key "Ben Hardill <ben@hardill.me.uk>" importedgpg: Total number processed: 1gpg: imported: 1pub rsa4096 2024-11-25 [SC] 4F19C128BB4DC20AA5E564D8FC2D3FB5080CFED8uid [ unknown] Ben Hardill <ben@hardill.me.uk>sub rsa4096 2024-11-25 [E]</pre> <p>The RFC is <a href="https://datatracker.ietf.org/doc/html/rfc8162" rel="nofollow noopener" target="_blank">here</a>.</p><p><a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://blog.hardill.me.uk/tag/keys/" target="_blank">#keys</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://blog.hardill.me.uk/tag/pgp/" target="_blank">#pgp</a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://tech.lgbt/@deilann" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>deilann</span></a></span> +9001%</p><p>Use <em>actually secure comms</em> instead that are <a href="https://infosec.space/tags/decentralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>decentralized</span></a>, <a href="https://infosec.space/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SelfHosting</span></a>-capable, auditable and provide actual <a href="https://infosec.space/tags/SelfCustody" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SelfCustody</span></a> of all the <a href="https://infosec.space/tags/Keys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Keys</span></a>, so you can <em>enforce</em> your 5th Amendment!</p><ul><li><p>AFAICT <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XMPP</span></a>+<a href="https://infosec.space/tags/OMEMO" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OMEMO</span></a> it is, followered by <a href="https://infosec.space/tags/PGP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PGP</span></a>/MIME <a href="https://infosec.space/tags/eMails" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>eMails</span></a>. For.bith there are excellent clients like <span class="h-card" translate="no"><a href="https://monocles.social/@monocles" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>monocles</span></a></span> / <a href="https://infosec.space/tags/monoclesChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>monoclesChat</span></a> & <span class="h-card" translate="no"><a href="https://fosstodon.org/@gajim" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>gajim</span></a></span> (XMPP+OMEMO) and <span class="h-card" translate="no"><a href="https://chaos.social/@delta" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>delta</span></a></span> / <span class="h-card" translate="no"><a href="https://mastodon.online/@thunderbird" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>thunderbird</span></a></span> (PGP/MIME)...</p></li><li><p>Use <span class="h-card" translate="no"><a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>torproject</span></a></span> / <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tor</span></a> and not <a href="https://infosec.space/tags/VPN" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VPN</span></a> as the latter one <a href="https://web.archive.org/web/20220112020000/https://twitter.com/thegrugq/status/1085614812581715968" rel="nofollow noopener" target="_blank"><em>will snitch</em></a> since <a href="https://infosec.space/tags/loglessVPN" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>loglessVPN</span></a>|s are basically illegal (every juristiction I know demands <a href="https://infosec.space/tags/LawfulInterception" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LawfulInterception</span></a> and <a href="https://infosec.space/tags/logging" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>logging</span></a> by <a href="https://infosec.space/tags/Telcos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Telcos</span></a>)!</p></li></ul>
Kir4ik52 :blobfoxnerd:<p>Key Copier — утилита для копирования замковых ключей с помощью Flipper Zero</p><p>Для копирования бородки надо выбрать модель ключа, приложить сам ключ к экрану Flipper Zero и отрегулировать положение выемок. Цифровой слепок можно использовать для изготовления дубликата в мастерской.</p><p>src: <a href="https://github.com/zinongli/KeyCopier" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">github.com/zinongli/KeyCopier</span><span class="invisible"></span></a></p><p><a href="https://mastodon.ml/tags/blacktriangle" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>blacktriangle</span></a> <a href="https://mastodon.ml/tags/github" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>github</span></a> <a href="https://mastodon.ml/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a> <a href="https://mastodon.ml/tags/foss" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>foss</span></a> <a href="https://mastodon.ml/tags/FlipperZero" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FlipperZero</span></a> <a href="https://mastodon.ml/tags/key" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>key</span></a> <a href="https://mastodon.ml/tags/keys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>keys</span></a></p>
This Is My Glasgow<p>Odell latch keys were most often used for communal doors to provide a level of security at a time when proper locks were much more expensive and the keys were much larger, making them hard to carry around. </p><p>While I knew these were used in Glasgow, I've never found one of their distinctive keyhole plates before. The Odell Night Latches, which these keys fitted into, are almost impossible to find.</p><p><a href="https://mastodon.scot/tags/glasgow" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>glasgow</span></a> <a href="https://mastodon.scot/tags/odelllatchkey" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>odelllatchkey</span></a> <a href="https://mastodon.scot/tags/doorfuriture" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>doorfuriture</span></a> <a href="https://mastodon.scot/tags/keys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>keys</span></a> <a href="https://mastodon.scot/tags/locks" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>locks</span></a> <a href="https://mastodon.scot/tags/glasgowhistory" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>glasgowhistory</span></a></p>
This Is My Glasgow<p>I came across this unusual upside down T-shaped keyhole on the door of a Victorian townhouse in Glasgow today. It's for an Odell Night Latch Key, of the type shown on the right. Patented in 1792, they came in a wide variety of different shapes and you put them through the cross bar of the T and then lifted them up. They'd only open the latch if their shape fitted the inverse shape of the mechanism in the lock itself, which sat on the other side of the door. </p><p>Cont./</p><p><a href="https://mastodon.scot/tags/glasgow" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>glasgow</span></a> <a href="https://mastodon.scot/tags/doorfuriture" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>doorfuriture</span></a> <a href="https://mastodon.scot/tags/keys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>keys</span></a></p>
Chirael (Anthony) :donor: :ferdiverified: 🇺🇦 :rainbow_flag:<p>I’ll stick with my Devious Decoder Card (from <span class="h-card" translate="no"><a href="https://defcon.social/@deviantollam" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>deviantollam</span></a></span>) but this is still cool and better than nothing, something else to try besides taking a picture of the key and trying to decode with a line/depth overlay.</p><p>Kwikset as shown in the video is pretty easy to almost sight read anyway but I wonder if the Flipper app would be harder to use with finer depth increments like Schlage or Best SFIC.</p><p>Still cool to think they could add many more key depths over time though.</p><p><a href="https://www.youtube.com/watch?v=RPrd-S5Cmxo" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">youtube.com/watch?v=RPrd-S5Cmx</span><span class="invisible">o</span></a> <a href="https://infosec.exchange/tags/FlipperZero" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FlipperZero</span></a> <a href="https://infosec.exchange/tags/locksport" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>locksport</span></a> <a href="https://infosec.exchange/tags/locksmith" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>locksmith</span></a> <a href="https://infosec.exchange/tags/keys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>keys</span></a> <a href="https://infosec.exchange/tags/pentesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pentesting</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://grapheneos.social/@GrapheneOS" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>GrapheneOS</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>signalapp</span></a></span> I didn't say all of them have it...</p><p>Re: <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Signal</span></a> I'd not consider it <a href="https://infosec.space/tags/disinfo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>disinfo</span></a> as we've seen more elaborate Setups like <a href="https://infosec.space/tags/EncroChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EncroChat</span></a> & <a href="https://infosec.space/tags/AN%C3%98M" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ANØM</span></a> fall.</p><ul><li><p>Given the fact that one cannot <a href="https://infosec.space/tags/SelfHost" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SelfHost</span></a> <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Signal</span></a>'s backend, they shilled the <a href="https://infosec.space/tags/MobileCoin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MobileCoin</span></a> <a href="https://infosec.space/tags/scam" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>scam</span></a> and use <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PII</span></a> like <a href="https://infosec.space/tags/PhoneNumbers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PhoneNumbers</span></a> to enforce <em>'selective availability'</em> as well being incorporated in the <a href="https://infosec.space/tags/USA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>USA</span></a> all rubs be unpleasantly...</p></li><li><p><em>"The" correct way</em> to do things (sarcasm OFC!) is to do <a href="https://infosec.space/tags/OfflinePGP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OfflinePGP</span></a> but we can all agree <a href="https://www.youtube.com/watch?v=vdab4T_CoN8" rel="nofollow noopener" target="_blank">it's not practical</a>...</p></li></ul><p>I remember when <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Signal</span></a> did a good <a href="https://infosec.space/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>E2EE</span></a> Messenger (<a href="https://infosec.space/tags/TextSecure" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TextSecure</span></a>) and that had a reason to use <a href="https://infosec.space/tags/PhoneNumbers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PhoneNumbers</span></a> as it merely encrypted <a href="https://infosec.space/tags/SMS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SMS</span></a>, but that OFC has other issues.</p><ul><li>In terms if <em>"proper <a href="https://infosec.space/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>E2EE</span></a>"</em> with <a href="https://infosec.space/tags/SelfCustody" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SelfCustody</span></a> if <a href="https://infosec.space/tags/keys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>keys</span></a>, <span class="h-card" translate="no"><a href="https://chaos.social/@delta" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>delta</span></a></span> / <a href="https://infosec.space/tags/deltaChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>deltaChat</span></a> does fit even the stingest criteria - including <a href="https://infosec.space/tags/encrypted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>encrypted</span></a> <a href="https://infosec.space/tags/GroupChats" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GroupChats</span></a>!</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://exquisite.social/@h3artbl33d" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>h3artbl33d</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.sdf.org/@arikb" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>arikb</span></a></span> <span class="h-card" translate="no"><a href="https://grapheneos.social/@GrapheneOS" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>GrapheneOS</span></a></span> well, there are existibg solutions like <a href="https://infosec.space/tags/OTR" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OTR</span></a>, <a href="https://infosec.space/tags/OMEMO" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OMEMO</span></a> or minimalist <a href="https://infosec.space/tags/PGP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PGP</span></a> implementations.</p><ul><li>OFC all of these require <a href="https://infosec.space/tags/SelfCustody" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SelfCustody</span></a> of <a href="https://infosec.space/tags/Keys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Keys</span></a> for real <a href="https://infosec.space/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>E2EE</span></a> where providers basically can't decrypt shit, but one can, already use these today:</li></ul><p>It's 2024, <a href="https://infosec.space/tags/Tails" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tails</span></a> / <span class="h-card" translate="no"><a href="https://fosstodon.org/@tails" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>tails</span></a></span> / <span class="h-card" translate="no"><a href="https://venera.social/profile/tails_live" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>tails_live</span></a></span> , <a href="https://infosec.space/tags/Kleopatra" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kleopatra</span></a> & <a href="https://infosec.space/tags/OpenKeychain" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenKeychain</span></a> exist. There's <a href="https://infosec.space/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>documentation</span></a> and <a href="https://infosec.space/tags/tutorials" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tutorials</span></a> around, and at a certain point we can't help <a href="https://infosec.space/tags/TechIlliterates" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechIlliterates</span></a> that refuse to learn even the simplest & most -"hand holding*" solutions anymore...</p>
Schneier on Security RSS<p>Compromising the Secure Boot Process</p><p>This isn’t good:<br>On Thursday, researchers from security firm Binarly revealed that Secure... <a href="https://www.schneier.com/blog/archives/2024/07/compromising-the-secure-boot-process.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">schneier.com/blog/archives/202</span><span class="invisible">4/07/compromising-the-secure-boot-process.html</span></a></p><p> <a href="https://burn.capital/tags/vulnerabilities" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vulnerabilities</span></a> <a href="https://burn.capital/tags/Uncategorized" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Uncategorized</span></a> <a href="https://burn.capital/tags/cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cryptography</span></a> <a href="https://burn.capital/tags/supplychain" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>supplychain</span></a> <a href="https://burn.capital/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>encryption</span></a> <a href="https://burn.capital/tags/passwords" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>passwords</span></a> <a href="https://burn.capital/tags/keys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>keys</span></a></p>
TrendingLive feeds
Mastodon is the best way to keep up with what's happening.
Follow anyone across the fediverse and see it all in chronological order. No algorithms, ads, or clickbait in sight.
Create accountLoginDrag & drop to upload