Quote:
Originally Posted by donB006
I looked at the /usr/java/lib/security directory inside my K3G immediately after updating to 3.4.2 a few months ago and found this:
Code:
drwxr-xr-x 2 root root 1024 Jun 1 2012 .
drwxr-xr-x 7 root root 1024 Jun 1 2012 ..
-rw-r--r-- 1 1004 5000 48913 Oct 7 09:47 cacerts
-rwxr-xr-x 1 root root 250 Dec 27 2010 java_permissive.policy
-rwxr-xr-x 1 root root 3968 Dec 27 2010 java.policy
-rw-r--r-- 1 root root 8097 Jun 1 2012 java.security
-rwxr-xr-x 1 root root 2915 Jun 1 2012 local_policy.jar
-rwxr-xr-x 1 root root 2433 Jun 1 2012 US_export_policy.jar
The cacerts file seems newer than the rest and might have the certs from the critical update. The DXG stock at 2.5.8 looks like this:
Code:
drwxr-xr-x 2 root root 1024 Jan 13 2011 .
drwxr-xr-x 7 root root 1024 Jan 13 2011 ..
-rwxr-xr-x 1 root root 48913 Jan 13 2011 cacerts
-rwxr-xr-x 1 root root 3238 Jan 13 2011 java.policy
-rw-r--r-- 1 root root 7276 Jan 13 2011 java.security
-rwxr-xr-x 1 root root 2921 Jan 13 2011 local_policy.jar
-rwxr-xr-x 1 root root 2440 Jan 13 2011 US_export_policy.jar
The cacerts file is the same size for 2.5.8 and 3.4.2 at 48913 bytes except with different dates are probably not really the same.
I suppose I can try to transfer the new cacerts from K3G 3.4.2 to my DXG 3.1 and see what happens. Maybe I can figure this out. |
the client certificates are plain text files, look at them in an editor.
