#openssl — Public Fediverse posts

「OpenSSL」の次期長期サポート版は「OpenSSL 4.2」、「OpenSSL 5.0」は2027年10月／今後のリリーススケジュールが発表
https://forest.watch.impress.co.jp/docs/news/2107570.html

#forest_watch_impress #OpenSSL #セキュリティ #その他 #インターネット #ネットワーク

「OpenSSL」の次期長期サポート版は「OpenSSL 4.2」、「OpenSSL 5.0」は2027年10月／今後のリリーススケジュールが発表
https://forest.watch.impress.co.jp/docs/news/2107570.html

#forest_watch_impress #OpenSSL #セキュリティ #その他 #インターネット #ネットワーク

「OpenSSL」の次期長期サポート版は「OpenSSL 4.2」、「OpenSSL 5.0」は2027年10月／今後のリリーススケジュールが発表
https://forest.watch.impress.co.jp/docs/news/2107570.html

#forest_watch_impress #OpenSSL #セキュリティ #その他 #インターネット #ネットワーク

Sehr schön, der Fix für #CopyFail und #openssl bei #openWrt ist da. Zack, eine Minute Update, eine Minute Reboot, schon ist die #openWrt-One wieder im Rennen. Auch wenn Privilgieneskalation auf einem solchen System kaum ein Anwendungsfall sein dürfte, aber was soll's...

Der Fix für #DirtyFrag wird sicher zeitnah aufpoppen.

$ ssh root@openwrt-one owut upgrade
ASU-Server     https://sysupgrade.openwrt.org
Upstream       https://downloads.openwrt.org
Target         mediatek/filogic
Profile        openwrt_one
Package-arch   aarch64_cortex-a53
Version-from   25.12.2 r32802-f505120278 (kernel 6.12.74)
Version-to     25.12.3 r32912-6639b15f62 (kernel 6.12.85)
93 packages are out-of-date
There are 0 missing and 1 modified default packages
Request hash: <xxx>
--
Status:   done
Progress:   0s total =   0s in queue +   0s in build

Build succeeded in   0s total =   0s in queue +   0s to build:
Image saved : /tmp/firmware.bin
Installing /tmp/firmware.bin and rebooting...

#GNU/Linux #security #wifi #wlan #PoweredByRSS

forum.openwrt.org/t/openwrt-25…

Sehr schön, der Fix für #CopyFail und #openssl bei #openWrt ist da. Zack, eine Minute Update, eine Minute Reboot, schon ist die #openWrt-One wieder im Rennen. Auch wenn Privilgieneskalation auf einem solchen System kaum ein Anwendungsfall sein dürfte, aber was soll's...

Der Fix für #DirtyFrag wird sicher zeitnah aufpoppen.

$ ssh root@openwrt-one owut upgrade
ASU-Server     https://sysupgrade.openwrt.org
Upstream       https://downloads.openwrt.org
Target         mediatek/filogic
Profile        openwrt_one
Package-arch   aarch64_cortex-a53
Version-from   25.12.2 r32802-f505120278 (kernel 6.12.74)
Version-to     25.12.3 r32912-6639b15f62 (kernel 6.12.85)
93 packages are out-of-date
There are 0 missing and 1 modified default packages
Request hash: <xxx>
--
Status:   done
Progress:   0s total =   0s in queue +   0s in build

Build succeeded in   0s total =   0s in queue +   0s to build:
Image saved : /tmp/firmware.bin
Installing /tmp/firmware.bin and rebooting...

#GNU/Linux #security #wifi #wlan #PoweredByRSS

forum.openwrt.org/t/openwrt-25…

Sehr schön, der Fix für #CopyFail und #openssl bei #openWrt ist da. Zack, eine Minute Update, eine Minute Reboot, schon ist die #openWrt-One wieder im Rennen. Auch wenn Privilgieneskalation auf einem solchen System kaum ein Anwendungsfall sein dürfte, aber was soll's...

Der Fix für #DirtyFrag wird sicher zeitnah aufpoppen.

$ ssh root@openwrt-one owut upgrade
ASU-Server     https://sysupgrade.openwrt.org
Upstream       https://downloads.openwrt.org
Target         mediatek/filogic
Profile        openwrt_one
Package-arch   aarch64_cortex-a53
Version-from   25.12.2 r32802-f505120278 (kernel 6.12.74)
Version-to     25.12.3 r32912-6639b15f62 (kernel 6.12.85)
93 packages are out-of-date
There are 0 missing and 1 modified default packages
Request hash: <xxx>
--
Status:   done
Progress:   0s total =   0s in queue +   0s in build

