From mboxrd@z Thu Jan 1 00:00:00 1970 Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: fr.comp.lang.ada,comp.lang.ada Subject: Re: Canal+ crash Date: Sun, 21 Jul 2024 18:49:27 +0200 Organization: A noiseless patient Spider Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Sun, 21 Jul 2024 18:49:25 +0200 (CEST) Injection-Info: dont-email.me; posting-host="e65d71e4824229d2f452f6602bfcd7bc"; logging-data="195059"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19nHsqYcBHLXUXKB1jn47J71eC5K/o1TNY=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:zATIs5Tf69P0KP9md00BIjE6nsg= Content-Language: en-US In-Reply-To: Xref: news.eternal-september.org fr.comp.lang.ada:2295 comp.lang.ada:66239 List-Id: On 2024-07-21 13:31, Niklas Holsti wrote: > Security researchers and crypto implementers seem to take timing attacks > quite seriously, putting a lot of effort into making the crucial crypto > steps run in constant time. Cynically: they certainly know how to butter their bread... > As I understand it, the "internal knowledge" needed for timing attacks > is mostly what is easily discoverable from the open source-code of the > SW that is attacked. Considering many many layers of software to predict timing from code in uncontrolled environment would be a challenge. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de