When I try to connect to my monitoring system with desktop widget Nagstamon, Nagstamon was not able to connect due to SSL certificate validation problem. I’m using certificate from CAcert.org. After a while of hacking I have found this workaround in source code. This is the wrong way:
I bought a new hard drive. Because I protect all my harddisk with encryption, I setup LUKS for new harddrive too. But init scripts ask password for every encrypted partition and I want to enter my harddisk password only once. I have started with googling but I wasn’t succesfull. I have found this thread about the same problem. But the author didn’t provide a patch, and the uploaded *.tar.gz archive is no longer available.
Do you need to discover what IP netblocks are owned and operated by Google to perhaps add to your firewall ACLs? With dynamic zones available in Shorewall, you are able to define firewall rules and to filter network traffic based on the domain name. For example, you can permit IMAPS connection only to gmail.com domain. Problem is that Google cluster is very big and you are always connecting to different IP address. So you can’t define static rules for traffic filtering. Here is little HOWTO do this.
Na kontrolu SSL certifikátu použijeme známy nástroj :
openssl s_client -starttls xmpp -connect jabber.hostname.sk:5222