Build succeeded in   0s total =   0s in queue +   0s to build:
Image saved : /tmp/firmware.bin
Installing /tmp/firmware.bin and rebooting...

#GNU/Linux #security #wifi #wlan #PoweredByRSS

forum.openwrt.org/t/openwrt-25…

Sehr schön, der Fix für #CopyFail und #openssl bei #openWrt ist da. Zack, eine Minute Update, eine Minute Reboot, schon ist die #openWrt-One wieder im Rennen. Auch wenn Privilgieneskalation auf einem solchen System kaum ein Anwendungsfall sein dürfte, aber was soll's...

Der Fix für #DirtyFrag wird sicher zeitnah aufpoppen.

$ ssh root@openwrt-one owut upgrade
ASU-Server     https://sysupgrade.openwrt.org
Upstream       https://downloads.openwrt.org
Target         mediatek/filogic
Profile        openwrt_one
Package-arch   aarch64_cortex-a53
Version-from   25.12.2 r32802-f505120278 (kernel 6.12.74)
Version-to     25.12.3 r32912-6639b15f62 (kernel 6.12.85)
93 packages are out-of-date
There are 0 missing and 1 modified default packages
Request hash: <xxx>
--
Status:   done
Progress:   0s total =   0s in queue +   0s in build

Build succeeded in   0s total =   0s in queue +   0s to build:
Image saved : /tmp/firmware.bin
Installing /tmp/firmware.bin and rebooting...

#GNU/Linux #security #wifi #wlan #PoweredByRSS

forum.openwrt.org/t/openwrt-25…

Last week I asked in a blog about #openssl 4 support and experiences:

https://www.syslog-ng.com/community/b/blog/posts/support-for-openssl-4-0

We received a detailed answer, and also a pull request to the #syslog_ng #GitHub repo. Of course, more investigation is needed, but syslog-ng now compiles with openssl 4 🤩

Last week I asked in a blog about #openssl 4 support and experiences:

https://www.syslog-ng.com/community/b/blog/posts/support-for-openssl-4-0

We received a detailed answer, and also a pull request to the #syslog_ng #GitHub repo. Of course, more investigation is needed, but syslog-ng now compiles with openssl 4 🤩

Last week I asked in a blog about #openssl 4 support and experiences:

https://www.syslog-ng.com/community/b/blog/posts/support-for-openssl-4-0

We received a detailed answer, and also a pull request to the #syslog_ng #GitHub repo. Of course, more investigation is needed, but syslog-ng now compiles with openssl 4 🤩

Last week I asked in a blog about #openssl 4 support and experiences:

https://www.syslog-ng.com/community/b/blog/posts/support-for-openssl-4-0

We received a detailed answer, and also a pull request to the #syslog_ng #GitHub repo. Of course, more investigation is needed, but syslog-ng now compiles with openssl 4 🤩

Last week I asked in a blog about #openssl 4 support and experiences:

https://www.syslog-ng.com/community/b/blog/posts/support-for-openssl-4-0

We received a detailed answer, and also a pull request to the #syslog_ng #GitHub repo. Of course, more investigation is needed, but syslog-ng now compiles with openssl 4 🤩

Как шифровать сообщения в любом мессенджере и соцсети

В нынешних условиях многим пользователям приходится по принуждению использовать незащищённые мессенджеры и социальные сети, то есть скомпрометированные каналы связи. К счастью, есть возможность передавать секретные зашифрованные сообщения по публичным открытым каналам. Это стандартная задача, которая давно решена в криптографии. Более того, зашифрованное сообщение можно сделать похожим на обычный текст или даже скрыть в обычном контенте — видео, звуковых файлах и тексте, который не вызовет подозрений у «цензора». Это область стеганографии Но прямо сейчас людям нужен простой и практичный способ шифровать сообщения, максимально удобным способом. Рассмотрим самые простые онлайновые утилиты, которые позволяют это делать.

https://habr.com/ru/companies/globalsign/articles/1030886/

#шифрование #Paranoia_Text_Encryption #LOCKPUB #GCHQ_CyberChef #AES_Utils #GnuPG #OpenSSL #ccrypt #VeraCrypt #Cryptomator

