Re: security issues with a dll
- From: "Brian Muth" <bmuth@xxxxxxxx>
- Date: Mon, 5 Mar 2007 20:24:55 -0800
"William DePalo [MVP VC++]" <willd.no.spam@xxxxxxxx> wrote in message
news:uPHkoP3XHHA.4552@xxxxxxxxxxxxxxxxxxxxxxx
"Dave Cullen" <nospam@xxxxxxxx> wrote in message
news:45EC93E9.CC1165C3@xxxxxxxxxxx
Ugh. Thanks, but that's a tad more complicated than I'm comfortable
with.
Such is life. Security is not pretty. :-)
Isn't there a way to "register" a dll (I remember seeing that term)
that'll make it available to all users?
No. You are facing in issue of trust with respect to a user, not a stretch
of code. Your mission is to get the code that invokes some function in
that DLL to execute in another user's context.
Technically, you can register a COM dll into Component Services (thus
rendering it as a COM+ object). Component Services allow one to configure
access such that the dll is available to all users (or a subset of users).
Brian
.
- Follow-Ups:
- Re: security issues with a dll
- From: William DePalo [MVP VC++]
- Re: security issues with a dll
- References:
- security issues with a dll
- From: Dave Cullen
- Re: security issues with a dll
- From: William DePalo [MVP VC++]
- Re: security issues with a dll
- From: Dave Cullen
- Re: security issues with a dll
- From: William DePalo [MVP VC++]
- security issues with a dll
- Prev by Date: Re: Whats going onto the stack here?
- Next by Date: Re: open a large file in win64
- Previous by thread: Re: security issues with a dll
- Next by thread: Re: security issues with a dll
- Index(es):
Relevant Pages
|
