Dumb and Dumber

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Phillip McClurg - 16 Sep 2003 18:57 GMT

I just had VC++ installed by our administrator - when I
tried to debug a test application I discovered I did not
have access because I wasn't in the Debugger User Group.

Geez - I guess I'll call the administrator back up and
have him waste another thirty minutes because Microsoft is
busy creating another industry called "I'm sorry, you
can't use the software you just purchased from us."

By the way, are there any other menu items I need the
administrator to come by and enable?

Get Real Bill - Phil McClurg

Reply to this Message

Carl Daniel [VC++ MVP] - 16 Sep 2003 19:26 GMT

> I just had VC++ installed by our administrator - when I
> tried to debug a test application I discovered I did not
[quoted text clipped - 7 lines]
> By the way, are there any other menu items I need the
> administrator to come by and enable?

Of course the requirement to be a member of the Debugger's group is not a
Visual Studio requirement, it's an operating systrem requirement. Running a
debugger is a potential security risk, since the debugger can attach to
(nearly) any process running on the machine, examine memory, etc. Be glad
that this is something that ordinary users are not allowed to do.

Be unhappy that your IT department hasn't figured out that developers aren't
ordinary users and shouldn't be configured as such!

-cd

Reply to this Message

Jasper Kent - 16 Sep 2003 19:27 GMT

If you're going to be programming ASP.NET with IIS on your own machine, then
I'd book the system administrator for a couple of days.

Regards,

Jasper Kent.

> I just had VC++ installed by our administrator - when I
> tried to debug a test application I discovered I did not
[quoted text clipped - 9 lines]
>
> Get Real Bill - Phil McClurg

Reply to this Message

William DePalo [MVP VC++ ] - 16 Sep 2003 19:32 GMT

> I just had VC++ installed by our administrator - when I
> tried to debug a test application I discovered I did not
> have access because I wasn't in the Debugger User Group.

There are security issues to be consider when debugging stored procedures
and debugging across the network. This link should explain them:

http://support.microsoft.com/?id=329282

> Geez - I guess I'll call the administrator back up and
> have him waste another thirty minutes because Microsoft is
> busy creating another industry called "I'm sorry, you
> can't use the software you just purchased from us."

FWIW: NT enforces a discretionary security model. Someone with debug
privilege who knows his way around the o/s poses a greater threat than the
garden variety user of Word and Excel hence the check.

Regards,
Will

Reply to this Message

Dumb and Dumber

Free Magazines