Как шифровать сообщения в любом мессенджере и соцсети

В нынешних условиях многим пользователям приходится по принуждению использовать незащищённые мессенджеры и социальные сети, то есть скомпрометированные каналы связи. К счастью, есть возможность передавать секретные зашифрованные сообщения по публичным открытым каналам. Это стандартная задача, которая давно решена в криптографии. Более того, зашифрованное сообщение можно сделать похожим на обычный текст или даже скрыть в обычном контенте — видео, звуковых файлах и тексте, который не вызовет подозрений у «цензора». Это область стеганографии Но прямо сейчас людям нужен простой и практичный способ шифровать сообщения, максимально удобным способом. Рассмотрим самые простые онлайновые утилиты, которые позволяют это делать.

https://habr.com/ru/companies/globalsign/articles/1030886/

#шифрование #Paranoia_Text_Encryption #LOCKPUB #GCHQ_CyberChef #AES_Utils #GnuPG #OpenSSL #ccrypt #VeraCrypt #Cryptomator

Как шифровать сообщения в любом мессенджере и соцсети

В нынешних условиях многим пользователям приходится по принуждению использовать незащищённые мессенджеры и социальные сети, то есть скомпрометированные каналы связи. К счастью, есть возможность передавать секретные зашифрованные сообщения по публичным открытым каналам. Это стандартная задача, которая давно решена в криптографии. Более того, зашифрованное сообщение можно сделать похожим на обычный текст или даже скрыть в обычном контенте — видео, звуковых файлах и тексте, который не вызовет подозрений у «цензора». Это область стеганографии Но прямо сейчас людям нужен простой и практичный способ шифровать сообщения, максимально удобным способом. Рассмотрим самые простые онлайновые утилиты, которые позволяют это делать.

https://habr.com/ru/companies/globalsign/articles/1030886/

#шифрование #Paranoia_Text_Encryption #LOCKPUB #GCHQ_CyberChef #AES_Utils #GnuPG #OpenSSL #ccrypt #VeraCrypt #Cryptomator

Как шифровать сообщения в любом мессенджере и соцсети

В нынешних условиях многим пользователям приходится по принуждению использовать незащищённые мессенджеры и социальные сети, то есть скомпрометированные каналы связи. К счастью, есть возможность передавать секретные зашифрованные сообщения по публичным открытым каналам. Это стандартная задача, которая давно решена в криптографии. Более того, зашифрованное сообщение можно сделать похожим на обычный текст или даже скрыть в обычном контенте — видео, звуковых файлах и тексте, который не вызовет подозрений у «цензора». Это область стеганографии Но прямо сейчас людям нужен простой и практичный способ шифровать сообщения, максимально удобным способом. Рассмотрим самые простые онлайновые утилиты, которые позволяют это делать.

https://habr.com/ru/companies/globalsign/articles/1030886/

#шифрование #Paranoia_Text_Encryption #LOCKPUB #GCHQ_CyberChef #AES_Utils #GnuPG #OpenSSL #ccrypt #VeraCrypt #Cryptomator

Error while installing wine on Ubuntu 25.10 #wine #openssl

https://askubuntu.com/q/1566281/612

Error while installing wine on Ubuntu 25.10 #wine #openssl

https://askubuntu.com/q/1566281/612

Error while installing wine on Ubuntu 25.10 #wine #openssl

https://askubuntu.com/q/1566281/612

Error while installing wine on Ubuntu 25.10 #wine #openssl

https://askubuntu.com/q/1566281/612

Error while installing wine on Ubuntu 25.10 #wine #openssl

https://askubuntu.com/q/1566281/612

Although #OpenSSL 4.0 released just two weeks ago, the syslog-ng project has already received a #GitHub issue complaining that we do not support it. So, before we would allocate too much effort on it: what should we expect?

https://www.syslog-ng.com/community/b/blog/posts/support-for-openssl-4-0

#LogManagement #syslog_ng

Although #OpenSSL 4.0 released just two weeks ago, the syslog-ng project has already received a #GitHub issue complaining that we do not support it. So, before we would allocate too much effort on it: what should we expect?

https://www.syslog-ng.com/community/b/blog/posts/support-for-openssl-4-0

#LogManagement #syslog_ng

Although #OpenSSL 4.0 released just two weeks ago, the syslog-ng project has already received a #GitHub issue complaining that we do not support it. So, before we would allocate too much effort on it: what should we expect?

https://www.syslog-ng.com/community/b/blog/posts/support-for-openssl-4-0

#LogManagement #syslog_ng

Although #OpenSSL 4.0 released just two weeks ago, the syslog-ng project has already received a #GitHub issue complaining that we do not support it. So, before we would allocate too much effort on it: what should we expect?

https://www.syslog-ng.com/community/b/blog/posts/support-for-openssl-4-0

#LogManagement #syslog_ng

Although #OpenSSL 4.0 released just two weeks ago, the syslog-ng project has already received a #GitHub issue complaining that we do not support it. So, before we would allocate too much effort on it: what should we expect?

https://www.syslog-ng.com/community/b/blog/posts/support-for-openssl-4-0

#LogManagement #syslog_ng

Pro-Grade Ham Radio Displays: Integrating OpenHamClock into PiSignage

758 words, 4 minutes read time.

A Helping Hand Needed for a Fellow Programmer

I’m reaching out to see if you can lend a hand to a talented software developer who’s currently on the job hunt. With over 30 years of experience in C#, .NET (Core/6–8), REST APIs, SQL Server, Angular/Razor, Kubernetes, and cloud CI/CD, he’s a seasoned pro with a proven track record of leading modernization projects and delivering production systems.

Some of his notable accomplishments include DB2 to SQL migrations, building real-time SignalR apps, and developing full-stack API and frontend projects. Based in Southeast Michigan, he’s looking for senior engineering, architecture, or technical lead roles that will challenge him and utilize his skills.

If you’re in a position to help, you can check out his resume and portfolio at http://charles.friasteam.com.

Let’s all look out for each other – if you know of any opportunities that might be a good fit, could you please consider passing this along to your network?

—

If you are a ham radio operator, you know that a HamClock is the ultimate shack companion. But what if you want to move beyond a dedicated small screen and integrate that data-rich display into a professional digital signage environment?

By using PiSignage, you can rotate your HamClock with other station metrics, weather, or club announcements. However, getting a clean, secure, and “pop-up free” experience requires a few tricks.

In this post, I’ll show you how to deploy OpenHamClock using Docker and how to strip away the UI clutter for a seamless kiosk experience.

The Setup

To follow along, you will need a PiSignage server instance. I personally run mine as a Docker container, which keeps the server stack isolated and easy to back up.

1. The Docker Compose Configuration

PiSignage and modern browsers often require secure contexts (HTTPS) for certain features. Since the standard HamClock output is HTTP, we’ll use a two-service setup: the clock itself and a lightweight SSL-wrap sidecar using socat and openssl.

docker-componse.yml

 services:    openhamclock:      image: ghcr.io/accius/openhamclock:latest      container_name: openhamclock      expose:        - "3000"      environment:        - CALLSIGN=<CALL SIGN>        - LOCATOR=<Grid Square Locator>        - THEME=dark        - UNITS=imperial      restart: unless-stopped     ssl-wrap:      image: alpine      container_name: hamclock-ssl      ports:        - "3000:3000"      command: >        sh -c "apk add --no-cache socat openssl &&                openssl req -x509 -newkey rsa:2048 -keyout /tmp/key.pem -out /tmp/cert.pem -days 365 -nodes -subj '/CN=localhost' &&               cat /tmp/cert.pem /tmp/key.pem > /tmp/combined.pem &&               socat OPENSSL-LISTEN:3000,cert=/tmp/combined.pem,verify=0,fork,reuseaddr TCP:openhamclock:3000"      restart: unless-stopped 

2. Silencing the “What’s New” Pop-ups

When using HamClock as a signage element, you want it to be “set and forget.” The “What’s New” slide-ins are helpful for desktop users but ruin a clean kiosk display.

While there is a formal change request pending for a toggle, you can currently “force” these elements to stay hidden by injecting a bit of CSS directly into the distribution files. Run this command within your app environment:

find /app/dist -name "*.css" -exec sh -c 'echo "div[style*=\"whatsNewSlideIn\"], div[style*=\"backdrop-filter\"] { display: none !important; }" >> {}' \;

3. Setting Up the Slide in PiSignage

Once your containers are humming along, you need to tell PiSignage how to display the clock.

Create the Weblink Asset

