OK dumb question but is it potentially possible to have signed chrome which
could be authenticated when Mozilla starts up?

I know that signing is primary used for file transfer verfication but I am
more interested in preventing tampering at the

local workstation (i.e. tampering/ replacement of JAR files)

Instead of having to sign individual scripts, objects, etc, I would like to
sign  a  single chrome JAR file containing a collection of secure  files .
i.e. the signed chrome would be verified on startup using Mozilla certficate
security  methods.

I asked this question a couple of years ago and there didnt seem to be too
much concern for local security issues.

i.e. a security loophole that results in mozilla's application files being
compromised

I was trying to find out if things have moved on?



Reply via email to