similar to: how to compile a working icecast against openssl

Hi > A. Where can I get a cert for my icecast server? look here https://letsencrypt.org/ you can use certbot command to obtain certificate for your domain > B. How to re-do the current icecast server enhanced with the cert? in yor settings add ... <listen-socket> <port>8001</port> <ssl>1</ssl> </listen-socket> ...

Terve, I used You guidance and yes… version 2.4.4 Now I have one new line on error.log WARN connection/get_ssl_certificate Invalid cert file /usr/share/icecast2/icecast.pem It might be that Michel van Dop was right… This is how I generated the cert: openssl req -new -newkey rsa:2048 -days 365 -nodes -x509 -keyout icecast2.pem -out icecast2.pem Have I done something wrong? There is still

First I would recommend to run make uninstall from the location you ran make install before to clean up what it already installed in the wrong location. Then repeat the ./configure ... step but without the prefix: ./configure --with-curl --with-openssl then make and make install, which should install Icecast to /usr/local with the Icecast binary in /usr/local/bin and the configuration

I am struggling to get icecast running with https, but I cannot get it working My environment is: Debian 10 (Buster) I tried the standard debian package but there is no SSL capability at all. So I compiled the icecast-2.4.4.tar.gz contents with ./configure --with-curl --with-openssl; make; make install I always get the error: [2020-02-05 17:35:36] INFO connection/get_ssl_certificate

On 17 Oct 2020, at 15:14, Bananradion wrote: > I tried that, but i'm not sure what´s supposed to happen after "make > install" is done? Nothing us supposed to happen afterwards. The log you posted looks like it successfully installed everything. > > Making install in examples > make[1]: Entering directory '/home/pi/icecast-2.4.4/examples' > make[2]:

Greetings all, I have verified a bug that has long been attributed to lack of knowledge on the part of the user. Dovecot rejects StartSSL client certificates due to reject StartSSL root CA when doing client verification even though the appropriately constructed ca-bundle.pem has been created and applied vi ssl_ca = </etc/dovecot/ca-bundle.pem. openssl verify -CAfile ca-bundle.pem

I am struggling to get icecast running with https, but I cannot get it working My environment is: Debian 10 (Buster) Question 1: I tried the standard debian icecast2 package but there is no SSL capability at all. Is there a reason for this ? The icecast documentation mentions: Packages are built with openSSL enabled. Question 2: I tried to compile the latest version from github

No, I don't have centovacast.. i just want to use icecast with ices2. But icecast has to have ssl enabled. Den lör 17 okt. 2020 kl 13:55 skrev Marvin Scholz <epirat07 at gmail.com>: > Hi, > > the guide you followed is not really correct for the usecase you have > unless you use CentovaCast, which I guess you do not? > > On 17 Oct 2020, at 13:19, Bananradion wrote:

On 11/13/18 19:58, Aki Tuomi wrote: > On 13 November 2018 at 20:53 Arkadiusz Mi?kiewicz wrote: >> I'm considering dovecot migration from 2.2.36 run with openssl 1.0.2o to >> dovecot 2.3.3 run with openssl 1.1.1. >> >> Currently I have both variants running with identical configs and certs >> (the only differences are due to config syntax changes in dovecot

Hello everyone. Thanks a lot! I got it working. Frankly speaking I had already tested the setup proposed, but I made two mistakes, first i tried to setup the port 443 and it was stupid as this port is already used by web service https. Second mistake was the .pem file that probably was wrongly concatenated and was not recognized/loaded by icecast. However I confirm that in most places on

I tried that, but i'm not sure what´s supposed to happen after "make install" is done? Making install in examples make[1]: Entering directory '/home/pi/icecast-2.4.4/examples' make[2]: Entering directory '/home/pi/icecast-2.4.4/examples' make[2]: Nothing to be done for 'install-exec-am'. make[2]: Nothing to be done for 'install-data-am'. make[2]:

Here you go: - https://serverok.in/centovacast-enable-ssl-on-icecast No problem, you're welcome! Chip Scooter On Wed, 5 Feb 2020 at 18:41, Henk van de Ridder <henk.vande.ridder at solcon.nl> wrote: > I am struggling to get icecast running with https, but I cannot get it > working > > My environment is: Debian 10 (Buster) > > > > I tried the standard

Hi, the guide you followed is not really correct for the usecase you have unless you use CentovaCast, which I guess you do not? On 17 Oct 2020, at 13:19, Bananradion wrote: > Thanks for the fast reply, but that didn't help either. > > What is supposed to happened after "make install" > I see: > > Making install in examples > make[1]: Entering directory

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> <br> </div> <blockquote type="cite"> <div> On 13 November 2018 at 20:53 Arkadiusz Miśkiewicz < <a href="mailto:arekm@maven.pl">arekm@maven.pl</a>> wrote: </div> <div>

Main question: is it safe, to open a port for an openssl server? e.g.: server side - generate a self-signed cert. time openssl req -x509 -nodes -days 365 -newkey rsa:8192 -keyout mycert.pem -out mycert.pem openssl s_server -accept 52310 -cert mycert.pem Is it secure? - it could be DOSed' [DenialofService] or could it be attacked in any way? Are there any iptables rule for restricting

Thanks for the fast reply, but that didn't help either. What is supposed to happened after "make install" I see: Making install in examples make[1]: Entering directory '/usr/local/src/icecast-2.4.4/examples' make[2]: Entering directory '/usr/local/src/icecast-2.4.4/examples' make[2]: Nothing to be done for 'install-exec-am'. make[2]: Nothing to be done for

i can use "natively" openssl for anonymous chat: # Chat: # server side: openssl req -x509 -nodes -days 365 -newkey rsa:8192 -keyout mycert.pem -out mycert.pem # server side - generate a self-signed cert. openssl s_server -accept 52310 -cert mycert.pem # client side - "127.0.0.1" is the IP of the server openssl s_client -connect 127.0.0.1:52310 1) but how can i set it to

hello, I made a modification to ssl-proxy-openssl.c (patch attached) zo that it a) disconnects when no client certificate is presented b) checks the client certificate against the crl for our root cert. (so you can't use a revoked client cert.) c) returns the CommonName from the client cert. in ssl_proxy_get_peer_name (this way it's easier to use dovecot as imap-proxy with a

Hi. I'm considering dovecot migration from 2.2.36 run with openssl 1.0.2o to dovecot 2.3.3 run with openssl 1.1.1. Currently I have both variants running with identical configs and certs (the only differences are due to config syntax changes in dovecot 2.3), so for example on both I have: ssl_ca = </etc/openssl/certs/wildcard_ca.pem (this file contains single intermediate certificate of

I copy certificate.crt and private.key to one file and this file convert to .pem. This is in icecast error.log: [2020-06-11 13:37:30] INFO main/main.c Icecast 2.4.4 server started [2020-06-11 13:37:30] INFO yp/yp.c YP update thread started [2020-06-11 13:37:30] WARN connection/connection.c Invalid private key file ./cert/icecast.pem [2020-06-11 13:37:30] INFO connection/connection.c No SSL