1. Log in to your PiSignage Admin Panel.
2. Navigate to Assets > Add > Weblink.
3. Fill in the details:
   • Name: OpenHamClock
   • Link Address: https://<YOUR-HOSTNAME>:3000/?kiosk=true
4. Click Save.

Pro Tip: The ?kiosk=true suffix is critical. It tells HamClock to hide its own internal menus and headers, giving you a dedicated, high-contrast dashboard perfect for a wall-mounted display.

Deploy to Your Player

1. Go to Playlists and add your new “OpenHamClock” asset.
2. Set the Duration: Set this to 0 for a permanent display, or a high number (like 300 for 5 minutes) if it’s part of a rotation.
3. Go to Groups, select your player, and deploy the playlist.

Your screen should refresh and show a beautiful, clean HamClock interface within seconds!

Running PiSignage in Docker?

For those of you looking to keep your entire server stack contained, running the PiSignage central server in Docker is the way to go. It keeps your host OS clean and makes management a breeze.

If you’d like me to discuss how to set up a dockerized PiSignage server, please comment below!

— 73 —

Call to Action

Getting this stack to play nice wasn’t a “one-and-done” install. It was a hard-fought process that took multiple attempts to finally crack the code on bypassing those “What’s New” screens and forcing a clean kiosk display. But the victory is in the uptime.

Don’t just lurk. If you’ve got the guts to show how you’re rebuilding your station on the wreckage of the old ways, drop a comment below. How are you occupying the victory today?

D. Bryan King

Sources

• OpenHamClock GitHub Repository (accius)
• Original HamClock Source by Clear Sky Institute
• PiSignage Official Documentation
• Docker Compose Specification and Documentation
• Alpine Linux Official Docker Image
• Socat Man Page – Multipurpose Relay Tool
• OpenSSL Official Documentation
• Maidenhead Locator System Overview
• Deep Dive: HamClock on Raspberry Pi
• PiSignage Server Docker Implementation
• Raspberry Pi Kiosk Mode Configuration
• MDN Web Docs: CSS Display Property
• Docker CMD vs Entrypoint Explained
• Understanding Self-Signed SSL Certificates
• ARRL: Understanding Grid Squares
• CSS Attribute Selectors (For Style Injection)
• Docker Container Networking Guide
• Linux Find Command Documentation
• Portainer: Managing Dockerized Signage Stacks
• PiSignage Community Support Forum

Disclaimer:

I love sharing what I’m learning, but please keep in mind that everything I write here—including this post—is just my personal take. These are my own opinions based on my research and my understanding of things at the time I’m writing them. Since life moves way too fast and things change quickly, please use your own best judgment and consult the experts for your specific situations!

Related Posts

Rate this:

Pro-Grade Ham Radio Displays: Integrating OpenHamClock into PiSignage

758 words, 4 minutes read time.

A Helping Hand Needed for a Fellow Programmer

I’m reaching out to see if you can lend a hand to a talented software developer who’s currently on the job hunt. With over 30 years of experience in C#, .NET (Core/6–8), REST APIs, SQL Server, Angular/Razor, Kubernetes, and cloud CI/CD, he’s a seasoned pro with a proven track record of leading modernization projects and delivering production systems.

Some of his notable accomplishments include DB2 to SQL migrations, building real-time SignalR apps, and developing full-stack API and frontend projects. Based in Southeast Michigan, he’s looking for senior engineering, architecture, or technical lead roles that will challenge him and utilize his skills.

If you’re in a position to help, you can check out his resume and portfolio at http://charles.friasteam.com.

Let’s all look out for each other – if you know of any opportunities that might be a good fit, could you please consider passing this along to your network?

—

If you are a ham radio operator, you know that a HamClock is the ultimate shack companion. But what if you want to move beyond a dedicated small screen and integrate that data-rich display into a professional digital signage environment?

By using PiSignage, you can rotate your HamClock with other station metrics, weather, or club announcements. However, getting a clean, secure, and “pop-up free” experience requires a few tricks.

In this post, I’ll show you how to deploy OpenHamClock using Docker and how to strip away the UI clutter for a seamless kiosk experience.

The Setup

To follow along, you will need a PiSignage server instance. I personally run mine as a Docker container, which keeps the server stack isolated and easy to back up.

1. The Docker Compose Configuration

