Bug 1303283

The right file is copied over; check the contents of the java.security files after install.

# The pretrans lua scriptlet prevents an unmodifiedk ava.security                                                              
# from being replaced via an update. It gets created as                                                                        
# java.security.rpmnew instead. This invalidates the patch of                                                                  
# JDK-8061210 of the January 2015 CPU, JDK-8043201 of the                                                                      
# July 2015 CPU and JDK-8141287 of the January 2016 CPU. We                                                                    
# fix this via a post scriptlet which runs on updates.                                                                         
if [ "$1" -gt 1 ]; then
  javasecurity="%{_jvmdir}/%{uniquesuffix}/jre/lib/security/java.security"
  sum=$(md5sum "${javasecurity}" | cut -d' ' -f1)
  # This is the md5sum of an unmodified java.security file                                                                     
  if [ "${sum}" = '1690ac33955594f71dc952c9e83fd396' -o \\
       "${sum}" = 'b138695d0c0ea947e64a21a627d973ba' -o \\
       "${sum}" = 'd17958676bdb9f9d941c8a59655311fb' -o \\
       "${sum}" = '5463aef7dbf0bbcfe79e0336a7f92701' -o \\
       "${sum}" = '400cc64d4dd31f36dc0cc2c701d603db' -o \\
       "${sum}" = '321342219bb130d238ff144b9e5dbfc1' ]; then
    if [ -f "${javasecurity}.rpmnew" ]; then
      mv -f "${javasecurity}.rpmnew" "${javasecurity}"
    fi
  fi
fi

I believe there's already a bug to fix this properly, but I can't see it. Assigning to Jiri to look at it.

Yes the bug is
https://bugzilla.redhat.com/show_bug.cgi?id=1183793

I time stmaped the java.security today. Maybe it will magicaly fix the issue as it did for repcked policies. But I doubt, and generally I dont know simple way out.

*** This bug has been marked as a duplicate of bug 1183793 ***

I can't see that bug as it is restricted to internal Red Hat users. Can you keep this bug open for Fedora until it is corrected and tested?

Well, yes. Problem is, that I don know solution for now. Every solution which crossed my mind is close to be unmaintainable (as current md5sum list...). So this bug may be lingering open around for pretty long time. Sorry for inconvenience.

This bug is getting slightly out of hand. On a machine that was upgraded, over time, from F22 to F24:

[root@monster ~]# ls /usr/lib/jvm/*/jre/lib/security/java.security.rpm*
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.60-14.b27.fc22.x86_64/jre/lib/security/java.security.rpmnew
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.60-14.b27.fc22.x86_64/jre/lib/security/java.security.rpmsave
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-13.b17.fc23.x86_64/jre/lib/security/java.security.rpmnew
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-13.b17.fc23.x86_64/jre/lib/security/java.security.rpmsave
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-15.b17.fc23.x86_64/jre/lib/security/java.security.rpmnew
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-15.b17.fc23.x86_64/jre/lib/security/java.security.rpmsave
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-3.b17.fc22.x86_64/jre/lib/security/java.security.rpmnew
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-3.b17.fc22.x86_64/jre/lib/security/java.security.rpmsave
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-3.b17.fc23.x86_64/jre/lib/security/java.security.rpmnew
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-3.b17.fc23.x86_64/jre/lib/security/java.security.rpmsave
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-4.b17.fc23.x86_64/jre/lib/security/java.security.rpmnew
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-4.b17.fc23.x86_64/jre/lib/security/java.security.rpmsave
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.71-1.b15.fc23.x86_64/jre/lib/security/java.security.rpmnew
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.71-1.b15.fc23.x86_64/jre/lib/security/java.security.rpmsave
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.72-4.b15.fc23.x86_64/jre/lib/security/java.security.rpmnew
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.72-4.b15.fc23.x86_64/jre/lib/security/java.security.rpmsave
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.72-9.b16.fc23.x86_64/jre/lib/security/java.security.rpmnew
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.72-9.b16.fc23.x86_64/jre/lib/security/java.security.rpmsave
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.77-1.b03.fc23.x86_64/jre/lib/security/java.security.rpmnew
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.77-1.b03.fc23.x86_64/jre/lib/security/java.security.rpmsave
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-2.b14.fc23.x86_64/jre/lib/security/java.security.rpmnew
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-2.b14.fc23.x86_64/jre/lib/security/java.security.rpmsave
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-5.b14.fc23.x86_64/jre/lib/security/java.security.rpmnew
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-5.b14.fc23.x86_64/jre/lib/security/java.security.rpmsave
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-6.b14.fc23.x86_64/jre/lib/security/java.security.rpmnew
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-6.b14.fc23.x86_64/jre/lib/security/java.security.rpmsave
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.92-1.b14.fc23.x86_64/jre/lib/security/java.security.rpmnew
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.92-1.b14.fc23.x86_64/jre/lib/security/java.security.rpmsave
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.92-1.b14.fc24.x86_64/jre/lib/security/java.security.rpmnew

Hello. My apologise. I'm aware of this misbehaviour (it happens only under some circumstances [actually in deep past]) And I don't know the cure.
 
If you remove all old, unsused /usr/lib/jvm/java-1.8.0-openjdk* (all except latest) AND inside the latest one remove any rpmnew/rpmsave/rpmwhatever files, you will never see this again.

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

(In reply to jiri vanek from comment #6)
> Hello. My apologise. I'm aware of this misbehaviour (it happens only under
> some circumstances [actually in deep past]) And I don't know the cure.
>  
> If you remove all old, unsused /usr/lib/jvm/java-1.8.0-openjdk* (all except
> latest) AND inside the latest one remove any rpmnew/rpmsave/rpmwhatever
> files, you will never see this again.

I tried to do that and it happened again recently:

Scriptlet output:
   1 warning: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.111-3.b16.fc25.x86_64/jre/lib/security/java.security created as /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.111-3.b16.fc25.x86_64/jre/lib/security/java.security.rpmnew

These messages occur on dnf transaction, here is the most recent one:

Scriptlet output:
   1 warning: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.111-4.b16.fc25.x86_64/jre/lib/security/java.security created as /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.111-4.b16.fc25.x86_64/jre/lib/security/java.security.rpmnew

But directories does not contain rpmnew or rpmsave, so not sure why this message occurred. I don't remember removing these manually.

$ ls /usr/lib/jvm/*/jre/lib/security/java.security*
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.111-4.b16.fc25.x86_64/jre/lib/security/java.security

Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.