Bug 778520 (SOA-992) - SFTP certificate passphrase is not optional when using certificates
Summary: SFTP certificate passphrase is not optional when using certificates
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-992
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.3 GA
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.3 CP01
Assignee: Mark Little
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-07 21:48 UTC by Len DiMaggio
Modified: 2009-03-17 19:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-17 19:12:55 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 778617 0 medium CLOSED SFTP certificate passphrase is not optional when using certificates 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-992 0 None None None Never

Internal Links: 778617

Description Len DiMaggio 2008-11-07 21:48:37 UTC
Date of First Response: 2009-03-11 03:29:23
project_key: SOA

Platform JIRA for project JIRA:  https://jira.jboss.org/jira/browse/JBESB-2173

Comment 1 Len DiMaggio 2008-11-07 21:48:46 UTC
Link: Added: This issue depends JBESB-2173


Comment 2 Mark Little 2008-12-22 04:09:29 UTC
Link: Added: This issue is related to JBESB-2173


Comment 3 Mark Little 2008-12-22 04:10:36 UTC
Link: Removed: This issue is related to JBESB-2173 


Comment 4 Mark Little 2008-12-22 04:11:07 UTC
Link: Added: This issue is related to SOA-1097


Comment 5 Mark Little 2008-12-22 05:36:35 UTC
Link: Added: This issue depends JBESB-2249


Comment 6 Dana Mison 2009-03-11 07:29:23 UTC
Release Note:

JBESB-2173
The SFTP certificate passphrase is no longer required when using a certificate.

Comment 7 Len DiMaggio 2009-03-17 19:12:55 UTC
Verified - when the certificate key in question does have a key, certificate-passphrase is optional - 4.3 CP01 CR4.




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