Frama-C-discuss mailing list archives
This page gathers the archives of the old Frama-C-discuss archives, that was hosted by Inria's gforge before its demise at the end of 2020. To search for mails newer than September 2020, please visit the page of the new mailing list on Renater.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Frama-c-discuss] how to abstract the loop
- Subject: [Frama-c-discuss] how to abstract the loop
- From: pascal.cuoq at gmail.com (Pascal Cuoq)
- Date: Sat, 31 Dec 2011 04:43:15 +0100
- In-reply-to: <CAOH62JhD-nbOZn_80CHWYDFNMRtB1+zwsPf3tpEYobmfRrTVxw@mail.gmail.com>
- References: <17b4cd1.59f5.134880b6e54.Coremail.luoting8609@163.com> <CAOH62JhD-nbOZn_80CHWYDFNMRtB1+zwsPf3tpEYobmfRrTVxw@mail.gmail.com>
On Thu, Dec 29, 2011 at 10:46 AM, Pascal Cuoq <pascal.cuoq at gmail.com> wrote: > With only a little bit of additional work, the value analysis would also > tell you that beyond the information flow shown above, AES is susceptible > to cache-timing attacks ( > http://cr.yp.to/antiforgery/cachetiming-20050414.pdf ). And it would > verify that Skein-256 is not. This kind of verification was put together > with researchers and students at University of Minho, and it's currently > not documented > It's documented now, at http://blog.frama-c.com/index.php?post/2011/12/31/Do-not-use-AES-in-a-context-where-timing-attacks-are-possible Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20111231/fa0a9c03/attachment.htm>
- References:
- [Frama-c-discuss] how to abstract the loop
- From: luoting8609 at 163.com (罗婷)
- [Frama-c-discuss] how to abstract the loop
- From: pascal.cuoq at gmail.com (Pascal Cuoq)
- [Frama-c-discuss] how to abstract the loop
- Prev by Date: [Frama-c-discuss] how to abstract the loop
- Previous by thread: [Frama-c-discuss] how to abstract the loop
- Index(es):