<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic TrustPanel's shield-with-checkmark icon may create a misconceptions of security in Discussions</title>
    <link>https://connect.mozilla.org/t5/discussions/trustpanel-s-shield-with-checkmark-icon-may-create-a/m-p/121404#M47680</link>
    <description>&lt;P&gt;I appreciate Mozilla's effort to simplify the address bar by combining the old Privacy (shield) and Security (padlock) panels into a single TrustPanel in Firefox 149. Having one place to check both privacy protections and connection security is a good idea in principle.&lt;/P&gt;&lt;P&gt;However, I have a concern about the new visual design:&lt;/P&gt;&lt;P&gt;The previous padlock icon clearly communicated one specific technical fact: “This connection is encrypted via HTTPS.” It was neutral and precise — it never claimed the website itself was safe.&lt;/P&gt;&lt;P&gt;Now, a shield icon with a checkmark (often in green/success style) is used to indicate that everything is “protected” or “secure.” This change can easily lead ordinary users to mistakenly believe “This website is safe, I can safely enter my personal information or passwords.”&lt;/P&gt;&lt;P&gt;In reality:&lt;BR /&gt;- HTTPS only provides transport-layer encryption (protecting against eavesdropping and man-in-the-middle attacks).&lt;BR /&gt;- It does not guarantee that the website is legitimate. Phishing sites, look-alike domains (e.g. fake bank pages), or compromised legitimate sites can still be fully HTTPS-encrypted.&lt;BR /&gt;- Even on encrypted pages, there can be vulnerabilities, malicious scripts, or risks from unsafe browser extensions.&lt;/P&gt;&lt;P&gt;The visual language of a checkmark strongly signals “Everything is OK” in users’ minds, which may create a false sense of security. This could make users less cautious than they should be.&lt;/P&gt;&lt;P&gt;Suggestion:&lt;/P&gt;&lt;P&gt;Keep the unified TrustPanel (it’s convenient), but improve the icon to better reflect the distinction:&lt;BR /&gt;- Use a shield icon combined with a small padlock, or&lt;BR /&gt;- Use a shield icon with a keyhole in the center.&lt;/P&gt;&lt;P&gt;This would maintain clarity that the icon represents both privacy protections and connection encryption, without implying overall safety of the site.&lt;/P&gt;&lt;P&gt;What do you think? Has anyone else noticed this potential issue? I’d love to hear your opinions.&lt;BR /&gt;(This post was drafted in English with help from&amp;nbsp;machine for clarity and natural flow.If you notice anything amiss, Please leave a comment below, thank you.)&lt;/P&gt;</description>
    <pubDate>Sun, 29 Mar 2026 16:58:35 GMT</pubDate>
    <dc:creator>Frain</dc:creator>
    <dc:date>2026-03-29T16:58:35Z</dc:date>
    <item>
      <title>TrustPanel's shield-with-checkmark icon may create a misconceptions of security</title>
      <link>https://connect.mozilla.org/t5/discussions/trustpanel-s-shield-with-checkmark-icon-may-create-a/m-p/121404#M47680</link>
      <description>&lt;P&gt;I appreciate Mozilla's effort to simplify the address bar by combining the old Privacy (shield) and Security (padlock) panels into a single TrustPanel in Firefox 149. Having one place to check both privacy protections and connection security is a good idea in principle.&lt;/P&gt;&lt;P&gt;However, I have a concern about the new visual design:&lt;/P&gt;&lt;P&gt;The previous padlock icon clearly communicated one specific technical fact: “This connection is encrypted via HTTPS.” It was neutral and precise — it never claimed the website itself was safe.&lt;/P&gt;&lt;P&gt;Now, a shield icon with a checkmark (often in green/success style) is used to indicate that everything is “protected” or “secure.” This change can easily lead ordinary users to mistakenly believe “This website is safe, I can safely enter my personal information or passwords.”&lt;/P&gt;&lt;P&gt;In reality:&lt;BR /&gt;- HTTPS only provides transport-layer encryption (protecting against eavesdropping and man-in-the-middle attacks).&lt;BR /&gt;- It does not guarantee that the website is legitimate. Phishing sites, look-alike domains (e.g. fake bank pages), or compromised legitimate sites can still be fully HTTPS-encrypted.&lt;BR /&gt;- Even on encrypted pages, there can be vulnerabilities, malicious scripts, or risks from unsafe browser extensions.&lt;/P&gt;&lt;P&gt;The visual language of a checkmark strongly signals “Everything is OK” in users’ minds, which may create a false sense of security. This could make users less cautious than they should be.&lt;/P&gt;&lt;P&gt;Suggestion:&lt;/P&gt;&lt;P&gt;Keep the unified TrustPanel (it’s convenient), but improve the icon to better reflect the distinction:&lt;BR /&gt;- Use a shield icon combined with a small padlock, or&lt;BR /&gt;- Use a shield icon with a keyhole in the center.&lt;/P&gt;&lt;P&gt;This would maintain clarity that the icon represents both privacy protections and connection encryption, without implying overall safety of the site.&lt;/P&gt;&lt;P&gt;What do you think? Has anyone else noticed this potential issue? I’d love to hear your opinions.&lt;BR /&gt;(This post was drafted in English with help from&amp;nbsp;machine for clarity and natural flow.If you notice anything amiss, Please leave a comment below, thank you.)&lt;/P&gt;</description>
      <pubDate>Sun, 29 Mar 2026 16:58:35 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/trustpanel-s-shield-with-checkmark-icon-may-create-a/m-p/121404#M47680</guid>
      <dc:creator>Frain</dc:creator>
      <dc:date>2026-03-29T16:58:35Z</dc:date>
    </item>
    <item>
      <title>Re: TrustPanel's shield-with-checkmark icon may create a misconceptions of security</title>
      <link>https://connect.mozilla.org/t5/discussions/trustpanel-s-shield-with-checkmark-icon-may-create-a/m-p/121408#M47683</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;A subject &lt;A href="https://www.reddit.com/r/FirefoxCSS/comments/1s325pk/i_dont_like_the_new_shield_icon_as_much_as_the" target="_blank"&gt;https://www.reddit.com/r/FirefoxCSS/comments/1s325pk/i_dont_like_the_new_shield_icon_as_much_as_the&lt;/A&gt;&lt;BR /&gt;If you wish to test &lt;A href="https://www.reddit.com/r/FirefoxCSS/comments/1s325pk/comment/occu9ev" target="_blank"&gt;https://www.reddit.com/r/FirefoxCSS/comments/1s325pk/comment/occu9ev&lt;/A&gt; browser.urlbar.trustPanel.featureGate&lt;/P&gt;&lt;P&gt;Yes, https isn't always "clean" safe &lt;A href="https://connect.mozilla.org/t5/discussions/google-blocked-direct-access-to-our-site-in-firefox/td-p/39931" target="_blank"&gt;https://connect.mozilla.org/t5/discussions/google-blocked-direct-access-to-our-site-in-firefox/td-p/39931&lt;/A&gt;&lt;/P&gt;&lt;P&gt;To complement&lt;BR /&gt;&lt;A href="https://support.mozilla.org/en-US/questions/1573386" target="_blank"&gt;https://support.mozilla.org/en-US/questions/1573386&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://connect.mozilla.org/t5/discussions/new-vague-errors-with-sites/td-p/120666" target="_blank"&gt;https://connect.mozilla.org/t5/discussions/new-vague-errors-with-sites/td-p/120666&lt;/A&gt; *&lt;BR /&gt;* Note: new analyze &lt;A href="https://www.ssllabs.com/ssltest/analyze.html?d=avenerussia.ru&amp;amp;latest" target="_blank"&gt;https://www.ssllabs.com/ssltest/analyze.html?d=avenerussia.ru&amp;amp;latest&lt;/A&gt; is ok at instant.&lt;/P&gt;</description>
      <pubDate>Sun, 29 Mar 2026 17:54:54 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/trustpanel-s-shield-with-checkmark-icon-may-create-a/m-p/121408#M47683</guid>
      <dc:creator>Agentvirtuel</dc:creator>
      <dc:date>2026-03-29T17:54:54Z</dc:date>
    </item>
    <item>
      <title>Re: TrustPanel's shield-with-checkmark icon may create a misconceptions of security</title>
      <link>https://connect.mozilla.org/t5/discussions/trustpanel-s-shield-with-checkmark-icon-may-create-a/m-p/121464#M47708</link>
      <description>&lt;P&gt;Thanks for the reply. "browser.urlbar.trustPanel.featureGateworks" in&amp;nbsp;about:config is works for now. It seems there are still many aspects of SSL security and display that warrant our attention. Thank you.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Mar 2026 09:05:39 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/trustpanel-s-shield-with-checkmark-icon-may-create-a/m-p/121464#M47708</guid>
      <dc:creator>Frain</dc:creator>
      <dc:date>2026-03-30T09:05:39Z</dc:date>
    </item>
  </channel>
</rss>

