Uploaded image for project: 'Commons Crypto'
  1. Commons Crypto
  2. CRYPTO-76

Remove log dependence

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • None
    • None
    • None

    Description

      According the discussion in commons-dev, we will remove the log dependence of common-logging.
      About the logging of native library failure, users of CRYPTO could get the information about whether native is enabled or native failure reason from org.apache.commons.crypto.utils.NativeCodeLoader#isNativeCodeLoaded() or org.apache.commons.crypto.cipher.Openssl#loadingFailureReason(), they could log these information in their system if they need.
      At the same time, I think we can add an option for "native only" (Currently, when loading native failed, we log native failure error and use JCE implementation as fallback directly), the property in configuration may like "ENABLE_FALLBACK_ON_NATIVE_FAILED", if user disable the option, it could throw an exception when loading native failed.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            dapengsun Dapeng Sun
            dapengsun Dapeng Sun
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment