Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: Re: Adding "Log on as a service" rights to a user programmatically?

  1. #11

    Default Re: Adding "Log on as a service" rights to a user programmatically?

    > Is ntrights.exe a binary that we can distribute with our software?
    Yes.

    > Does it work on both 64/32 bit?
    Yes.

    Best regards,
    Jeffrey

  2. #12

    Default Re: Adding "Log on as a service" rights to a user programmatically?

    Where can I find this information? Is there a license agreement?

    Thanks.

    >
    > > Is ntrights.exe a binary that we can distribute with our software?
    >Yes.

    Jeff Slarve
    www.jssoftware.com

    you know what happens when you assuage

  3. #13

    Default Re: Adding "Log on as a service" rights to a user programmatically?

    Good question, I spoke too soon.
    Perhaps Friedrich knows...

    Best regards
    Jeffrey

  4. #14

    Default Re: Adding "Log on as a service" rights to a user programmatically?

    Well, the one in the 2003 resource kit is not codesigned, but it's
    written by Georg Zanzen and it's a beta.<g>

    NTRights.Exe - Beta Version by Georg Zanzen
    Grants/Revokes NT-Rights to a user/group

    Jeff Slarve
    www.jssoftware.com

    you know what happens when you assuage

  5. #15

    Default Re: Adding "Log on as a service" rights to a user programmatically?

    Found this "scratch pad". Looks interesting, whether or not it
    actually works.

    https://github.com/zippy1981/ntrights

    Jeff Slarve
    www.jssoftware.com

    you know what happens when you assuage

  6. #16

    Default Re: Adding "Log on as a service" rights to a user programmatically?

    Hi Jeff,

    Thank you.
    I have included ntrights in my SB project some weeks ago and ntrights is
    doing the job perfectly well.

    Best regards,
    Jeffrey

  7. #17

    Default Re: Adding "Log on as a service" rights to a user programmatically?

    I can dig that it works and that you're happy with it.

    But I can also dig that desipite the apparent effectiveness, this
    solution involves introducing an un-vouched, un-documented, and
    un-maintained black box executable to twiddle around with a computers
    most private parts in an elevated and vulnerable state.

    I'd feel better about it if MS actually took ownership of it and moved
    it out of "beta" or at least codesigned it.

    The customer executes and elevates your setup that's signed with your
    company name. So the one that they're basically trusting with their
    security is you.

    The water is fine until it isn't.<g>

    Jeff Slarve
    www.jssoftware.com

    you know what happens when you assuage

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •