
The Monkey Business
Seperate Private Key and Certificate file
#Generate certificates bundle file
openssl pkcs12 -nokeys -in server-cert-key-bundle.p12 -out server-ca-cert-bundle.pem
#Generate server key file.
openssl pkcs12 -nocerts -nodes -in server-cert-key-bundle.p12 -out server.key
Convert a PKCS#12 file (.pfx .p12) containing a private key and certificates to PEM
openssl pkcs12 -in keyStore.pfx -out keyStore.pem -nodes
Create a .pfx/.p12 certificate file using OpenSSL
openssl pkcs12 -export -out certificate.pfx -inkey privateKey.key -in certificate.crt
Src: https://www.sslshopper.com/article-most-common-openssl-commands.html
Was just playing around. It’s a great home entertainment tool indeed.
Method-1: Creating repository and using Yum
To enable the Plex repository open your text editor and create a new YUM repository configuration file named plex.repo in /etc/yum.repos.d/ directory:
[PlexRepo] name=PlexRepo baseurl=https://downloads.plex.tv/repo/rpm/$basearch/ enabled=1 gpgkey=https://downloads.plex.tv/plex-keys/PlexSign.key gpgcheck=1
Method-2: Installation using RPM
download the package for your Linux distro. It is much easier to do this by simply coping the download link location with right click and then you can run:
$ sudo rpm -ivh https://downloads.plex.tv/plex-media-server/1.13.8.5395-10d48da0d/plexmediaserver-1.13.8.5395-10d48da0d.x86_64.rpm
Alternatively, you can download the package on your system with wget command as shown.
$ wget https://downloads.plex.tv/plex-media-server/1.13.8.5395-10d48da0d/plexmediaserver-1.13.8.5395-10d48da0d.x86_64.rpm
If you’ve used install base using yum repo- you now need to install it, otherwise if you’re with RPM installation, you already have plex installed. Continue reading “Install Plex on CentOS 7” »
If you ever encounter similar issue like below-
Get more security updates through Ubuntu Pro with 'esm-apps' enabled: libavformat58 libavfilter7 ffmpeg mc sntp libswresample3 lynx-common libzmq5 fail2ban mc-data redis lynx libpostproc55 ntp ntpdate libgsasl7 redis-tools cpanminus libavcodec58 libavutil56 libavdevice58 libswscale5 libsdl2-2.0-0 libmysofa1 redis-server libavresample4
And don’t like to be financially trapped into Ubuntu long term commercials, do this (Kidding, it’s actually good to keep the esm as it’s worth for expanded security)-run command to navigate to that directory: Continue reading “Get rid of esm-apps while ubuntu updates” »
If you ever encounter with such similar of an error (in my case it occurred on my Ubuntu 20 distro), you may apply the following process to get a fix.
The error:
Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: apt apt-transport-https apt-utils dpkg libapt-inst2.0 libapt-pkg5.0 ntpdate oracle-java8-installer oracle-java8-set-default thermald 10 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/4,389 kB of archives. After this operation, 8,192 B of additional disk space will be used. Do you want to continue? [Y/n] Y Preconfiguring packages ... dpkg: unrecoverable fatal error, aborting: files list file for package 'linux-generic' is missing final newline E: Sub-process /usr/bin/dpkg returned an error code (2)
Disclaimer: it worked for me, that doesn’t necessary means that would work same for you! However, you may give it a try. Continue reading “Troubleshooting ubuntu: dpkg: unrecoverable fatal error, aborting: files list file for package ‘linux-generic’ is missing final newline” »
Prerequisites:
XRDP is an open-source version of the Microsoft Remote desktop Protocol server. It enables operating systems besides Microsoft Windows to offer a fully functional remote desktop experience. The prerequisites for the installation include:
Before all else, install Gnome GUI on CentOS 7 or RHEL 7.
Then install and configure EPEL repository with this commandrpm -Uvh https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm Continue reading “Install XRDP on CentOS 7” »
Disclaimer:
This howto is tested on Ubuntu 16, 18, 20 and Debian 10, 11 edition.
Installing and configuring postfix
Step 1 » Assign static IP and hostname and add a host entry for the host name .
Assign hostname in /etc/hostname
mail.tweenpath.net
Add a host entry in /etc/hosts
192.168.1.10 mail.tweenpath.net
Step 2 » Update the repositories.
tweenpath@mail:~$ sudo apt-get update
Step 3 » Install postfix and dependencies . Press enter for all prompted questions during installation. we will do that in the next step.
tweenpath@mail:~$ sudo apt-get install postfix
Step 4 » After installation issue the below command to configure postfix.
tweenpath@mail:~$ sudo dpkg-reconfigure postfix
Now you will be prompted for set of details . choose the following values and replace tweenpath.net with your domain name. Continue reading “Install mail server on Ubuntu or Debian” »
For activating module accounting, open webui via browser
http://>zimbra-host>:7780/webui/index.php
choose accounting | configure. Select add, and fill with the following example
Name : Rate limit perday Link to policy : Default Track : Sender:@domain . You can choose with your choice Period : Daily Message Count Limit : 5000 Message Cumulative Size Limit : empty. I am not using cumulative size Verdict : HOLD. Data : You can fill with information if policy has been fulfilled. for example, you can fill with "Sorry, your maximum email perday have been full" Stop processing here : No Comment : You can fill with comment or emptied Disabled : No
If no tables for module accounting and get information “no such table” while create rule, you can manually adding tables accounting to sqlite. Continue reading “Limit Sending/Receipt Email Per day, Per Week or Per Month” »
Policyd have module quotas. This module can use for limit sending/receipt email. As example just allow sending/receipt email 200 emails/hours/users. If your email server attacked by spam or compromised password some users and used by spammer, the maximum email can be sent as many as 200 emails per hour. This policy will safe your IP public from blacklist on RBL. Besides, you can check who user send email with many email
How To Install Policyd on Zimbra
This guidance is step by step how to install policyd on Zimbra 8.5 and latest
su - zimbra zmprov ms `zmhostname` +zimbraServiceInstalled cbpolicyd +zimbraServiceEnabled cbpolicyd
Activate Policyd WebUI
– For Zimbra 8.5/8.6
Run the following command as root
cd /opt/zimbra/httpd/htdocs/ ln -s ../../cbpolicyd/share/webui .
Edit file /opt/zimbra/cbpolicyd/share/webui/includes/config.php and putting “#” on front of all the lines beginning with $DB_DSN and adding the following line just before the line beginning with $DB_USER. Continue reading “Install PolicyD on Zimbra 8.5 or 8.8” »
Below is how to install and configure Fail2Ban for Zimbra. In this guidance, I use CentOS. Please adjust python-pip version if using another OS
1. Install pip
yum install python3-pip
2. Install dependencies required by Fail2Ban
pip3 install pyinotify pip3 install dnspython
3. Download and extract Fail2Ban
cd /tmp/ wget -c https://github.com/fail2ban/fail2ban/archive/0.9.4.tar.gz
4. Install Fail2Ban
tar -xvf 0.9.4.tar.gz cd fail2ban-0.9.4 python3 setup.py install
5. Copy Fail2Ban service to systemd
cp files/fail2ban.service /usr/lib/systemd/system/
6. Adjust bin location on Fail2Ban service
vi /usr/lib/systemd/system/fail2ban.service
Adjust the following lines. Change /usr/bin become /usr/local/bin Continue reading “Install and Configure Fail2Ban for Zimbra on CentOS 7” »
First, you must register to get a download link: zextras-theme-zimbra-interface. Then, you will receive instructions for installing the new Zextras theme
For Ubuntu users
Download the package from your Zimbra server using the following command:
wget https://link-download-from-zextras/zextras-theme-ubuntu.tgz
Note: Change link-download-from-zextras with the link received in the email
Extract the package you have just downloaded with
tar xvf zextras-theme-ubuntu.tgz
Execute the installation Continue reading “Zextras Modern Theme for Zimbra web interface” »
Step 1: Check the VirtualBox Version (Optional)
First, check out the Virtualbox installed version by specifying the application package name as “vboxmange” name with the “version” flag:
$ vboxmanage --version
The Virtualbox installed version is “6.1.38”.
Step 2: Uninstall Virtual Box
Use the default package manager alongside the “–remove” and “–purge” flags to completely remove the “VirtualBox” tool.
The “–remove” flag will remove the installation files, and the “–purge” will uninstall the configuration files. The “purge” flag is not used in Fedora/CentOS/RHEL because its “remove” flag completely deletes all the files of the package:
$ sudo dnf remove virtualbox #For CentOS/RHEL $ sudo dnf remove virtualbox #For Fedora $ sudo apt --purge remove virtualbox #For Ubuntu/Debian-Based
The highlighted section confirms that all the installation and configuration files of Virtualbox have been removed.
Step 3: Remove VirtualBox Dependencies
When an application is installed in the Linux system, additional dependencies are installed. Execute the “autoremove” command to remove the additional dependencies of Virtualbox:
$ sudo yum autoremove virtualbox #For CentOS/RHEL $ sudo apt autoremove virtualbox #For Ubuntu/Debian-Based $ sudo dnf autoremove virtualbox #For Fedora
The Virtualbox dependencies have also been removed completely.
Step 4: Delete All Virtual Machines
The Virtualbox contains the virtual machine occupying a specific size in the virtual hard drives. By default, the virtual machines of VirtualBox are created in the “Home” directory, while it can be different in your case. So, use the path of the virtual machines as per your system.
To delete these files and settings, run the “rm(remove)” command with the combination of “R(recursively) and “f(forcefully)” flags in this way:
$ sudo rm ~/"VirtualBox VMs" -Rf $ sudo rm ~/.config/VirtualBox/ -Rf
The first command deletes the virtual machine’s files, and the second removes their setting from the virtual hard drive.
Step 4: Verify the VirtualBox
Verify the “VirtualBox” uninstallation process by again executing the “version” command on the terminal:
$ vboxmanage --version
It is verified that “VirtualBox” has been completely removed from the Linux system.
Src: