coapp-developers team mailing list archive

[Garrett Serack <garretts@xxxxxxxxxxxxx>]

LOL.

That's why we'll be doing a security audit at many checkpoints in the development of the client.

And really, that's how Windows Update works anyway... we might as well learn from that.

Without that, we'd be forced to Admin-only installs of shared libraries, since there is no way to handle WinSxS without it.

The install client will be doing package verification before it installs it, and it can limit its admin-level install to shared libraries (the only thing that needs it).


Garrett Serack | Open Source Software Developer | Microsoft Corporation 
I don't make the software you use; I make the software you use better on Windows.


-----Original Message-----
From: coapp-developers-bounces+garretts=microsoft.com@xxxxxxxxxxxxxxxxxxx [mailto:coapp-developers-bounces+garretts=microsoft.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Olaf van der Spek
Sent: Friday, April 16, 2010 9:41 AM
To: coapp-developers@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Coapp-developers] Bundling x64 and x86 binaries in the same library package?

On Fri, Apr 16, 2010 at 6:31 PM, Garrett Serack <garretts@xxxxxxxxxxxxx> wrote:
> I'm not aware of a way to have user installs of WinSXS libraries. By definition, they are system level.
>
> However, we could just require the installer client to be installed and setup as admin, and have it run its service at a higher level, so shared libraries can be installed (which aren't end-user installed anyway), which would allow lower-rights installs of applications themselves.

Sounds like a potential securty hole.

Olaf

_______________________________________________
Mailing list: https://launchpad.net/~coapp-developers
Post to     : coapp-developers@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~coapp-developers
More help   : https://help.launchpad.net/ListHelp