looks good

j'ai raté quelque chose à la création de la première clef, j'ai créé une nouvelle paire de clef voici la clef publique

I have no idea how to do it, but looks like a good plan. Apart that, in my opinion, you do a much more of what would be necessary to run nasqueron services (but it is your time, you use it like you want)

looks an interesting tool, something quite frightening is that it comes with a set of exploit, (if I understand, a common way to exploit sudo flaws).
As a shell script not even indented, it is absolutely unreadable, and more or less one have to trust the creator to not making mistake.
Moreover for full use, you have to give a sudo password in clear text ( I just don't understand the reason)
As such, I would say it would be kind of crazy to run it automatically and I would not comfortable to simply run it for myself in any way.

looks ok

I'm all but an expert in cryptography, but according to https://infosec.mozilla.org/guidelines/openssh https://infosec.mozilla.org/guidelines/openssh is good enough for mozilla

flake8 and correct bug fd->output

If I understand well, to require Tcl to do the copy, and so be free to allocate where we want the string (also in the stack), we should pass it as TCL_VOLATILE. TCL_DYNAMIC is intended to create a modifiable variable, but the allocation should saty

According to this answer on stack overflow http://stackoverflow.com/a/867996/128629

A way to conduct testing

.

• adding quote to command arguments

I wonder if the shell variables should not be quoted for example

improved commit: https://devcentral.nasqueron.org/D602

@dereckson Yes it's ok I would just nitpick that the line in the example of the README -e TRUST_ALL_PROXIES=1 \ is an unecessary example of unsecure use and a better line would be -e TRUST_ALL_PROXIES=0\ But that is really too much nitpicking for saying no to the patch

Le llvm style guide, c'est un style guide pour c++ par pour le c ?

Where is the llvm C code style guide ?

That should be easy done with the github api. No problem to do it in python3 ?

Some python idioms.

I did not understood, it was an easy task. It totally changed my mind and find it well fitted.

represent the CSV as JSON is the action not the objective it is the functionnallity implemented

I think that the objective are to vague for making something concrete.

About the browser stack, two questions (more or less related)

• Does a framework bring a lot comparing to vanilla javascript for the use ?
• Which browser we intend to support. A good target would be in my opinion Grade A support by mediawiki

I'm not sure at all that Sandstorm fit well with nasqueron way of thinking

about unit test

The official doc for trusted proxy looks like https://github.com/fideloper/TrustedProxy