Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-3681

Not All Cipher Algorithms Work For Encrypting Property Placeholders

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • jboss-fuse-6.2.1
    • jboss-fuse-6.2
    • Security
    • None
    • Documentation (Ref Guide, User Guide, etc.)
    • % %
    • Hide

      Follow the steps outlined in section 2.3 of the Fuse 6.2 Security Guide (1) to encrypt a property placeholder in the activemq.xml file. Choose one of the stronger ciphers like, PBEWITHHMACSHA224ANDAES_128. When starting the Fuse container, the broker will not start because of the following exception:

      org.jasypt.exceptions.EncryptionOperationNotPossibleException
	at org.jasypt.encryption.pbe.StandardPBEByteEncryptor.decrypt(StandardPBEByteEncryptor.java:1055)[26:org.apache.servicemix.bundles.jasypt:1.9.2.1]
	at org.jasypt.encryption.pbe.StandardPBEStringEncryptor.decrypt(StandardPBEStringEncryptor.java:725)[26:org.apache.servicemix.bundles.jasypt:1.9.2.1]
	at org.jasypt.properties.PropertyValueEncryptionUtils.decrypt(PropertyValueEncryptionUtils.java:72)[26:org.apache.servicemix.bundles.jasypt:1.9.2.1]
	at org.jasypt.spring31.properties.EncryptablePropertyPlaceholderConfigurer.convertPropertyValue(EncryptablePropertyPlaceholderConfigurer.java:109)[187:org.apache.servicemix.bundles.jasypt-spring31:1.9.2.1]

      If you revert back to one of the weaker ciphers, the exception no longer occurs. I have attached an example activemq.xml and corresponding properties file that includes the encrypted password.

      (1) https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.2/html/Security_Guide/FMQSecurityEncryptProperties.html

      Show
      Follow the steps outlined in section 2.3 of the Fuse 6.2 Security Guide (1) to encrypt a property placeholder in the activemq.xml file. Choose one of the stronger ciphers like, PBEWITHHMACSHA224ANDAES_128. When starting the Fuse container, the broker will not start because of the following exception: org.jasypt.exceptions.EncryptionOperationNotPossibleException at org.jasypt.encryption.pbe.StandardPBEByteEncryptor.decrypt(StandardPBEByteEncryptor.java:1055)[26:org.apache.servicemix.bundles.jasypt:1.9.2.1] at org.jasypt.encryption.pbe.StandardPBEStringEncryptor.decrypt(StandardPBEStringEncryptor.java:725)[26:org.apache.servicemix.bundles.jasypt:1.9.2.1] at org.jasypt.properties.PropertyValueEncryptionUtils.decrypt(PropertyValueEncryptionUtils.java:72)[26:org.apache.servicemix.bundles.jasypt:1.9.2.1] at org.jasypt.spring31.properties.EncryptablePropertyPlaceholderConfigurer.convertPropertyValue(EncryptablePropertyPlaceholderConfigurer.java:109)[187:org.apache.servicemix.bundles.jasypt-spring31:1.9.2.1] If you revert back to one of the weaker ciphers, the exception no longer occurs. I have attached an example activemq.xml and corresponding properties file that includes the encrypted password. (1) https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.2/html/Security_Guide/FMQSecurityEncryptProperties.html

    Description

      Not all the cipher algorithms listed by jasypt-1.9.2/bin/listAlgothims.sh work for encrypting property placeholders.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-9727 Please ship org.apache.servicemix.bundles.jasypt-1.9.3.redhat_3.jar or get associated fixes

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              bicollin1@redhat.com William Collins (Inactive)
              Argo_Integration Travis North (Inactive)
              Tomas Plevko Tomas Plevko
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: