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
[email protected]
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Reply via email to