PiSignage and modern browsers often require secure contexts (HTTPS) for certain features. Since the standard HamClock output is HTTP, we’ll use a two-service setup: the clock itself and a lightweight SSL-wrap sidecar using socat and openssl.

docker-componse.yml

 services:    openhamclock:      image: ghcr.io/accius/openhamclock:latest      container_name: openhamclock      expose:        - "3000"      environment:        - CALLSIGN=<CALL SIGN>        - LOCATOR=<Grid Square Locator>        - THEME=dark        - UNITS=imperial      restart: unless-stopped     ssl-wrap:      image: alpine      container_name: hamclock-ssl      ports:        - "3000:3000"      command: >        sh -c "apk add --no-cache socat openssl &&                openssl req -x509 -newkey rsa:2048 -keyout /tmp/key.pem -out /tmp/cert.pem -days 365 -nodes -subj '/CN=localhost' &&               cat /tmp/cert.pem /tmp/key.pem > /tmp/combined.pem &&               socat OPENSSL-LISTEN:3000,cert=/tmp/combined.pem,verify=0,fork,reuseaddr TCP:openhamclock:3000"      restart: unless-stopped 

2. Silencing the “What’s New” Pop-ups

When using HamClock as a signage element, you want it to be “set and forget.” The “What’s New” slide-ins are helpful for desktop users but ruin a clean kiosk display.

While there is a formal change request pending for a toggle, you can currently “force” these elements to stay hidden by injecting a bit of CSS directly into the distribution files. Run this command within your app environment:

find /app/dist -name "*.css" -exec sh -c 'echo "div[style*=\"whatsNewSlideIn\"], div[style*=\"backdrop-filter\"] { display: none !important; }" >> {}' \;

3. Setting Up the Slide in PiSignage

Once your containers are humming along, you need to tell PiSignage how to display the clock.

Create the Weblink Asset

1. Log in to your PiSignage Admin Panel.
2. Navigate to Assets > Add > Weblink.
3. Fill in the details:
   • Name: OpenHamClock
   • Link Address: https://<YOUR-HOSTNAME>:3000/?kiosk=true
4. Click Save.

Pro Tip: The ?kiosk=true suffix is critical. It tells HamClock to hide its own internal menus and headers, giving you a dedicated, high-contrast dashboard perfect for a wall-mounted display.

Deploy to Your Player

1. Go to Playlists and add your new “OpenHamClock” asset.
2. Set the Duration: Set this to 0 for a permanent display, or a high number (like 300 for 5 minutes) if it’s part of a rotation.
3. Go to Groups, select your player, and deploy the playlist.

Your screen should refresh and show a beautiful, clean HamClock interface within seconds!

Running PiSignage in Docker?

For those of you looking to keep your entire server stack contained, running the PiSignage central server in Docker is the way to go. It keeps your host OS clean and makes management a breeze.

If you’d like me to discuss how to set up a dockerized PiSignage server, please comment below!

— 73 —

Call to Action

Getting this stack to play nice wasn’t a “one-and-done” install. It was a hard-fought process that took multiple attempts to finally crack the code on bypassing those “What’s New” screens and forcing a clean kiosk display. But the victory is in the uptime.

Don’t just lurk. If you’ve got the guts to show how you’re rebuilding your station on the wreckage of the old ways, drop a comment below. How are you occupying the victory today?

D. Bryan King

Sources

• OpenHamClock GitHub Repository (accius)
• Original HamClock Source by Clear Sky Institute
• PiSignage Official Documentation
• Docker Compose Specification and Documentation
• Alpine Linux Official Docker Image
• Socat Man Page – Multipurpose Relay Tool
• OpenSSL Official Documentation
• Maidenhead Locator System Overview
• Deep Dive: HamClock on Raspberry Pi
• PiSignage Server Docker Implementation
• Raspberry Pi Kiosk Mode Configuration
• MDN Web Docs: CSS Display Property
• Docker CMD vs Entrypoint Explained
• Understanding Self-Signed SSL Certificates
• ARRL: Understanding Grid Squares
• CSS Attribute Selectors (For Style Injection)
• Docker Container Networking Guide
• Linux Find Command Documentation
• Portainer: Managing Dockerized Signage Stacks
• PiSignage Community Support Forum

Disclaimer:

I love sharing what I’m learning, but please keep in mind that everything I write here—including this post—is just my personal take. These are my own opinions based on my research and my understanding of things at the time I’m writing them. Since life moves way too fast and things change quickly, please use your own best judgment and consult the experts for your specific situations!

