[EAS] Sage Update Available

[Sean Donelan]

On Mon, 4 Nov 2019, Dave Turnmire wrote:
> Another option you can consider the merits of.  Disable the signature check 
> while you are waiting for an opportunity to get the new software installed.  
> That has a theoretical security risk.  But the alternative is to risk not 
> sending out alerts for a real emergency.  Or more likely (assuming you aren't 
> an LP), just forwarding alerts from an LP.  That of course means not getting 
> the advantages of CAP.  How big of deal that is depends on your 
> circumstances.

DASDEC logs show CAP XMLSEC signature validation results.

Sage logs do NOT show CAP XMLSEC signature validation results (I haven't 
checked if Rev95 changes this).

Trilithic logs show warning CAP XMLSEC signature validation results.

Don't have any Gorman-Redlich boxes to check.

User interface debates -- do lots of spurious warning messages 
confuse or help operators.  Broken stuff won't get fixed if the operator 
doesn't know about it.  On the other hand, there are a lot of 'normal' 
errors that are only needed in diagnostic logs or when trouble shooting.

> Make your best choice among poor options and move on...

Document in notes in your EAS logs.