Ticket #416 (new defect)
Verify Eraser's plugin loading behaviour when CRLs cannot be verified
| Reported by: | Joel | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | Eraser 6.0.11 |
| Component: | Core | Version: | |
| Keywords: | Cc: | ||
| Processor Architecture: | Blocked By: | ||
| Blocking: | Operating System: |
Description (last modified by Joel) (diff)
A forum post states that when all outbound HTTP connections are blocked, and when a proper proxy is not specified, Eraser is not able to load the default plugin.
In addition, when the poster sent an erase command via the Command Line, Eraser crashed.
Blocking
| Id | Summary | Milestone |
|---|---|---|
| #416 | └ Verify Eraser's plugin loading behaviour when CRLs cannot be verified | Eraser 6.0.11 |
Blocked by
| Id | Summary | Milestone |
|---|---|---|
| #416 | └ Verify Eraser's plugin loading behaviour when CRLs cannot be verified | Eraser 6.0.11 |
Note: See
TracTickets for help on using
tickets.