Related Posts

Rate this:

#OpenSSL 4.0.0 removed all traces of SSL3 support - including the OPENSSL_NO_SSL3_METHOD define that indicates that SSL3 methods are not available.

This define is used by a lot of code to see if they should try to use SSLv3_client_method() or not. Example: https://github.com/mirror/wget/blob/8775506f632f14404e4755dbae679dea07abf12a/src/openssl.c#L229

#OpenSSL 4.0.0 removed all traces of SSL3 support - including the OPENSSL_NO_SSL3_METHOD define that indicates that SSL3 methods are not available.

This define is used by a lot of code to see if they should try to use SSLv3_client_method() or not. Example: https://github.com/mirror/wget/blob/8775506f632f14404e4755dbae679dea07abf12a/src/openssl.c#L229

#OpenSSL 4.0.0 removed all traces of SSL3 support - including the OPENSSL_NO_SSL3_METHOD define that indicates that SSL3 methods are not available.

This define is used by a lot of code to see if they should try to use SSLv3_client_method() or not. Example: https://github.com/mirror/wget/blob/8775506f632f14404e4755dbae679dea07abf12a/src/openssl.c#L229

#OpenSSL 4.0.0 removed all traces of SSL3 support - including the OPENSSL_NO_SSL3_METHOD define that indicates that SSL3 methods are not available.

This define is used by a lot of code to see if they should try to use SSLv3_client_method() or not. Example: https://github.com/mirror/wget/blob/8775506f632f14404e4755dbae679dea07abf12a/src/openssl.c#L229

#OpenSSL 4.0.0 removed all traces of SSL3 support - including the OPENSSL_NO_SSL3_METHOD define that indicates that SSL3 methods are not available.

This define is used by a lot of code to see if they should try to use SSLv3_client_method() or not. Example: https://github.com/mirror/wget/blob/8775506f632f14404e4755dbae679dea07abf12a/src/openssl.c#L229

Build your own secure realm, where the most powerful secret tongues are spoken. #TLS #OpenSSL #cybersecurity #Nginx #OpenSource https://cromwell-intl.com/open-source/nginx-openssl-quantum-safe/oqsprovider-on-freebsd.html?s=mc

Build your own secure realm, where the most powerful secret tongues are spoken. #TLS #OpenSSL #cybersecurity #Nginx #OpenSource https://cromwell-intl.com/open-source/nginx-openssl-quantum-safe/oqsprovider-on-freebsd.html?s=mc

Build your own secure realm, where the most powerful secret tongues are spoken. #TLS #OpenSSL #cybersecurity #Nginx #OpenSource https://cromwell-intl.com/open-source/nginx-openssl-quantum-safe/oqsprovider-on-freebsd.html?s=mc

Build your own secure realm, where the most powerful secret tongues are spoken. #TLS #OpenSSL #cybersecurity #Nginx #OpenSource https://cromwell-intl.com/open-source/nginx-openssl-quantum-safe/oqsprovider-on-freebsd.html?s=mc

Build your own secure realm, where the most powerful secret tongues are spoken. #TLS #OpenSSL #cybersecurity #Nginx #OpenSource https://cromwell-intl.com/open-source/nginx-openssl-quantum-safe/oqsprovider-on-freebsd.html?s=mc

Ah #OpenSSL 4.0.0 est sorti la semaine dernière. Je note :

