supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Vincent Danen <vdanen@annvix.org>
Cc: <supervision@list.skarnet.org><supervision@list.skarnet.org>
	<supervision@list.skarnet.org>
Subject: Re: runit running under linux 2.4 with openwall patches
Date: Sat, 5 Feb 2005 16:14:53 -0700	[thread overview]
Message-ID: <86f55940a26d28d7a6a3a131c9947f5b@annvix.org> (raw)
In-Reply-To: <20050205212555.GI20427@digitus>

[-- Attachment #1: Type: text/plain, Size: 1638 bytes --]


On Feb 05, 2005, at 14:25, Csillag Tamás wrote:

>> Hmmm... spoke too soon.  None of the services requiring tcpsvd were
>> installed, so I tried with rsync and if I start supervise on those
>> services, nothing happens.  But if "sh -x run" myself, I can see the
>> services are starting.  Not sure if recompiling ipsvd without dietlibc
>> will help, but it's something I'll have to try.
>>
>>> In grsec I use the chpax utility to bypass this security checks on
>>> these
>>> (and only these) programs.
>>
>> Ouch.  Not a good solution.
>>
>>> Maybe it is worth asking the author of dietlibc..
>>> http://www.fefe.de/dietlibc/
>>
>> I have... and am in the middle of a conversation with him.  He's very
>> interested in seeing this resolved.
>
> Can you tell me what is the result?
> Felix released 0.28 recently, it contains the fixes for that or not?
> (I was unable to figure out from the CHANGES file)

I meant to email the list earlier, but didn't get a chance.  I did 
build dietlibc 0.28 and recompiled runit under it and it seems to work 
ok.  At least the kernel doesn't kill or stall runit anymore.  But I 
had to build without WANT_STACKGAP due to my gcc+SSP compiler (I don't 
know if this will make any difference to runit itself because I can't 
compiled dietlibc 0.28 with gcc+SSP with WANT_STACKGAP enabled).

So far it seems good although I want to keep an eye on it more before I 
put it into production.

-- 
Annvix - Secure Linux Server: http://annvix.org/
"lynx -source http://linsec.ca/vdanen.asc | gpg --import"
{FEE30AD4 : 7F6C A60C 06C2 4811 FA1C  A2BC 2EBC 5E32 FEE3 0AD4}

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 186 bytes --]

  parent reply	other threads:[~2005-02-05 23:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-20 22:14 Vincent Danen
2005-01-20 22:28 ` Charlie Brady
2005-01-20 22:52   ` Vincent Danen
2005-01-21 19:32 ` Gerrit Pape
2005-01-25  4:51   ` Vincent Danen
2005-01-25 10:58     ` Torne Wuff
2005-01-25 19:54       ` Vincent Danen
2005-01-25 23:33       ` Vincent Danen
2005-01-26  0:44         ` Csillag Tamás
2005-01-26  4:31           ` Vincent Danen
2005-01-26  8:52             ` Csillag Tamás
2005-01-27 19:52               ` Charlie Brady
2005-01-26 12:07             ` Milan P. Stanic
     [not found]             ` <20050205212555.GI20427@digitus>
2005-02-05 23:14               ` Vincent Danen [this message]
2005-03-14 14:11                 ` Csillag Tamás
2005-03-14 17:40                   ` Gerrit Pape

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86f55940a26d28d7a6a3a131c9947f5b@annvix.org \
    --to=vdanen@annvix.org \
    --cc=supervision@list.skarnet.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).