Re: Logging sensitive information from kernel (while atomic and uninterrupted)
|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
did u check out syslog feature
On 03-May-2012 2:11 PM, "Panagiotis Sakkos" <panos.sakkos@xxxxxxx> 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,
> Kernelnewbies mailing list
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
[Newbies FAQ] [Linux Kernel Development] [IETF Annouce] [Git] [Networking] [Security] [Bugtraq] [Photo] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Networking] [Linux RAID] [Linux SCSI] [Linux ACPI]