From: "Daniel P. Berrange" <berrange@redhat.com>
To: Ewan Mellor <ewan@xensource.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Scrub VNC passwords from XenD log files
Date: Wed, 6 Dec 2006 17:16:03 +0000 [thread overview]
Message-ID: <20061206171603.GA13126@redhat.com> (raw)
In-Reply-To: <20061206122520.GE17323@leeni.uk.xensource.com>
On Wed, Dec 06, 2006 at 12:25:20PM +0000, Ewan Mellor wrote:
> On Tue, Dec 05, 2006 at 07:31:25PM +0000, Daniel P. Berrange wrote:
>
> > The XendDomainInfo and XendConfig classes both log the guest VM config data
> > to the /var/log/xen/xend.log in many places. Unfortunately the VNC passwords
> > are stored in plain text in the guest VM config files. So we end up with
> > plain text passwords in the xend.log file
> >
> > Now we can make /var/log/xen mode 0700 to protect them from local users,
> > but it is very common when debugging issues to request that a user attach
> > the contents of /var/log/xen/xend.log to the bug report ticket, or emails
> > sent to mailing lists. This will obviously compromise any VNC passwords
> > to essentially the while world & his dog. What's more, Google will make
> > it incredibly easy to search for these too.
> >
> >
> > There are a few potential approaches to this
> >
> > 1. Remove all logging from xend.log
> > 2. Change default log level to only record WARN and higher, so DEBUG
> > stuff is not recorded normally
> > 3. Scrub the passwords out of the data being logged
> > 4. Do nothing
> >
> > I really don't like options 1 or 2, because the stuff XenD is logging is
> > actually incredibly helpful when debugging end user problems. 4 is not
> > really a viable option either. So we're left with 3.
> >
> > Thus I am attaching a prototype patch which scrubs VNC passwords out of
> > the data being logged by XenD.
>
> That looks good to me -- could I have a Signed-off-by line, so I can apply it?
I didn't add the signed-off-by because the patch isn't finished - I really
just wanted to see if people were amenable to this kind of approach before
doing more work on it. Since you like it, I'll finish it off shortly - there
just a couple more test cases I need to go through - suspend/restore & inactive
domains - to verify passwords are always scrubbed correctly. I'll post a final
version of the patch by the end of today if all goes to plan.
Regards,
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 -=|
next prev parent reply other threads:[~2006-12-06 17:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 19:31 [PATCH] Scrub VNC passwords from XenD log files Daniel P. Berrange
2006-12-06 12:25 ` Ewan Mellor
2006-12-06 17:16 ` Daniel P. Berrange [this message]
2006-12-06 17:24 ` Ewan Mellor
2006-12-06 19:43 ` Daniel P. Berrange
2006-12-07 12:14 ` Ewan Mellor
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=20061206171603.GA13126@redhat.com \
--to=berrange@redhat.com \
--cc=ewan@xensource.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.