home.social

#tlsv1 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #tlsv1, aggregated by home.social.

  1. chromium-browser (104.0.5112.79-1) unstable; urgency=low

    We've switched the default search engine from Google to DuckDuckGo.
    To manually override it, just go into Settings, click "Search Engine",
    and next to "Search engine used in the address bar", select a different
    search engine from the pull-down.

    Also, catching up on a few upstream changes:

    #TLSv1 and TLSv1.1 support have been completely dropped from chromium
    (as described in chromestatus.com/feature/57591).
    Support for CPUs that lack #SSE3 extensions has also been dropped (as
    described on
    tomshardware.com/news/chrome-s).
    Most users shouldn't notice, unless you're using older hardware or
    "securely" communicating with older hardware.

    Lastly, #Chromium 101 changed a setting for host-based authentication.
    This broke some folks' #Kerberos, among other things. "AuthServerWhitelist"
    was renamed to "AuthServerAllowlist", as described in
    bugs.debian.org/1013268

    -- Andres Salomon <[email protected]> Tue, 16 Aug 2022 17:29:29 -0400

    #Debian #Changelog

  2. chromium-browser (104.0.5112.79-1) unstable; urgency=low

    We've switched the default search engine from Google to DuckDuckGo.
    To manually override it, just go into Settings, click "Search Engine",
    and next to "Search engine used in the address bar", select a different
    search engine from the pull-down.

    Also, catching up on a few upstream changes:

    #TLSv1 and TLSv1.1 support have been completely dropped from chromium
    (as described in chromestatus.com/feature/57591).
    Support for CPUs that lack #SSE3 extensions has also been dropped (as
    described on
    tomshardware.com/news/chrome-s).
    Most users shouldn't notice, unless you're using older hardware or
    "securely" communicating with older hardware.

    Lastly, #Chromium 101 changed a setting for host-based authentication.
    This broke some folks' #Kerberos, among other things. "AuthServerWhitelist"
    was renamed to "AuthServerAllowlist", as described in
    bugs.debian.org/1013268

    -- Andres Salomon <[email protected]> Tue, 16 Aug 2022 17:29:29 -0400

    #Debian #Changelog

  3. chromium-browser (104.0.5112.79-1) unstable; urgency=low

    We've switched the default search engine from Google to DuckDuckGo.
    To manually override it, just go into Settings, click "Search Engine",
    and next to "Search engine used in the address bar", select a different
    search engine from the pull-down.

    Also, catching up on a few upstream changes:

    #TLSv1 and TLSv1.1 support have been completely dropped from chromium
    (as described in chromestatus.com/feature/57591).
    Support for CPUs that lack #SSE3 extensions has also been dropped (as
    described on
    tomshardware.com/news/chrome-s).
    Most users shouldn't notice, unless you're using older hardware or
    "securely" communicating with older hardware.

    Lastly, #Chromium 101 changed a setting for host-based authentication.
    This broke some folks' #Kerberos, among other things. "AuthServerWhitelist"
    was renamed to "AuthServerAllowlist", as described in
    bugs.debian.org/1013268

    -- Andres Salomon <[email protected]> Tue, 16 Aug 2022 17:29:29 -0400

    #Debian #Changelog

  4. chromium-browser (104.0.5112.79-1) unstable; urgency=low

    We've switched the default search engine from Google to DuckDuckGo.
    To manually override it, just go into Settings, click "Search Engine",
    and next to "Search engine used in the address bar", select a different
    search engine from the pull-down.

    Also, catching up on a few upstream changes:

    #TLSv1 and TLSv1.1 support have been completely dropped from chromium
    (as described in chromestatus.com/feature/57591).
    Support for CPUs that lack #SSE3 extensions has also been dropped (as
    described on
    tomshardware.com/news/chrome-s).
    Most users shouldn't notice, unless you're using older hardware or
    "securely" communicating with older hardware.

    Lastly, #Chromium 101 changed a setting for host-based authentication.
    This broke some folks' #Kerberos, among other things. "AuthServerWhitelist"
    was renamed to "AuthServerAllowlist", as described in
    bugs.debian.org/1013268

    -- Andres Salomon <[email protected]> Tue, 16 Aug 2022 17:29:29 -0400

    #Debian #Changelog

  5. chromium-browser (104.0.5112.79-1) unstable; urgency=low

    We've switched the default search engine from Google to DuckDuckGo.
    To manually override it, just go into Settings, click "Search Engine",
    and next to "Search engine used in the address bar", select a different
    search engine from the pull-down.

    Also, catching up on a few upstream changes:

    #TLSv1 and TLSv1.1 support have been completely dropped from chromium
    (as described in chromestatus.com/feature/57591).
    Support for CPUs that lack #SSE3 extensions has also been dropped (as
    described on
    tomshardware.com/news/chrome-s).
    Most users shouldn't notice, unless you're using older hardware or
    "securely" communicating with older hardware.

    Lastly, #Chromium 101 changed a setting for host-based authentication.
    This broke some folks' #Kerberos, among other things. "AuthServerWhitelist"
    was renamed to "AuthServerAllowlist", as described in
    bugs.debian.org/1013268

    -- Andres Salomon <[email protected]> Tue, 16 Aug 2022 17:29:29 -0400

    #Debian #Changelog

  6. #MTTM / #ModellbahnTechnikTeamMünchen

    Dass die Steuerzentrale wo ichs entdeckt hab auf nem #WindowsXP läuft, schön und gut. 💁🏼

    Jetzt hab ich aber die Software gegoogelt und erstaunt festgestellt die hat gar kein TLS 🫣

    mttm.de/

    Wobei, wenn man auf den Shop Link geht, kommt eine Meldung, dass der gerade umgebaut wird.
    Hoffentlich wieder verfügbar bis Ende Juni.
    Da wird sogar extra drauf hingewiesen, dass man TLS hat 😯
    Fragt sich nur, ob #SSL 3.0, oder #TLSv1?🤔

  7. #MTTM / #ModellbahnTechnikTeamMünchen

    Dass die Steuerzentrale wo ichs entdeckt hab auf nem #WindowsXP läuft, schön und gut. 💁🏼

    Jetzt hab ich aber die Software gegoogelt und erstaunt festgestellt die hat gar kein TLS 🫣

    mttm.de/

    Wobei, wenn man auf den Shop Link geht, kommt eine Meldung, dass der gerade umgebaut wird.
    Hoffentlich wieder verfügbar bis Ende Juni.
    Da wird sogar extra drauf hingewiesen, dass man TLS hat 😯
    Fragt sich nur, ob #SSL 3.0, oder #TLSv1?🤔

  8. #MTTM / #ModellbahnTechnikTeamMünchen

    Dass die Steuerzentrale wo ichs entdeckt hab auf nem #WindowsXP läuft, schön und gut. 💁🏼

    Jetzt hab ich aber die Software gegoogelt und erstaunt festgestellt die hat gar kein TLS 🫣

    mttm.de/

    Wobei, wenn man auf den Shop Link geht, kommt eine Meldung, dass der gerade umgebaut wird.
    Hoffentlich wieder verfügbar bis Ende Juni.
    Da wird sogar extra drauf hingewiesen, dass man TLS hat 😯
    Fragt sich nur, ob #SSL 3.0, oder #TLSv1?🤔

  9. #MTTM / #ModellbahnTechnikTeamMünchen

    Dass die Steuerzentrale wo ichs entdeckt hab auf nem #WindowsXP läuft, schön und gut. 💁🏼

    Jetzt hab ich aber die Software gegoogelt und erstaunt festgestellt die hat gar kein TLS 🫣

    mttm.de/

    Wobei, wenn man auf den Shop Link geht, kommt eine Meldung, dass der gerade umgebaut wird.
    Hoffentlich wieder verfügbar bis Ende Juni.
    Da wird sogar extra drauf hingewiesen, dass man TLS hat 😯
    Fragt sich nur, ob #SSL 3.0, oder #TLSv1?🤔

  10. #MTTM / #ModellbahnTechnikTeamMünchen

    Dass die Steuerzentrale wo ichs entdeckt hab auf nem #WindowsXP läuft, schön und gut. 💁🏼

    Jetzt hab ich aber die Software gegoogelt und erstaunt festgestellt die hat gar kein TLS 🫣

    mttm.de/

    Wobei, wenn man auf den Shop Link geht, kommt eine Meldung, dass der gerade umgebaut wird.
    Hoffentlich wieder verfügbar bis Ende Juni.
    Da wird sogar extra drauf hingewiesen, dass man TLS hat 😯
    Fragt sich nur, ob #SSL 3.0, oder #TLSv1?🤔

  11. Just in time for some holiday play, #Radiator v4.27 is now out with #TLSv1.3 support in authentication (#EAP-TLS #PEAP #TTLS) and transport (#RadSec) protocols. blog.radiatorsoftware.com/2022

  12. Just in time for some holiday play, #Radiator v4.27 is now out with #TLSv1.3 support in authentication (#EAP-TLS #PEAP #TTLS) and transport (#RadSec) protocols. blog.radiatorsoftware.com/2022

  13. Just in time for some holiday play, #Radiator v4.27 is now out with #TLSv1.3 support in authentication (#EAP-TLS #PEAP #TTLS) and transport (#RadSec) protocols. blog.radiatorsoftware.com/2022

  14. "Kratz mich, beiß mich, flüster mir #TLSv1.3 verschlüsselte Schweinereien ins Ohr!"

  15. #nginx 1.17.2 auf #Ubuntu Server 18.04 LTS: Endlich Support für #TLSv1.3 👍
    Blöd nur, dass man unter "Key Exchange" und "Cipher Strength" nur noch 90% bekommt, sobald TLSv1.3 aktiv ist... 🧐

  16. Current Status: Trusted TLS connection established to dungeon.maclemon.at:25: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)

    #SysadminLife #TLSv1.3 #Email
    That's the way, aha, aha, I like it.