Bug 454758 - Software Repository's "MD5" and "SHA-256" fields allow more than 32 and 64 chars
Software Repository's "MD5" and "SHA-256" fields allow more than 32 and 64 chars
Status: CLOSED WONTFIX
Product: JBoss Customer Support Portal
Classification: Retired
Component: Product Mappings (Show other bugs)
1.3.8
All All
medium Severity low
: ---
: ---
Assigned To: JBoss CSP Bug Watch List
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-09 17:28 EDT by Mike Amburn
Modified: 2011-01-31 12:48 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-01-31 12:40:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Mike Amburn 2008-07-09 17:28:38 EDT
the MD5 field should only allow 32 chars (otherwise it won't be a valid MD5), similarly, the SHA-256 field should only allow 64 chars. It would be an easy way to catch errors if the UI would only allow the user to enter the allowed number of chars and no more.

----
Data relocated from Jira (JBNET-1838)
Comment 1 John Sanda 2008-09-04 10:09:43 EDT
I think we ought to implement the validation in the application layer as well to make things robust. We will need it there anyway if we every expose this functionality as a service as some have requested.
Comment 2 David Spalding 2011-01-31 12:40:37 EST
Bugs are no longer tracked under this classification. CSP is now monitored in 
Other | Customer Portal | Integrated app: JBoss CSP. 

Please refile any current defect records or RFEs under the current 
classification.
Comment 3 David Spalding 2011-01-31 12:48:25 EST
Bugs are no longer tracked under this classification. CSP is now monitored in 
Other | Customer Portal | Integrated app: JBoss CSP. 

Please refile any current defect records or RFEs under the current 
classification.

Note You need to log in before you can comment on or make changes to this bug.