From: royanirban@gmail.com (Anirban Roy)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Logging sensitive information from kernel (while atomic and uninterrupted)
Date: Fri, 4 May 2012 08:13:34 +0530 [thread overview]
Message-ID: <CAF2EO-w=b9Zygg_5dBgg6zsm1Li_Y2o02ejOPKQJ1MX2J04jaA@mail.gmail.com> (raw)
In-Reply-To: <A1F86B12A2E22C4CB3164ECFFD1C54DB08ECB6C4@PLOXCHG03.cern.ch>
did u check out syslog feature
On 03-May-2012 2:11 PM, "Panagiotis Sakkos" <panos.sakkos@cern.ch> wrote:
>
> Hi again,
>
> I would like to ask you the possible ways of logging information from the
kernel, without
> the messages being intercepted from dmesg. Also please note that my
implementation uses the kprobes API, so in my probes I am atomic and
uninterrupted.
>
> printk sends the logs to the kernel ring buffer, so dmesg will always see
them. Hence, printk-ing is not a solution.
> Logging to a unix socket (i.e. /dev/log) didn't work (check "Crash when
sending a lot of messages through a unix socket" thread).
> proc filesystem, I am not sure, but I believe that is not suitable for
logging information. It is more for kernel information exposing.
> Any other ideas? My problem is that I log sensitive data and any
unprivileged user can run dmesg and see the sensitive logs.
>
> Thank you in advance for your time,
> Panos
> --
> http://www.cern.ch/psakkos
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20120504/c4a12e70/attachment.html
prev parent reply other threads:[~2012-05-04 2:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 8:40 Logging sensitive information from kernel (while atomic and uninterrupted) Panagiotis Sakkos
2012-05-03 11:03 ` Kernel latency for handling the Network traffic Suresh Kumar Subramanian
2012-05-03 13:54 ` michi1 at michaelblizek.twilightparadox.com
2012-05-03 16:47 ` Abu Rasheda
2012-05-03 19:52 ` michi1 at michaelblizek.twilightparadox.com
2012-05-04 2:43 ` Anirban Roy [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='CAF2EO-w=b9Zygg_5dBgg6zsm1Li_Y2o02ejOPKQJ1MX2J04jaA@mail.gmail.com' \
--to=royanirban@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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;
as well as URLs for NNTP newsgroup(s).