I’m seeing my previous installation in /Library/Developer/CommandLineTools. However, if I run
I’m seeing the installer which tries to fetch the latest Xcode command line tools. However, it always fails with
Unable to Download App. "Xcode" could not be installed. Please try again later.
I don’t intend to install the large Xcode from the appstore. So I’ve tried to delete the existing installation of the command line tools with
sudo rm -rf /Library/Developer
but the problem is still present.
Many people suggest to go to the developer.apple.com page and to search manually for the Xcode command line tools. I thought this wouldn’t work, because I’m only seeing the Xcode command line tools for Xcode 12.
However, we’re already at Xcode 12.1, so I thought this is the wrong download and is already outdated. But after I’ve installed the tools from this dmg, its working again and
xcode-select: error: command line tools are already installed, use "Software Update" to install updates
shows a suitable error message.
So lessons learned: using the latest major version of the command line tools installer seems to be sufficient.
The action can be one of these, whereby I’ve chosen action_mwl:
action_: ban only the IP
action_mw: ban the IP and send email with whois information about the banned IP
action_mwl: ban the IP and send email with whois information about the banned IP and add relevant log lines to the email
action_cf_mwl: notify Cloudfare about the offending IP, ban the IP and send email with whois information about the banned IP
Do a restart of fail2ban:
sudo systemctl restart fail2ban
You’ll receive a lot of emails from fail2ban. This also includes any starts and stops of fail2ban as well as the ban notifications. You can limit this behavior by adding following content to the file /etc/fail2ban/action.d/mail-buffered.local:
# Option: actionstart
# Notes.: command executed once at the start of Fail2Ban.
# Values: CMD
# Option: actionstop
# Notes.: command executed once at the end of Fail2Ban
# Values: CMD
Now copy this file a few times with different file names:
If you’ll open SSH on a server to the open internet, you’ll notice a lot of bots trying to login. You certainly should setup certificate based login, but banning offending IPs is also an important security measure.
I’ve installed fail2ban on my Raspbian installations and want to explain the installation and configuration. Its quite easy and the benefits are huge!
sudo apt-get install fail2ban
Create a copy of the original configuration file so that it won’t be overwritten by any updates:
I’ve intended to disable all comment or trackback functionality to avoid having spam and dealing with it in form of anti-spam plugins like Akismet. While I already had comments disabled, Trackbacks were still active.
Even when you disable Trackbacks in the WordPress settings via “Settings / Discussion” under “Allow link notifications from other Weblogs (Pingbacks and Trackbacks)”, your existing pages needs manual update to take effect.
Connect to your MySQL database of your blog (e.g. with PHPMyAdmin) and execute these two queries:
UPDATE wp_posts set ping_status='closed' WHERE post_status='publish' AND post_type='post';
UPDATE wp_posts set ping_status='closed' WHERE post_status='publish' AND post_type='page';
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.