This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Support for plugin verification against CA | ||
---|---|---|---|
Product: | platform | Reporter: | Jiri Rechtacek <jrechtacek> |
Component: | Plugin Manager | Assignee: | Jaroslav Tulach <jtulach> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | CC: | anebuzelsky, err, omatzura |
Priority: | P2 | Keywords: | PLAN, UI |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
Jiri Rechtacek
2008-04-21 18:58:22 UTC
We're evaluating this RFE for next NetBeans release. Isn't this a regression? It use to work in NB5.5. Some of the issues filed about this problem have "regression" in keywords, some don't. But since it used to work, doesn't that make it a defect? err, it cannot be a regression. Verification in NB6.1 works in as same way as NB5.5. If a plugin is signed by a certification which was not trusted in NB so far and user has approved it, then NB add this certificate among trusted and will not ask for confirmation again (fixed issue 123148). This RFE is speaking about possibility to verify plugins against 3rd party Certificate Authority beside of current NetBeans certification. Ah, my bad. Thanks for the clarification. *** Issue 120250 has been marked as a duplicate of this issue. *** Reassigning to the new "autoupdate/*" owner dlipin. Good idea, who's going to implement it? |