From: "Daniel P. Berrange" <berrange@redhat.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com,
Masaki Kanno <kanno.masaki@jp.fujitsu.com>
Subject: Re: [PATCH] Scrub vnc password for vfb
Date: Tue, 5 Feb 2008 14:06:02 +0000 [thread overview]
Message-ID: <20080205140602.GC20888@redhat.com> (raw)
In-Reply-To: <C3CDD296.134A8%Keir.Fraser@cl.cam.ac.uk>
On Tue, Feb 05, 2008 at 08:45:10AM +0000, Keir Fraser wrote:
> This leads to a question -- should xend.log (and our other log files) be
> world readable in the first place?
In Fedora & RHEL /etc/xen and /var/log/xen are both mode 0700
> If we want to change it we may have to hack the logging package a bit, as it
> seems that Python's open() function calls fopen() which does not allow you
> to manually specify access permissions. Although we could have xend set its
> umask to 0770. Maybe that would break other stuff though?
The permissions of the logfile don't really matter once you set the directory
permissions - and this gives the admin flexibility to chmod/chgrp the dir
to allow selected users acccess to the logs
The main reason for scrubbing the logs is to protect users' passwords when
they post logfiles to mailing lists / bug trackers :-)
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
prev parent reply other threads:[~2008-02-05 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 7:47 [PATCH] Scrub vnc password for vfb Masaki Kanno
2008-02-05 8:45 ` Keir Fraser
2008-02-05 10:38 ` Ian Jackson
2008-02-05 14:06 ` Daniel P. Berrange [this message]
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=20080205140602.GC20888@redhat.com \
--to=berrange@redhat.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=kanno.masaki@jp.fujitsu.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.