Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Tue, 23 Mar 2004 11:58:20 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: suid bit on executables? Message-ID: <20040323105820.GB13267@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On Mar 22 19:49, Richard Troy wrote: > A little over a year ago, I poked my nose under the tent to inquire about > this once more and in the interrim there had been a new cygserver and a > new ssh daemon, and I was very happy with the advance, but still things > were short of the SUID bit being honored... > > Now, I read in the archives about something, apparently upcoming, called > cygdaemon... I read hints that cygdaemon helps address this problem. There's no such thing as a cygdaemon, only cygserver. If the SUID stuff gets implemented, it will be based on cygserver. But there's no code for doing this so far. Security changes in 2K3 are making an implementation even more complex. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/