Issue #30: JSS Test Suite fails with FUTURE crypto policy - jss

jss

#30 JSS Test Suite fails with FUTURE crypto policy

Closed: fixed 5 years ago by cipherboy. Opened 5 years ago by cipherboy.

This should be fixed prior to release of 4.5.1, though it only affects users who have changed their system policy.

Two choices:

Warn about crypto policies set to FUTURE and bail.
Use FUTURE-compatible value (min key length bits 3072).

I'd probably update the value to 4096.

cipherboy commented 5 years ago

This was fixed in jss-pr#92.

Metadata Update from @cipherboy:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

5 years ago

Metadata

Assignee

None

Tags

None

Blocking

None

Depending on

None

Priority

None

Milestone

None

type

None

component

None

version

None

keywords

None

estimate

None

feature

None

origin

None

proposedpriority

None

proposedmilestone

None

reviewer

None

fixedinversion

None

platforms

None

blockedby

None

blocking

None

rhbz

None

jss

Source Code

#30 JSS Test Suite fails with FUTURE crypto policy Closed: fixed 5 years ago by cipherboy. Opened 5 years ago by cipherboy.

Metadata

#30 JSS Test Suite fails with FUTURE crypto policy

Closed: fixed 5 years ago by cipherboy. Opened 5 years ago by cipherboy.