24/6/20, Parc des Princes, jubilé Ellegaard, les vieux [notamment Lucien Lesna, Charles Terront, Jules Dubois, Antony, Eugène Renaux, Robert Coquelle, Paul Bourotte, Victor Thuau et Paul Bor] : [photographie de presse] / [Agence Rol]

Référence bibliographique : Rol, 59845

Vies de Ste Geneviève et de St Magloire.

Contient : Vie de Ste Geneviève, en vers français, par « RENAUX » ; « [C]i enseigne que li douze Apostre firent la Credo e combien chascun en dist de sa partie » ; « [C]i enseigne par vers en latin quans espous [s]ainte Anne ot et quans enfans. » — Ibid. « [C]i povéz oïr les nons des vu. sains de Bretaigne. » — Ibid. « [C]i povéz oïr les nons ans trois rois de Couloigne. » — Ibid. « [C]i oroiz pourquoi on doit plus geuner an vendredi que aus autres jours de la semene » ; « La vie monseigneur saint Magloire, qui fu arcevesque de Dol, et les miracles que i fist, translatée de latin en françois et escrite en.. mil CCC.XV., le vendredi devant la saint Andri. » Début : « Comme le tresglorieus prophete David embrasé du feu du saint Esperit... »

A statistical evaluation of the field emission for copper oxide nanostructures

A statistical data analysis methodology was developed to evaluate the field emission properties of many samples of copper oxide nanostructured field emitters. This analysis was largely done in terms of Seppen-Katamuki (SK) charts, field strength and emission current. Some physical and mathematical models were derived to describe the effect of small electric field perturbations in the Fowler-Nordheim (F-N) equation, and then to explain the trend of the data represented in the SK charts. The field enhancement factor and the emission area parameters showed to be very sensitive to variations in the electric field for most of the samples. We have found that the anode-cathode distance is critical in the field emission characterization of samples having a non-rigid nanostructure. (C) 2007 Elsevier B.V. All rights reserved.

Uma API criptográfica para aplicações embarcadas

This document presents GEmSysC, an unified cryptographic API for embedded systems. Software layers implementing this API can be built over existing libraries, allowing embedded software to access cryptographic functions in a consistent way that does not depend on the underlying library. The API complies to good practices for API design and good practices for embedded software development and took its inspiration from other cryptographic libraries and standards. The main inspiration for creating GEmSysC was the CMSIS-RTOS standard, which defines an unified API for embedded software in an implementation-independent way, but targets operating systems instead of cryptographic functions. GEmSysC is made of a generic core and attachable modules, one for each cryptographic algorithm. This document contains the specification of the core of GEmSysC and three of its modules: AES, RSA and SHA-256. GEmSysC was built targeting embedded systems, but this does not restrict its use only in such systems – after all, embedded systems are just very limited computing devices. As a proof of concept, two implementations of GEmSysC were made. One of them was built over wolfSSL, which is an open source library for embedded systems. The other was built over OpenSSL, which is open source and a de facto standard. Unlike wolfSSL, OpenSSL does not specifically target embedded systems. The implementation built over wolfSSL was evaluated in a Cortex- M3 processor with no operating system while the implementation built over OpenSSL was evaluated on a personal computer with Windows 10 operating system. This document displays test results showing GEmSysC to be simpler than other libraries in some aspects. These results have shown that both implementations incur in little overhead in computation time compared to the cryptographic libraries themselves. The overhead of the implementation has been measured for each cryptographic algorithm and is between around 0% and 0.17% for the implementation over wolfSSL and between 0.03% and 1.40% for the one over OpenSSL. This document also presents the memory costs for each implementation.