Re: ClickOnce Security Risk
- From: "Steve Gerrard" <mynamehere@xxxxxxxxxxx>
- Date: Fri, 28 Mar 2008 19:40:07 -0700
NickP wrote:
Hi there,
I've discovered what I believe to be a security risk with
ClickOnce. I have only just started publishing my application using
our own Trusted certificate, before this I was using a test
certificate.
The problem is that when I published a new build with the new
certificate and then updated the client on a separate machine, it
didn't even warn me that the signature did not match the previous
version. Surely this is a security risk? So basically I could
create an application with the same name / guid etc, use a test
certificate with a similar company name and then overwrite the app
and the user would be none the wiser...
Unless I've missed the point somewhere along the lines of course.
I'm surprised, I have seen exactly the opposite, any change in certificate being
considered completely invalid. Did the user run the update from a shortcut on
their machine, or go to the web site again? You may have simply installed a new
program on their machine, not updated the old one.
.
- Follow-Ups:
- Re: ClickOnce Security Risk
- From: RobinS
- Re: ClickOnce Security Risk
- References:
- ClickOnce Security Risk
- From: NickP
- ClickOnce Security Risk
- Prev by Date: Re: GZip Compression :(
- Next by Date: Re: Odd resonses from VB9
- Previous by thread: ClickOnce Security Risk
- Next by thread: Re: ClickOnce Security Risk
- Index(es):
Relevant Pages
|