- Le support de SSLv3 dégage pour de bon
- Arrivée des salutations chiffrées (#ECH)
- Plus de crypto du turfu (post-quantique)

https://github.com/openssl/openssl/releases/tag/openssl-4.0.0

Ah #OpenSSL 4.0.0 est sorti la semaine dernière. Je note :

- Le support de SSLv3 dégage pour de bon
- Arrivée des salutations chiffrées (#ECH)
- Plus de crypto du turfu (post-quantique)

https://github.com/openssl/openssl/releases/tag/openssl-4.0.0

Ah #OpenSSL 4.0.0 est sorti la semaine dernière. Je note :

- Le support de SSLv3 dégage pour de bon
- Arrivée des salutations chiffrées (#ECH)
- Plus de crypto du turfu (post-quantique)

https://github.com/openssl/openssl/releases/tag/openssl-4.0.0

Ah #OpenSSL 4.0.0 est sorti la semaine dernière. Je note :

- Le support de SSLv3 dégage pour de bon
- Arrivée des salutations chiffrées (#ECH)
- Plus de crypto du turfu (post-quantique)

https://github.com/openssl/openssl/releases/tag/openssl-4.0.0

Ah #OpenSSL 4.0.0 est sorti la semaine dernière. Je note :

- Le support de SSLv3 dégage pour de bon
- Arrivée des salutations chiffrées (#ECH)
- Plus de crypto du turfu (post-quantique)

https://github.com/openssl/openssl/releases/tag/openssl-4.0.0

#Linux Weekly Roundup for April 19th, 2026: #LinuxMint 23 development cycle, #KDE Gear 26.04, latest #openSUSE Tumbleweed updates, #Archinstall 4.2, #GNOME 50.1, #Scribus 1.6.6, #ZorinOS 18.1, #GIMP 3.2.4, #Solus 4.9, #OpenSSL 4.0, #RaspberryPi OS 2026-04-13, #Mir 2.26, #COSMIC 1.0.10, new XOrg Server and #Xwayland security releases, #Proton 11 beta, Shelly 2.1, and more https://9to5linux.com/9to5linux-weekly-roundup-april-19th-2026

#OpenSource #FOSS #GNU

#Linux Weekly Roundup for April 19th, 2026: #LinuxMint 23 development cycle, #KDE Gear 26.04, latest #openSUSE Tumbleweed updates, #Archinstall 4.2, #GNOME 50.1, #Scribus 1.6.6, #ZorinOS 18.1, #GIMP 3.2.4, #Solus 4.9, #OpenSSL 4.0, #RaspberryPi OS 2026-04-13, #Mir 2.26, #COSMIC 1.0.10, new XOrg Server and #Xwayland security releases, #Proton 11 beta, Shelly 2.1, and more https://9to5linux.com/9to5linux-weekly-roundup-april-19th-2026

#OpenSource #FOSS #GNU

#Linux Weekly Roundup for April 19th, 2026: #LinuxMint 23 development cycle, #KDE Gear 26.04, latest #openSUSE Tumbleweed updates, #Archinstall 4.2, #GNOME 50.1, #Scribus 1.6.6, #ZorinOS 18.1, #GIMP 3.2.4, #Solus 4.9, #OpenSSL 4.0, #RaspberryPi OS 2026-04-13, #Mir 2.26, #COSMIC 1.0.10, new XOrg Server and #Xwayland security releases, #Proton 11 beta, Shelly 2.1, and more https://9to5linux.com/9to5linux-weekly-roundup-april-19th-2026

#OpenSource #FOSS #GNU

#Linux Weekly Roundup for April 19th, 2026: #LinuxMint 23 development cycle, #KDE Gear 26.04, latest #openSUSE Tumbleweed updates, #Archinstall 4.2, #GNOME 50.1, #Scribus 1.6.6, #ZorinOS 18.1, #GIMP 3.2.4, #Solus 4.9, #OpenSSL 4.0, #RaspberryPi OS 2026-04-13, #Mir 2.26, #COSMIC 1.0.10, new XOrg Server and #Xwayland security releases, #Proton 11 beta, Shelly 2.1, and more https://9to5linux.com/9to5linux-weekly-roundup-april-19th-2026

#OpenSource #FOSS #GNU

#Linux Weekly Roundup for April 19th, 2026: #LinuxMint 23 development cycle, #KDE Gear 26.04, latest #openSUSE Tumbleweed updates, #Archinstall 4.2, #GNOME 50.1, #Scribus 1.6.6, #ZorinOS 18.1, #GIMP 3.2.4, #Solus 4.9, #OpenSSL 4.0, #RaspberryPi OS 2026-04-13, #Mir 2.26, #COSMIC 1.0.10, new XOrg Server and #Xwayland security releases, #Proton 11 beta, Shelly 2.1, and more https://9to5linux.com/9to5linux-weekly-roundup-april-19th-2026

#OpenSource #FOSS #GNU

OpenSSL 4.0 Strengthens Privacy and Removes Legacy Protocols

https://yoota.it/en/openssl-4-0-strengthens-privacy-and-removes-legacy-protocols/

OpenSSL 4.0 Strengthens Privacy and Removes Legacy Protocols

https://yoota.it/en/openssl-4-0-strengthens-privacy-and-removes-legacy-protocols/