Taking a closer look ls -al $( find . | grep java.security ) -rw-r--r-- 1 root root 20K Dec 17 09:02 ./java-1.8.0-openjdk-1.8.0/jre/lib/security/java.security -rw-r--r-- 1 root root 21K Jan 22 09:34 ./java-1.8.0-openjdk-1.8.0/jre/lib/security/java.security.rpmnew that appears to demonstrate that existing 'java.security' IS preserved (any new installed java.security is installed as *.rpmnew ?) Iiuc, that'll be true only as long as we're within the "1.8.0" namespace, given ls -al total 244K drwxr-xr-x 3 root root 4.0K Jan 27 07:08 ./ drwxr-xr-x 264 root root 232K Jan 26 17:21 ../ lrwxrwxrwx 1 root root 32 Nov 2 10:40 java-1.8.0 -> /etc/alternatives/java_sdk_1.8.0/ lrwxrwxrwx 1 root root 24 Jan 23 05:50 java-1.8.0-openjdk -> java-1.8.0-openjdk-1.8.0/ drwxr-xr-x 7 root root 4.0K Jan 22 11:00 java-1.8.0-openjdk-1.8.0/ lrwxrwxrwx 1 root root 34 Nov 2 09:42 java-openjdk -> /etc/alternatives/java_sdk_openjdk/ lrwxrwxrwx 1 root root 27 Nov 2 10:33 jre-1.8.0 -> /etc/alternatives/jre_1.8.0/ lrwxrwxrwx 1 root root 28 Jan 23 05:50 jre-1.8.0-openjdk -> java-1.8.0-openjdk-1.8.0/jre/ lrwxrwxrwx 1 root root 29 Jun 11 2014 jre-openjdk -> /etc/alternatives/jre_openjdk/ As soon as 1.8.0 updates to > 1.8.0, then changes to the java.security file will need to remade. Is that correct? If so, what's the namespace policy? will the dirnames stay at *1.8.0* for the entire 1.8.x branch future? As for Oracle, that's of course, rpm-installed from their site. At first glance, the as-shipped 'java.security' file is identical to that of openjdk1.8's. Fwiw, this is all a bit muddled anyway as (1) current opensuse's distro-shipped bouncycastle pkg is INCOMPATIBLE with jdk 1.8.x (both openjdk & Oracle) anyway (https://bugzilla.suse.com/show_bug.cgi?id=914685), (2) BC's not Oracle/Sun-signed, so it can't be persistently added to Oracle's lib/ext install path -- only to OpenJDK's.