Bug 761603 - setpin can't create non hashed pins
Summary: setpin can't create non hashed pins
Keywords:
Status: CLOSED EOL
Alias: None
Product: Dogtag Certificate System
Classification: Retired
Component: Tools - Native
Version: 1.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christina Fu
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks: 530474
TreeView+ depends on / blocked
 
Reported: 2011-12-08 17:27 UTC by bbonok
Modified: 2020-03-27 18:39 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 18:39:32 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description bbonok 2011-12-08 17:27:40 UTC 
How reproducible:
create pin with setpin with option "hash=none" and user pins are stored in input file

 
Actual results:
In ldap pin attribute has same as pin field in input file. No 45 (in ASCII '-') in first byte. In ldap you can see pin as cleartext.

Expected results:
1. generated pin to have '-' in first byte
2. pin attribute to have base64 value, not cleartext value
Note You need to log in before you can comment on or make changes to this bug.