mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Mimi Zohar <zohar@us.ibm.com>
Cc: Crispin Cowan <crispin@novell.com>,
	David Safford <safford@us.ibm.com>,
	kjhall@us.ibm.com, linux-kernel <linux-kernel@vger.kernel.org>,
	LSM ML <linux-security-module@vger.kernel.org>,
	linux-security-module-owner@vger.kernel.org,
	David Safford <safford@watson.ibm.com>,
	Serge E Hallyn <sergeh@us.ibm.com>
Subject: Re: [RFC][PATCH 8/8] SLIM: documentation
Date: Thu, 31 Aug 2006 01:46:28 +0200	[thread overview]
Message-ID: <20060830234627.GM3923@elf.ucw.cz> (raw)
In-Reply-To: <OF47A7AF49.EC4403C3-ON852571DA.00818B73-852571DA.006C6E56@us.ibm.com>

Hi!

> > But my ssh data can't be classified higher, because ssh interacts with
> > network. Ouch.
> >
> > You are right that this will make recovery from spyware attack easier,
> > but...
> 
> Here you are raising concerns over secrecy, which is a totally separate
> issue from integrity.  In order to protect the secrecy of files, you
> would distinguish PUBLIC files from USER-SENSITIVE/SYSTEM-SENSITIVE
> files.

So... will I be able to set ~/.ssh/private_key to USER-SENSITIVE and
still use ssh to log in to remove machines? Will trojans coming from
network be able to read that file?

I do not think see how that can work... because ssh accesses network,
and needs to know my private_key.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2006-08-30 23:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-17 19:53 Kylene Jo Hall
2006-08-17 23:02 ` Pavel Machek
2006-08-18 17:41   ` Mimi Zohar
2006-08-24  5:49     ` Pavel Machek
2006-08-24 13:03       ` Serge E. Hallyn
2006-08-24 13:11         ` Pavel Machek
2006-08-24 18:00           ` David Safford
2006-08-26 10:11             ` Pavel Machek
     [not found]               ` <44F4DF11.20205@novell.com>
     [not found]                 ` <20060830225950.GI3923@elf.ucw.cz>
     [not found]                   ` <44F61B2E.5090603@novell.com>
2006-08-30 23:15                     ` Pavel Machek
     [not found]                   ` <OF47A7AF49.EC4403C3-ON852571DA.00818B73-852571DA.006C6E56@us.ibm.com>
2006-08-30 23:46                     ` Pavel Machek [this message]
2006-08-31 14:30                       ` David Safford
2006-08-18 22:05 ` Randy.Dunlap

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=20060830234627.GM3923@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=crispin@novell.com \
    --cc=kjhall@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module-owner@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=safford@us.ibm.com \
    --cc=safford@watson.ibm.com \
    --cc=sergeh@us.ibm.com \
    --cc=zohar@us.ibm.com \
    /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
all inboxes | Powered by JetHome®