[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: MEMORY credential cache interop between Heimdal and MIT?
- To: heimdal-discuss@sics.se, Ken Raeburn <raeburn@MIT.EDU>
- Subject: Re: MEMORY credential cache interop between Heimdal and MIT?
- From: Gabor Gombas <gombasg@sztaki.hu>
- Date: Thu, 16 Aug 2007 14:48:11 +0200
- Cc: Michael B Allen <miallen@ioplex.com>, jaltman@secure-endpoints.com, "Henry B. Hotz" <hotz@jpl.nasa.gov>, Alf Wachsmann <alfw@slac.stanford.edu>
- In-Reply-To: <79896EE9-9AE9-41C5-8F66-B144D0E0B1F8@mit.edu>
- List-Archive: <http://list.sics.se/sympa/arc/heimdal-discuss>
- List-Help: <mailto:sympa@sics.se?subject=help>
- List-Id: <heimdal-discuss.sics.se>
- List-Owner: <mailto:heimdal-discuss-request@sics.se>
- List-Post: <mailto:heimdal-discuss@sics.se>
- List-Subscribe: <mailto:sympa@sics.se?subject=subscribe%20heimdal-discuss>
- List-Unsubscribe: <mailto:sympa@sics.se?subject=unsubscribe%20heimdal-discuss>
- Mail-Followup-To: heimdal-discuss@sics.se, Ken Raeburn <raeburn@MIT.EDU>,Michael B Allen <miallen@ioplex.com>, jaltman@secure-endpoints.com,"Henry B. Hotz" <hotz@jpl.nasa.gov>,Alf Wachsmann <alfw@slac.stanford.edu>
- References: <Pine.LNX.4.64.0708151117370.17167@iris02.slac.stanford.edu> <540F131A-18D4-4343-AE0F-3B5D760DA215@jpl.nasa.gov> <20070815161906.8fcc2ddf.miallen@ioplex.com> <46C36271.7050402@secure-endpoints.com> <20070815183305.2580e548.miallen@ioplex.com> <79896EE9-9AE9-41C5-8F66-B144D0E0B1F8@mit.edu>
- Reply-To: heimdal-discuss@sics.se, Gabor Gombas <gombasg@sztaki.hu>
On Wed, Aug 15, 2007 at 09:26:45PM -0400, Ken Raeburn wrote:
> As for the OS providing secure storage available only to the right
> processes (for some definition of "right processes"), there is the Linux
> in-kernel keychain support, for example. But even using in-memory
> credentials won't protect you from one compromised worker process attaching
> another process under ptrace and extracting credentials (or forcing it to
> make some OS call to retrieve credentials).
IMHO in Linux it would not be too hard to write a security module that
simply disallows ptrace()/kill()/etc. for anyone but root (so some form
of debugging is still possible). Maybe SELinux can do the job if you
make the policy strict enough.
Gabor
--
---------------------------------------------------------
MTA SZTAKI Computer and Automation Research Institute
Hungarian Academy of Sciences
---------------------------------------------------------