<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <updated>2026-01-15T08:17:33Z</updated>
  <generator>https://njump.me</generator>

  <title>Nostr notes by Andrew Ayer</title>
  <author>
    <name>Andrew Ayer</name>
  </author>
  <link rel="self" type="application/atom+xml" href="https://njump.me/npub1c4nxhlszpufxkhzatcptp3t85065k87ugmzvsk7wcnnsa7egf8vq2jssdk.rss" />
  <link href="https://njump.me/npub1c4nxhlszpufxkhzatcptp3t85065k87ugmzvsk7wcnnsa7egf8vq2jssdk" />
  <id>https://njump.me/npub1c4nxhlszpufxkhzatcptp3t85065k87ugmzvsk7wcnnsa7egf8vq2jssdk</id>
  <icon>https://follow.agwa.name/media/a22d3ca3e8dfe2b04bfe961326831fd0bd332911b6e7ac9f3217d412c307fb20.png</icon>
  <logo>https://follow.agwa.name/media/a22d3ca3e8dfe2b04bfe961326831fd0bd332911b6e7ac9f3217d412c307fb20.png</logo>




  <entry>
    <id>https://njump.me/nevent1qqsrelra6wcy49vgjg46p3hnmtagxmuw5spvylllyqwycwzfz23n7tczyrzkv6l7qg83y66ut40q9vx9v73l2jclm3rvfjzmemzwwrhm9pyasducu8u</id>
    
      <title type="html">&amp;#34;private keys associated with eight eMudhra intermediate ...</title>
    
    <link rel="alternate" href="https://njump.me/nevent1qqsrelra6wcy49vgjg46p3hnmtagxmuw5spvylllyqwycwzfz23n7tczyrzkv6l7qg83y66ut40q9vx9v73l2jclm3rvfjzmemzwwrhm9pyasducu8u" />
    <content type="html">
      &amp;#34;private keys associated with eight eMudhra intermediate certificates had been compromised. These keys could allow attackers to issue fraudulent HTTPS certificates for websites they do not control.&amp;#34;&lt;br/&gt;&lt;br/&gt;&lt;a href=&#34;https://groups.google.com/a/mozilla.org/g/dev-security-policy/c/0R3XLJL6FuE&#34;&gt;https://groups.google.com/a/mozilla.org/g/dev-security-policy/c/0R3XLJL6FuE&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;Web browsers are already protected because their certificate verifiers are good. Go and rustls/webki have released security updates that explicitly block the intermediates and you should upgrade if you ship software using these libraries. No word yet from OpenSSL.&lt;br/&gt;&lt;br/&gt;IMO, the easiest and most thorough mitigation is to remove the following roots from your trust store, so that you don&amp;#39;t have to rely on certificate verifiers to block the intermediates:&lt;br/&gt;&lt;br/&gt;- AAA Certificate Services&lt;br/&gt;- anything from eMudhra or emsign&lt;br/&gt;&lt;br/&gt;Removing the AAA root should have no collateral damage provided your trust store is up-to-date (specifically: it has Sectigo&amp;#39;s newer roots). In fact, Mozilla and Chrome removed this root months ago.&lt;br/&gt;&lt;br/&gt;Removing the eMudhra/emsign roots will cause some sites to break but this compromise is so bad that it calls into question their entire operation and possibly their auditor.
    </content>
    <updated>2026-10-20T13:49:21Z</updated>
  </entry>

  <entry>
    <id>https://njump.me/nevent1qqsd7p3ufpav0p38vec5meyruzh8cl7h9e4zakc770kfjfpukvdjqpgzyrzkv6l7qg83y66ut40q9vx9v73l2jclm3rvfjzmemzwwrhm9pyas84pwkh</id>
    
      <title type="html">The State of OpenSSL for pyca/cryptography: ...</title>
    
    <link rel="alternate" href="https://njump.me/nevent1qqsd7p3ufpav0p38vec5meyruzh8cl7h9e4zakc770kfjfpukvdjqpgzyrzkv6l7qg83y66ut40q9vx9v73l2jclm3rvfjzmemzwwrhm9pyas84pwkh" />
    <content type="html">
      The State of OpenSSL for pyca/cryptography: &lt;a href=&#34;https://cryptography.io/en/latest/statements/state-of-openssl/&#34;&gt;https://cryptography.io/en/latest/statements/state-of-openssl/&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;Spoiler: it&amp;#39;s bad.
    </content>
    <updated>2026-01-14T22:43:15Z</updated>
  </entry>

  <entry>
    <id>https://njump.me/nevent1qqszhn8n032fqa93ya0ts38v99t4kpytxx20t7f98q2usss8nh7s49qzyrzkv6l7qg83y66ut40q9vx9v73l2jclm3rvfjzmemzwwrhm9pyasfn9hxk</id>
    
      <title type="html">@nprofile…8nxg These are excellent discoveries! Do you want to ...</title>
    
    <link rel="alternate" href="https://njump.me/nevent1qqszhn8n032fqa93ya0ts38v99t4kpytxx20t7f98q2usss8nh7s49qzyrzkv6l7qg83y66ut40q9vx9v73l2jclm3rvfjzmemzwwrhm9pyasfn9hxk" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqsdcsgqfsa3ehw4uf2xtslp8h2046503k2ggukpuu4d532d587nr5gpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qux9q4a&#39;&gt;nevent1q…9q4a&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;&lt;span itemprop=&#34;mentions&#34; itemscope itemtype=&#34;https://schema.org/Person&#34;&gt;&lt;a itemprop=&#34;url&#34; href=&#34;/nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqdyt7rahrhvmy300sk9jsr46enmzu08w5qkyyl4sp6dm2pc02kccqg68nxg&#34; class=&#34;bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1&#34;&gt;&lt;span&gt;nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqdyt7rahrhvmy300sk9jsr46enmzu08w5qkyyl4sp6dm2pc02kccqg68nxg&lt;/span&gt; (&lt;span class=&#34;italic&#34;&gt;nprofile…8nxg&lt;/span&gt;)&lt;/a&gt;&lt;/span&gt; These are excellent discoveries! Do you want to post this to the mozilla-dev-security-policy thread (&lt;a href=&#34;https://groups.google.com/a/mozilla.org/g/dev-security-policy/c/SgwC1QsEpvc&#34;&gt;https://groups.google.com/a/mozilla.org/g/dev-security-policy/c/SgwC1QsEpvc&lt;/a&gt;). Or I can relay them, with or without attribution.
    </content>
    <updated>2025-09-04T19:14:27Z</updated>
  </entry>

  <entry>
    <id>https://njump.me/nevent1qqsgftdk3zu3v66gatm5ky6g89g6zfu89qsvwadvxsp4ty2s2ugd2tczyrzkv6l7qg83y66ut40q9vx9v73l2jclm3rvfjzmemzwwrhm9pyaslupa0s</id>
    
      <title type="html">The Appmattus CT library doesn&amp;#39;t even need to exist anymore - ...</title>
    
    <link rel="alternate" href="https://njump.me/nevent1qqsgftdk3zu3v66gatm5ky6g89g6zfu89qsvwadvxsp4ty2s2ugd2tczyrzkv6l7qg83y66ut40q9vx9v73l2jclm3rvfjzmemzwwrhm9pyaslupa0s" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqszez9acde2spe34q9gcds3qahvq5lavz6269qkwdp4ga3x5tzcrmspz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qn8ggul&#39;&gt;nevent1q…ggul&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;The Appmattus CT library doesn&amp;#39;t even need to exist anymore - as of Android 16, you can opt your app into Certificate Transparency enforcement provided by the OS: &lt;a href=&#34;https://developer.android.com/privacy-and-security/security-config#certificateTransparencySummary&#34;&gt;https://developer.android.com/privacy-and-security/security-config#certificateTransparencySummary&lt;/a&gt;
    </content>
    <updated>2025-06-21T17:51:32Z</updated>
  </entry>

  <entry>
    <id>https://njump.me/nevent1qqs0463md7wlwy02nx03havajzsck95g03vs8x9fg2rumj33w7wshngzyrzkv6l7qg83y66ut40q9vx9v73l2jclm3rvfjzmemzwwrhm9pyas8t2zj0</id>
    
      <title type="html">Yandex&amp;#39;s covert web-to-app tracking ...</title>
    
    <link rel="alternate" href="https://njump.me/nevent1qqs0463md7wlwy02nx03havajzsck95g03vs8x9fg2rumj33w7wshngzyrzkv6l7qg83y66ut40q9vx9v73l2jclm3rvfjzmemzwwrhm9pyas8t2zj0" />
    <content type="html">
      Yandex&amp;#39;s covert web-to-app tracking (&lt;a href=&#34;https://localmess.github.io/&#34;&gt;https://localmess.github.io/&lt;/a&gt;) relies on shipping the private key for a publicly-trusted SSL certificate for yandexmetrica[.]com to every user of their apps, which is very forbidden.&lt;br/&gt;&lt;br/&gt;Anyone want to extract the private key from their Android app so we can get the cert revoked for key compromise?&lt;br/&gt;&lt;br/&gt;&lt;a href=&#34;https://crt.sh/?q=yandexmetrica.com&#34;&gt;https://crt.sh/?q=yandexmetrica.com&lt;/a&gt;
    </content>
    <updated>2025-06-04T16:12:39Z</updated>
  </entry>

  <entry>
    <id>https://njump.me/nevent1qqsfefpmwdwfv69d6zuhs8kuadgamrgmp4flevdv2hsr83n3x3yqw9szyrzkv6l7qg83y66ut40q9vx9v73l2jclm3rvfjzmemzwwrhm9pyas779zas</id>
    
      <title type="html">Yesterday&amp;#39;s Alpine Linux 3.21.1 release prematurely removed ...</title>
    
    <link rel="alternate" href="https://njump.me/nevent1qqsfefpmwdwfv69d6zuhs8kuadgamrgmp4flevdv2hsr83n3x3yqw9szyrzkv6l7qg83y66ut40q9vx9v73l2jclm3rvfjzmemzwwrhm9pyas779zas" />
    <content type="html">
      Yesterday&amp;#39;s Alpine Linux 3.21.1 release prematurely removed Entrust from the trust store, breaking TLS connections to servers using Entrust certs. They should have waited until Jan 2, 2026. Unfortunately, they vendor curl&amp;#39;s mk-ca-bundle.pl and didn&amp;#39;t update it after curl fixed this bug. &lt;a href=&#34;https://gitlab.alpinelinux.org/alpine/ca-certificates/-/issues/6&#34;&gt;https://gitlab.alpinelinux.org/alpine/ca-certificates/-/issues/6&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;Alpine is a popular base image for containers so this has the potential to be disruptive.&lt;br/&gt;&lt;br/&gt;Background: &lt;a href=&#34;https://sslmate.com/blog/post/entrust_distrust_more_disruptive_than_intended&#34;&gt;https://sslmate.com/blog/post/entrust_distrust_more_disruptive_than_intended&lt;/a&gt;
    </content>
    <updated>2025-01-07T17:28:18Z</updated>
  </entry>

  <entry>
    <id>https://njump.me/nevent1qqsv8gj5gp36hxnn0w53v7uhctnqpn700szv3z7tz4px5rzdj972ftczyrzkv6l7qg83y66ut40q9vx9v73l2jclm3rvfjzmemzwwrhm9pyastgzyrs</id>
    
      <title type="html">A Brazilian certificate authority trusted only by Microsoft has ...</title>
    
    <link rel="alternate" href="https://njump.me/nevent1qqsv8gj5gp36hxnn0w53v7uhctnqpn700szv3z7tz4px5rzdj972ftczyrzkv6l7qg83y66ut40q9vx9v73l2jclm3rvfjzmemzwwrhm9pyastgzyrs" />
    <content type="html">
      A Brazilian certificate authority trusted only by Microsoft has issued a presumably-unauthorized certificate for google.com: &lt;a href=&#34;https://bugzilla.mozilla.org/show_bug.cgi?id=1934361&#34;&gt;https://bugzilla.mozilla.org/show_bug.cgi?id=1934361&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;This can used to intercept traffic to Google from Edge and other Windows applications (except Chrome and Firefox). Hug-ops to Google folks.&lt;br/&gt;&lt;br/&gt;Microsoft are well aware of the extensive history of problems with this CA - I emailed them my concerns in 2021, and further issues were raised during a public CCADB discussion in 2022 - but they clearly don&amp;#39;t care. I hope this incident prompts some change; Windows users deserve better!
    </content>
    <updated>2024-11-30T14:20:30Z</updated>
  </entry>

  <entry>
    <id>https://njump.me/nevent1qqsrllj2vv0wc2ld4aeuuleua3mj298f2c3028pa3a7c09yyw92hngqzyrzkv6l7qg83y66ut40q9vx9v73l2jclm3rvfjzmemzwwrhm9pyaswp6chp</id>
    
      <title type="html">Cert Spotter lets you know if any of your certificates will be ...</title>
    
    <link rel="alternate" href="https://njump.me/nevent1qqsrllj2vv0wc2ld4aeuuleua3mj298f2c3028pa3a7c09yyw92hngqzyrzkv6l7qg83y66ut40q9vx9v73l2jclm3rvfjzmemzwwrhm9pyaswp6chp" />
    <content type="html">
      Cert Spotter lets you know if any of your  certificates will be revoked in the upcoming DigiCert mass revocation. They appear in your Cert Spotter dashboard with the original expiration replaced by the revocation date.&lt;br/&gt;&lt;br/&gt;Handy, because if you log into your DigiCert account, they just give you a list of serial numbers and expect you to figure out what certs they correspond to.&lt;br/&gt;&lt;br/&gt; &lt;img src=&#34;https://follow.agwa.name/media/cdac27488266eb796cbee4eeb803f80e69aecfdce40352469be7255a1fda1fe1.png&#34;&gt; 
    </content>
    <updated>2024-07-31T18:23:17Z</updated>
  </entry>

  <entry>
    <id>https://njump.me/nevent1qqsv857fu36ccpqtgz6ctt4xqfzzx9fp2ssl587rce2gmn04wessv9szyrzkv6l7qg83y66ut40q9vx9v73l2jclm3rvfjzmemzwwrhm9pyasg8c9as</id>
    
      <title type="html">The EU is considering a very bad law called eIDAS that would: - ...</title>
    
    <link rel="alternate" href="https://njump.me/nevent1qqsv857fu36ccpqtgz6ctt4xqfzzx9fp2ssl587rce2gmn04wessv9szyrzkv6l7qg83y66ut40q9vx9v73l2jclm3rvfjzmemzwwrhm9pyasg8c9as" />
    <content type="html">
      The EU is considering a very bad law called eIDAS that would:&lt;br/&gt;&lt;br/&gt;- Force browsers to accept government certificate authorities&lt;br/&gt;&lt;br/&gt;- Ban additional security checks on certificates (such as Certificate Transparency) unless the EU agrees to them&lt;br/&gt;&lt;br/&gt;This would undo 10 years of improvements to encryption on the Web and create an environment very favorable to MitM attacks.&lt;br/&gt;&lt;br/&gt;If you&amp;#39;re an EU citizen, consider writing to the MEP responsible for the eIDAS file, Romana JERKOVIĆ (&lt;a href=&#34;https://www.europarl.europa.eu/meps/en/112747/ROMANA_JERKOVIC/home&#34;&gt;https://www.europarl.europa.eu/meps/en/112747/ROMANA_JERKOVIC/home&lt;/a&gt;), to voice your concern.&lt;br/&gt;&lt;br/&gt;Learn more at &lt;a href=&#34;https://last-chance-for-eidas.org/&#34;&gt;https://last-chance-for-eidas.org/&lt;/a&gt;
    </content>
    <updated>2023-11-02T13:18:44Z</updated>
  </entry>

</feed>