Start adding CV

Using an existing 1-page ODT as basis, but with more sentences and
fewer keyword salads.

1 files changed, 48 insertions, 0 deletions

diff --git a/personal/cv/cv.org b/personal/cv/cv.org
new file mode 100644
index 0000000..ed6de01
--- /dev/null
+++ b/personal/cv/cv.org
@@ -0,0 +1,48 @@
+I strive to develop reliable and maintainable software,
+with an eye toward improving the tools of our craft.
+
+* Experience
+** 2014 – present: software engineer at Airbus CyberSecurity
+*** Research
+I took part in the [[https://paclido.fr][PACLIDO project]], a French government-funded project
+gathering industrial and academic partners in order to design and
+implement *lightweight authenticated encryption algorithms* and
+protocols.
+
+During the course of this project,
+
+- I implemented the reference version of Lilliput-AE, our submission
+  to the [[https://csrc.nist.gov/projects/lightweight-cryptography][NIST Lightweight Cryptography Standardization Process]].
+
+- I described this implementation in [[https://csrc.nist.gov/CSRC/media/Projects/Lightweight-Cryptography/documents/round-1/spec-doc/LILLIPUT-AE-spec.pdf][the algorithm's specification
+  document]], comparing its performance to that of Ascon and ACORN, the
+  lightweight winners of the [[https://competitions.cr.yp.to/caesar-submissions.html][CAESAR competition]].
+
+- I extended the [[https://www.cryptolux.org/index.php/FELICS][FELICS]] benchmarking framework to support AEAD
+  algorithms; we [[https://gitlab.inria.fr/minier/felics-ae/][published this fork]] and presented these improvements
+  at the [[https://csrc.nist.gov/CSRC/media/Presentations/felics-ae-a-framework-to-benchmark-lightweight/images-media/session3-huynh-felics-ae.pdf][NIST LWC Workshop 2019]].
+
+- I developed optimized software implementations for Lilliput-AE on
+  the 16-bit MSP430 platform.
+*** Industrial development
+For four years, I helped develop a network monitoring appliance.  My
+main role was *maintaining the codebase* for an in-house rule-matching
+engine: designing and implementing features, fixing bugs…  Over the
+course of the project, I took part in many over activities:
+
+- I helped our project transition from manual software packaging to
+  full-blown continuous integration,
+
+- I contributed extensively to our integration test suite,
+
+- I studied some mechanisms to improve the system's security (Secure
+  Boot, TPMs) and helped implement others (LXC containers).
+
+- I reviewed all uses of cryptography in the system as part of our
+  security certification process; this allowed me to get a good grasp
+  of how filesystem encryption, VPN, or repository authentication are
+  configured in a free software distribution.
+
+- I supported our license team in assessing our use of free and open
+  source software.
+