Categories
macOS

Snippet Managers and Secure Input

I use two different snippet managers, Alfred and Dash, and occasionally they stop working. I recently discovered that this is due to secure input being enabled by an app or the macOS loginwindow.

Some snippet managers will show you a dialog box with a helpful error message, like the one below, but others do not.

One of the apps you have open has enabled secure input, which means Dash is not able to expand snippets or search using selected text. This usually is not a problem (apps enable and disable secure input all the time). However, if you are not able to expand snippets or search using selected text at all, it means one of your open apps enabled secure input and forgot to turn it off.

It’s easy to overlook the name of the app in the dialog box, so look carefully. Simply closing the app or saving the item being edited will allow the snippet manager to start working again. In the case of the macOS loginwindow I find that locking and unlocking my Mac will clear the secure input status.

Secure Input Enabled for 1Password 7
Secure Input Enabled for System Preferences

Categories
macOS

Suppress Catalina zsh Nag Notification

Found a simple way to suppress the macOS nag for zsh by adding the following line to my .bash_profile.

export BASH_SILENCE_DEPRECATION_WARNING=1
Categories
Security

Restore www and https:// in the Google Chrome Location Bar

After Chrome 76, Google stopped displaying the following in the location bar.

http://
https://
www.
/ (the trailing slash)

For a little while there was a Chrome flag that would enable you to restore this important information, but now that’s been removed from Chrome as well.

chrome://flags/#omnibox-ui-hide-steady-state-url-trivial-subdomains

The best option I’ve found to restore this information in the Google Chrome location bar is Google’s Suspicious Site Reporter extension.

Categories
macOS

Google Chrome Remote Desktop

Google Chrome Remote Desktop

Categories
https

Automating Certbot Renewals

I was renewing my Let’s Encrypt certificates using the cron entry below, but this was problematic, as I was turning Apache off/on with each attempt, whether or not there was a certificate update available.

42 3 * * * root /usr/sbin/apache2ctl stop; /opt/certbot-auto renew >> /var/log/certbot-auto.log; /usr/sbin/apache2ctl start;

After checking with a co-worker and reading the documentation, I found a better way to automate my Let’s Encrypt certificates.

42 3 * * * root /opt/certbot-auto renew --pre-hook "/usr/sbin/apache2ctl stop" --post-hook "/usr/sbin/apache2ctl start" >> /var/log/certbot-auto.log`

Using this method, Apache will only stop/start if there is a certificate renewal required.