netdev - Re: [PATCH net-next] ipv4: Add support to disable icmp timestamp

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20190513.090733.1731394770012592569.davem@davemloft.net>
Date:   Mon, 13 May 2019 09:07:33 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     chenweilong@...wei.com
Cc:     mkubecek@...e.cz, netdev@...r.kernel.org, kuznet@....inr.ac.ru,
        yoshfuji@...ux-ipv6.org
Subject: Re: [PATCH net-next] ipv4: Add support to disable icmp timestamp

From: Weilong Chen <chenweilong@...wei.com>
Date: Mon, 13 May 2019 20:06:37 +0800

> So, the 'time' may become sensitive information. The OS should not
> leak it out.

The current time of day is a globally synchronized value everyone on
the planet has access to.

I don't buy this line of reasoning at all, time is not sensitive
information.

I agree with Michal, the apps should not be using time as a seed for
critical calculations that have security implications.

There is no way I am applying this patch, especially as-is.