Uploaded image for project: 'JGroups'
  1. JGroups
  2. JGRP-1279

ENCRYPT: algorithm provider only half implemented

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Done
    • None
    • 2.4.10, 2.6.19, 2.12
    • None

    Description

      [Dennis Reed]

      ENCRYPT allows the asym_provider to be specified.
      But it only uses it for the KeyGenerator lookup, not the Cipher lookup.
      And the sym_provider is hard-coded to null.

      Is there a reason the sym_provider isn't configurable, and that the providers aren't used for the Cipher lookups?

      This is causing issues for a customer, because they have an application that inserts a security provider at the beginning of the list.
      When JGroups first starts, it uses the default provider (BouncyCastle), but if there's a shun/reconnect after the application
      has inserted its provider, JGroups switches to the application's provider. And since some members are now using a different provider,
      they can't communicate.

      Attachments

        Issue Links

          Activity

            People

              rhn-engineering-bban Bela Ban
              rhn-engineering-bban Bela Ban
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: