Re: Permissions on Event Log?


I can deal with it. I can do alot worse things as non-admin app.
I don't see why it's a problem to log events.

What are the risks? I can create my own log file?
Space usage? Can be addressed.

You could have an admin install, but then the user may need to log off the
machine. In a corp. enviroment this is a pain. If you give the users admin
right they install everything from spyware to porn.



"Nicole Calinoiu" <calinoiu REMOVETHIS AT gmail DOT com> wrote in message
news:OdaBcdgHHHA.3676@xxxxxxxxxxxxxxxxxxxxxxx
When a non-admin user installs an application, there are plenty of things
that the installer should not be allowed to do, regardless of how much
that user might happen to trust the application. If your application
requires creation of an event log, then it should be installed by an
administrator. This is not an uncommon requirement, and I'm a little
puzzled as to why it seems to pose a problem for you.


"schneider" <eschneider@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:e9oN1PgHHHA.5104@xxxxxxxxxxxxxxxxxxxxxxx
Yes.
I don't agree with that requirement.
So now I need two installs if I'm not admin, just so I can have an event
log?
I can create my own log file without admin privileges.
Windows should be able to provide some basic log file needs. When a user
installs an app. they are already trusting the application. The Event log
can be viewed remotely from windows admins, by making it difficult to use
they are making harder for IT to manage apps through a know/common
interface.

Schneider


"Dominick Baier" <dbaier@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:51eb30483a388c8eb68b4e3e110@xxxxxxxxxxxxxxxxxxxxx
You can only register event source when you have administrative
privileges.
Build a small app that pre-creates the event sources at deployment time
(with admin privileges) - afterwards you can use them from normal-user
processes.


-----
Dominick Baier (http://www.leastprivilege.com)

I did find some new info:
http://msdn2.microsoft.com/en-us/library/5zbwd3s3.aspx
Basicly allows you to register a source during runtime. Have not tried
it yet myself.

Schneider

"schneider" <eschneider@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23R6U$iIGHHA.3952@xxxxxxxxxxxxxxxxxxxxxxx

Whats the deal here MS?

Has Issues in Win2003, only way to allow is a Regedit hack or
Installer
class? What kind of BS is this?
So what evey time I install to Win2003 I need to add X number of
Application Sources to the Event log system?
What if the Log is Full?

So what we do our own file log? Then Admin can't check them as
easily...

How about a real solution...

Schneider









.

Relevant Pages

  • Re: Deny Interactive Logon but Allow Runas
    ... users may also need to install a fix-pack, ... be an admin to install. ... if your secret app is really so bad ... As our users don't have local admin rights they usually have ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Permissions on Event Log?
    ... If I create a custom log file and fill the entire hard drive that effects ... Adding an event source affects the whole system and not that single ... You could have an admin install, but then the user may need to log off ...
    (microsoft.public.dotnet.security)
  • Re: Permissions on Event Log?
    ... Adding an event source affects the whole system and not that single user - so you need admin privs. ... You could have an admin install, but then the user may need to log off ... I can create my own log file without admin privileges. ...
    (microsoft.public.dotnet.security)
  • Re: Permissions on Event Log?
    ... If I create a custom log file and fill the entire hard drive that effects ... Adding an event source affects the whole system and not that single user - ... You could have an admin install, but then the user may need to log off ...
    (microsoft.public.dotnet.security)
  • Re: Limit administrators permissions
    ... > local admin, otherwise it does not install the Office ... I'm not the least bit familiar with Hummingbird 5, ... If not I think your best bet would be to contact the maker of the app. ...
    (microsoft.public.windowsxp.security_admin)