From: Aruna Balakrishnaiah <aruna@linux.vnet.ibm.com>
To: Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>,
Tachibana <tachibana@mxm.nes.nec.co.jp>
Cc: kexec@lists.infradead.org, ananth@in.ibm.com, BUENDGEN@de.ibm.com
Subject: makedumpfile security key filtering with EPPIC scripts
Date: Fri, 31 May 2013 16:16:02 +0530 [thread overview]
Message-ID: <51A87F6A.6090407@linux.vnet.ibm.com> (raw)
Hi Atsushi/Tachibana,
Now that upstream makedumpfile has eppic support, we are working
on sample EPPIC scripts that can be used with makedumpfile to scrub
confidential data from the vmcore. With these sample scripts as a
reference, customers can come up with their own EPPIC scripts. We are
looking for the possibility of pushing these sample EPPIC scripts to
upstream makedumpfile. Please let me know your opinion on this.
Regards,
Aruna
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2013-05-31 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 10:46 Aruna Balakrishnaiah [this message]
2013-06-04 7:36 ` makedumpfile security key filtering with EPPIC scripts Atsushi Kumagai
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=51A87F6A.6090407@linux.vnet.ibm.com \
--to=aruna@linux.vnet.ibm.com \
--cc=BUENDGEN@de.ibm.com \
--cc=ananth@in.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
--cc=tachibana@mxm.nes.nec.co.jp \
/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