macOS Finder – File Extension Not Hiding

I tried to recreate your Problem and noticed that you probably have not enabled the "Show all File Extensions" option in the Finder Preferences.

You can check by selecting the Finder and selecting "Preferences" from the Menubar. A small window should appear, titled "Finder Preferences". Select the "Advanced" Icon at the Top of that window. You should now see the option "Show all File Extensions", it should be checked. All files in your finder window should now show their extensions, like .txt or in your case .crt

You can now easily change all files to another extension.

If that does not work then the Fileextension is probably linked to another application. .crt-Files should link to the Keychain-Application which handels all certificates. You can check by selecting the crt-File and pressing "command" + "i". An information window should appear with additional information to that file. At the Entry "open with" should appear "Keychain.app".

There is not a safe and advisable way to achieve what you are after because this function of the OS is controlled by the Launch Services database. Developers register the filetypes their applications support with the OS on first launch.

The best way to get this fixed is to petition the developer to add support for the file extension in a future version of their application.

With that said you have already found the only documented way that Apple offers for overriding the edicts of the Launch Services database. If you want to dig deeper and take the road less traveled supported here are a few pointers.

There is a .plist file that governs part of what Launch Services does located at: ~/Library/Preferences/com.apple.LaunchServices.plist

Apple notes that removing this plist can clear out unwanted Open With contextual menu options. But that's the opposite of what you're after.

It's a binary .plist but you could convert it to an xml version and experiment a little to see if you can come up with a recipe to achieve what you're after. This isn't advisable, it could cause harm, and it will most likely get overwritten by the OS at some point.

There is also a tool hidden a bit deeper in the OS called lsregister which could be helpful in exploring Launch Services's plumbing. Here is a helpful explanation of lsregister and its options.