<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: Gargyle</title><link>https://news.ycombinator.com/user?id=Gargyle</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 17 Apr 2026 23:57:34 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=Gargyle" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by Gargyle in "Show HN: Digital privacy game for middle schoolers, our Harvard final project"]]></title><description><![CDATA[
<p>Complains about tracking, uses google assets.</p>
]]></description><pubDate>Sun, 25 Dec 2022 16:20:23 +0000</pubDate><link>https://news.ycombinator.com/item?id=34128449</link><dc:creator>Gargyle</dc:creator><comments>https://news.ycombinator.com/item?id=34128449</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=34128449</guid></item><item><title><![CDATA[New comment by Gargyle in "“Metadata of the metadata” informs product design without allowing backdoors"]]></title><description><![CDATA[
<p>What an egregious mislabeling.<p>Data -> Chats and actual Identity<p>Metadata -> Who with whom and when from where,...<p>They construe payment info, PII and similar except chat contents as metadata and say metadata of metadata was that which is normally called metadata. And that it was safe to share despite this obviously being not true.<p>Everyone remembers <a href="https://www.nybooks.com/daily/2014/05/10/we-kill-people-based-metadata/" rel="nofollow">https://www.nybooks.com/daily/2014/05/10/we-kill-people-base...</a><p>?<p>How does one understand the authors motivation?</p>
]]></description><pubDate>Sun, 14 Nov 2021 23:42:09 +0000</pubDate><link>https://news.ycombinator.com/item?id=29221860</link><dc:creator>Gargyle</dc:creator><comments>https://news.ycombinator.com/item?id=29221860</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29221860</guid></item><item><title><![CDATA[New comment by Gargyle in "Sign arbitrary data with your SSH keys"]]></title><description><![CDATA[
<p>Are there resources on the impact of Keybase being bought by Zoom?
Zoom is out of question too because they discourage e2e and darkpattern you into installing their software despite browser compatibility and because they darkpattern you into giving cam/mic access just to listen to a broadcast-only session even if unnecessary. They place their own controlled device toggles as source of truth instead of those by the browser UI and fail in weird ways if you toggle in-browser.
(Same for almost all other similar software as well)<p>I tossed them without a second thought after they annoyed me with Stellar. Nobody uses Stellar if they dont have a hidden incentive. It always had a huge forced marketing vibe.<p>Is there some sucessor to keybase?<p>(Motivation disclaimer: I want to dump on Keybase because in the end, even with flawless crypto at first, those organizations always erode the good things down to centralized with platform control again.)</p>
]]></description><pubDate>Sat, 13 Nov 2021 19:32:45 +0000</pubDate><link>https://news.ycombinator.com/item?id=29212532</link><dc:creator>Gargyle</dc:creator><comments>https://news.ycombinator.com/item?id=29212532</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29212532</guid></item><item><title><![CDATA[New comment by Gargyle in "Sign arbitrary data with your SSH keys"]]></title><description><![CDATA[
<p>Cryptographic Trust /= Trust in persons motives.<p>I guess we need better words.</p>
]]></description><pubDate>Sat, 13 Nov 2021 17:05:51 +0000</pubDate><link>https://news.ycombinator.com/item?id=29211302</link><dc:creator>Gargyle</dc:creator><comments>https://news.ycombinator.com/item?id=29211302</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29211302</guid></item><item><title><![CDATA[New comment by Gargyle in "Sign arbitrary data with your SSH keys"]]></title><description><![CDATA[
<p>SSH tooling does not make that any better tbh.<p>Things are being worked on.<p>Watch Sequoia.<p>Maybe some things regarding UX on my radar will surface in a range of <2 years.</p>
]]></description><pubDate>Sat, 13 Nov 2021 17:01:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=29211270</link><dc:creator>Gargyle</dc:creator><comments>https://news.ycombinator.com/item?id=29211270</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29211270</guid></item><item><title><![CDATA[New comment by Gargyle in "Sign arbitrary data with your SSH keys"]]></title><description><![CDATA[
<p>You might have gotten me having this too narrow to be broadly useful. Because we were already arguing about a detail and I concentrate just on this detail, not a general github privacy overview.<p>The whole intention was to raise attention to a less often mentioned part of the information github exposes about accounts.</p>
]]></description><pubDate>Sat, 13 Nov 2021 16:57:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=29211220</link><dc:creator>Gargyle</dc:creator><comments>https://news.ycombinator.com/item?id=29211220</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29211220</guid></item><item><title><![CDATA[New comment by Gargyle in "Sign arbitrary data with your SSH keys"]]></title><description><![CDATA[
<p>Right. They always use git@ instead of account@ and there is no further meta in the git remote url.
(gut remote url is a funny typo)</p>
]]></description><pubDate>Sat, 13 Nov 2021 15:21:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=29210339</link><dc:creator>Gargyle</dc:creator><comments>https://news.ycombinator.com/item?id=29210339</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29210339</guid></item><item><title><![CDATA[New comment by Gargyle in "Sign arbitrary data with your SSH keys"]]></title><description><![CDATA[
<p>(Don't expect realtime/neartime messages. I'll write whenever I feel like it.)<p>ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCssSd91viJEmUQNx28L6JifYcGwTNEkLnmvZvdNxWxdTCrKwPEBVdlLooN90QugL/mJVwcWj9qsnOLbcoVaJlqMppY8UYlHP6OnGwKRGkpPdbKHnBA+Rrg7r8GUwdLW/PvI8DWhEPXzzWvrCNiESJWVdSCT2bTfAA3CQuPnL9cr5hcpw0i1jf7PBXRiVw2E2133KhEr91xNMH/jXh4jrly3J+kmBEmJcrkHNrHj0O8Ml+PmVQknq+tYT1DivnE2dxHoMkfdP0xP9yV9s0+7/JhU+tnXJ2+kaIOSpOOmhBPyjNYO6wkNvQh3aYzKrtcoOWPO2y56sfw9Uqlbpyr1ZU1 Gargyle</p>
]]></description><pubDate>Sat, 13 Nov 2021 15:17:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=29210310</link><dc:creator>Gargyle</dc:creator><comments>https://news.ycombinator.com/item?id=29210310</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29210310</guid></item><item><title><![CDATA[New comment by Gargyle in "Sign arbitrary data with your SSH keys"]]></title><description><![CDATA[
<p>Maybe this needs more precise wording.
Like ingress/signature key but more compressed instead of public key.
Or peer key.
Any nice ideas?</p>
]]></description><pubDate>Sat, 13 Nov 2021 14:48:24 +0000</pubDate><link>https://news.ycombinator.com/item?id=29210094</link><dc:creator>Gargyle</dc:creator><comments>https://news.ycombinator.com/item?id=29210094</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29210094</guid></item><item><title><![CDATA[New comment by Gargyle in "Sign arbitrary data with your SSH keys"]]></title><description><![CDATA[
<p>The parents comment style is inherently advice.</p>
]]></description><pubDate>Sat, 13 Nov 2021 14:44:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=29210066</link><dc:creator>Gargyle</dc:creator><comments>https://news.ycombinator.com/item?id=29210066</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29210066</guid></item><item><title><![CDATA[New comment by Gargyle in "Sign arbitrary data with your SSH keys"]]></title><description><![CDATA[
<p>Can be configured in .ssh/config.
Shortcut for that is to use subdirs or filenames for keys that arent searched automatically and not have a default-name-key.</p>
]]></description><pubDate>Sat, 13 Nov 2021 14:42:04 +0000</pubDate><link>https://news.ycombinator.com/item?id=29210044</link><dc:creator>Gargyle</dc:creator><comments>https://news.ycombinator.com/item?id=29210044</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29210044</guid></item><item><title><![CDATA[New comment by Gargyle in "Sign arbitrary data with your SSH keys"]]></title><description><![CDATA[
<p>I am not sure actually because I do not have any persistent github accounts. I only do them in a throwaway fashion. (Of course Github is making that more annoying by the month, as every other bigcorp site.)</p>
]]></description><pubDate>Sat, 13 Nov 2021 14:40:29 +0000</pubDate><link>https://news.ycombinator.com/item?id=29210032</link><dc:creator>Gargyle</dc:creator><comments>https://news.ycombinator.com/item?id=29210032</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29210032</guid></item><item><title><![CDATA[New comment by Gargyle in "Sign arbitrary data with your SSH keys"]]></title><description><![CDATA[
<p>Its actually the same thing. A shared identifier. Of course email is another thing to separate for separate identities. But it is way more widely known that email adresses are used ad an unique identifier.</p>
]]></description><pubDate>Sat, 13 Nov 2021 14:35:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=29209999</link><dc:creator>Gargyle</dc:creator><comments>https://news.ycombinator.com/item?id=29209999</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29209999</guid></item><item><title><![CDATA[New comment by Gargyle in "Sign arbitrary data with your SSH keys"]]></title><description><![CDATA[
<p>I am just wary of flattery and "my friend".
I am not especially suspicious of your motives but we don't know each other yet. If you want to have an interesting conversation with me I am positive to do that pseudonymously. Maybe leave me a pubkey here</p>
]]></description><pubDate>Sat, 13 Nov 2021 14:32:52 +0000</pubDate><link>https://news.ycombinator.com/item?id=29209980</link><dc:creator>Gargyle</dc:creator><comments>https://news.ycombinator.com/item?id=29209980</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29209980</guid></item><item><title><![CDATA[New comment by Gargyle in "Sign arbitrary data with your SSH keys"]]></title><description><![CDATA[
<p>That happens as part of the ssh handshake. And is the basis of this whole scheme.
No idea if there is tooling to.do.that for arbitrary messages.</p>
]]></description><pubDate>Sat, 13 Nov 2021 14:29:27 +0000</pubDate><link>https://news.ycombinator.com/item?id=29209956</link><dc:creator>Gargyle</dc:creator><comments>https://news.ycombinator.com/item?id=29209956</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29209956</guid></item><item><title><![CDATA[New comment by Gargyle in "Sign arbitrary data with your SSH keys"]]></title><description><![CDATA[
<p>Attaching this to cryptoassets increases your operational (more mental overhead, doesnt work with simple keybearer devices, you assume people to be lazy and bad at key management) and technical (irrevocable ethereum-bugs that can only be mitigated by chain splits) complexity.<p>Albeit for long-term public signatures I see the benefit in spreading the sig and revocation information from the classical tools in to as many hard to modify places as possible. Popular global databases like Ethereum and similar are good condidates for that.<p>And of course have the verification scheme expose inconsistencies between different key-sources and tag them with their respective power structure categories. (Lime Government, Cryptocurrency-Devs, HugeCodeHostingPlatform, CompanyBehindHugeCodeHostingPlatform, etc...)</p>
]]></description><pubDate>Sat, 13 Nov 2021 12:50:11 +0000</pubDate><link>https://news.ycombinator.com/item?id=29209398</link><dc:creator>Gargyle</dc:creator><comments>https://news.ycombinator.com/item?id=29209398</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29209398</guid></item><item><title><![CDATA[New comment by Gargyle in "Sign arbitrary data with your SSH keys"]]></title><description><![CDATA[
<p>Is that sarcasm?</p>
]]></description><pubDate>Sat, 13 Nov 2021 12:41:52 +0000</pubDate><link>https://news.ycombinator.com/item?id=29209366</link><dc:creator>Gargyle</dc:creator><comments>https://news.ycombinator.com/item?id=29209366</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29209366</guid></item><item><title><![CDATA[New comment by Gargyle in "Sign arbitrary data with your SSH keys"]]></title><description><![CDATA[
<p>Then this is bad advice in general because its specific to a low trust expectation. Would be sensible to note that in your comment.</p>
]]></description><pubDate>Sat, 13 Nov 2021 12:35:02 +0000</pubDate><link>https://news.ycombinator.com/item?id=29209333</link><dc:creator>Gargyle</dc:creator><comments>https://news.ycombinator.com/item?id=29209333</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29209333</guid></item><item><title><![CDATA[New comment by Gargyle in "Sign arbitrary data with your SSH keys"]]></title><description><![CDATA[
<p>The crowd that needs privacy is also the most high stakes and vulnerable crowd.
They are the people that may save civil society with a structure built by thousands of small stones.
Dismissing concern in that area is inherently giving tyrants and aspiring ones power.</p>
]]></description><pubDate>Sat, 13 Nov 2021 12:28:06 +0000</pubDate><link>https://news.ycombinator.com/item?id=29209298</link><dc:creator>Gargyle</dc:creator><comments>https://news.ycombinator.com/item?id=29209298</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29209298</guid></item><item><title><![CDATA[New comment by Gargyle in "Sign arbitrary data with your SSH keys"]]></title><description><![CDATA[
<p>To shortcut a lot of this developing twister of why people should use different keypairs for different ssh hosts:<p>Its a big privacy leak, not a big security leak.<p>Your Pubkey can be used to cross-match multiple identities.
Example:
You have different coding personae.
One that is activist, one that is company-peon.
Different accounts, same SSH pubkey in Github or other server with publicly listed pubkeys --> Same person confirmed.<p>As a result of this the information can be used to target each of the identities in a more precise manner. On the human layer of the security side: 
New phishing/deception/blackmail vectors.<p>On the organizational layer: we have to target these keybearer devices now.<p>Maybe it even helps in a cryptanalytic way in some weird exotic scenario but not substantially.<p>And of course separation of concerns if you have different keybearer devices.<p>(Also the famous Keysticks are a nice solution to that organizationally but they are an additional risk for big scale attacks by having biased RNGs. In the end its hardware and audits are just a voluntary thing by corps. They can always choose to hide things from auditors or do a compromised batch at their mercy.)</p>
]]></description><pubDate>Sat, 13 Nov 2021 12:19:56 +0000</pubDate><link>https://news.ycombinator.com/item?id=29209264</link><dc:creator>Gargyle</dc:creator><comments>https://news.ycombinator.com/item?id=29209264</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29209264</guid></item></channel></rss>