[Mono-dev] setuid application

Gladish, Jacob Jacob.Gladish at sig.com
Mon Mar 2 14:27:37 EST 2009

Yes, that's what I'm doing. I had an .exe, now I have a native app that does little more than loads and runs my .exe and its main(). But now I need to compile that native app for 4 different platforms.

-----Original Message-----
From: Jonathan Pryor [mailto:jonpryor at vt.edu]
Sent: Monday, March 02, 2009 2:08 PM
To: Gladish, Jacob
Cc: mono-devel-list at lists.ximian.com
Subject: Re: [Mono-dev] setuid application

On Mon, 2009-03-02 at 12:00 -0500, Gladish, Jacob wrote:
> Before proceeding with my current plan, I wanted to get any feedback
> from anyone who may have explored building a mono app that has setuid.
> My application is mostly managed code, with a few p/invoke calls, but
> it's been pretty platform agnostic thus far. I need to have setuid
> privileges on my app, and the best way I have come up with so far is
> to have a small native app that acts as a host that has setuid on it.
> I certainly don't want to change the permissions on /usr/bin/mono.
> Does anyone have any other suggestions?

If you need a native app anyway (which makes sense, for the reasons you
specified) then it might make sense to embed the mono library and start
your managed code using the embedding API:


There are several examples as well:


 - Jon

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.

More information about the Mono-devel-list mailing list