linux-kernel - Re: [PATCH] Let SYSVIPC default to 'y'

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <9a8748490804231722o66ccb740q94b50c9ca7ba23ab@mail.gmail.com>
Date:	Thu, 24 Apr 2008 02:22:30 +0200
From:	"Jesper Juhl" <jesper.juhl@...il.com>
To:	"Kevin Winchester" <kjwinchester@...il.com>
Cc:	linux-kernel@...r.kernel.org,
	"Krishna Balasubramanian" <balasub@....ohio-state.edu>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"Sam Ravnborg" <sam@...nborg.org>
Subject: Re: [PATCH] Let SYSVIPC default to 'y'

On 24/04/2008, Kevin Winchester <kjwinchester@...il.com> wrote:
> Jesper Juhl wrote:
>
> > SYSVIPC is a pretty crucial feature that I doubt very much if anyone
> except embedded people should even consider disabling - it simply breaks too
> much software for a Linux box to really be useful without it, for most
> purposes.
> > For that reason I find it quite odd that the feature defaults to 'No'
> currently.  I really cannot see any reason why we wouldn't want this to
> default to 'Yes', so this patch changes the default by adding 'default y' to
> Kconfig.
> >
<...snip...>
>
>  I am running up-to-date Kubuntu Hardy Heron, but...
>
>  kevin@...khine:~/linux/linux-2.6$ grep SYSVIPC .config
>  # CONFIG_SYSVIPC is not set
>
>  What software that would be in a standard install would be broken?  I don't
> seem to notice anything...
>
>  Not that I mind the default being changed - I just wonder if things on my
> box are broken and I just don't know it.
>

Well,
  DOSEmu doesn't work without it.
  SysOrb (http://www.sysorb.com/) doesn't work without it AFAIK.
  IIRC, X had trouble in the past without it.
  Anything that uses SysV shared memory, SysV message passing
(msgget(), msgsnd() etc..),
  SysV semaphores (semget() etc), will have trouble.
  In general, System V IPC is just used by many different programs...
Perhaps not any you run,
  but it is pretty widely used.

-- 
Jesper Juhl <jesper.juhl@...il.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/