- 21 Oct, 2019 1 commit
-
-
anarcat authored
New translations from weblate: de, el, nb_NO, uk. Translation fixes: es, nl. None reviewed.
-
- 06 Jul, 2019 1 commit
-
-
THANOS SIOURDAKIS authored
-
- 03 Sep, 2018 1 commit
-
-
Allan Nordhøy authored
Currently translated at 100.0% (102 of 102 strings)
-
- 22 Jun, 2018 16 commits
-
-
Allan Nordhøy authored
Currently translated at 100.0% (102 of 102 strings)
-
Allan Nordhøy authored
Currently translated at 61.7% (63 of 102 strings)
-
Frans de Jonge authored
Currently translated at 56.8% (58 of 102 strings)
-
Jan Christian Grünhage authored
Currently translated at 2.9% (3 of 102 strings)
-
Jan Christian Grünhage authored
-
Марс Ямбар authored
Currently translated at 0.9% (1 of 102 strings)
-
Марс Ямбар authored
-
Allan Nordhøy authored
Currently translated at 56.8% (58 of 102 strings)
-
Allan Nordhøy authored
Currently translated at 55.8% (57 of 102 strings)
-
Allan Nordhøy authored
Currently translated at 54.9% (56 of 102 strings)
-
Allan Nordhøy authored
Currently translated at 32.3% (33 of 102 strings)
-
Allan Nordhøy authored
Currently translated at 12.7% (13 of 102 strings)
-
Allan Nordhøy authored
-
Sylvain Lesage authored
Currently translated at 100.0% (102 of 102 strings)
-
anarcat authored
-
anarcat authored
-
- 18 Jun, 2018 4 commits
-
-
anarcat authored
-
anarcat authored
-
anarcat authored
-
anarcat authored
The SigSpoof vulnerability found in GnuPG also affects Monkeysign, but in a lesser way. We check signatures only in one place: when we import images. This is a corner use case that is probably quite uncommon and since it requires access to the file in itself, it's likely there are already other ways to import arbitrary signatures into monkeysign. Still, we play it safe and disable the "verbose" mode that can possibly be enabled in `gnupg.conf` as recommended by the reporter, Marcus Brinkmann.
-
- 20 Nov, 2017 4 commits
-
-
Tobias Rueetschi authored
-
Tobias Rueetschi authored
- 04 Oct, 2017 2 commits
-
-
-
anarcat authored
-
- 12 Aug, 2017 2 commits
-
-
anarcat authored
we would previously copy the gpg.conf to the temporary keyring, which works, but then when we actually sign the key, we iterate over the secrets to figure out which key to use, and then the default-key setting is ignored. instead, we simply parse the gpg.conf by hand to detect the setting. we could have used gpgconf, but this doesn't seem easier to parse and adds yet another dependency. i would argue it is easier and simpler to parse the config file than to shell out to yet another obscure gpg command. this is a finalization of #721599
-
anarcat authored
-
- 09 Aug, 2017 1 commit
-
-
anarcat authored
-
- 06 Jun, 2017 1 commit
-
-
anarcat authored
-
- 02 Apr, 2017 1 commit
-
-
anarcat authored
-
- 30 Mar, 2017 1 commit
-
-
anarcat authored
-
- 29 Mar, 2017 4 commits
-
-
Heimen Stoffels authored
Currently translated at 19.6% (20 of 102 strings)
-
Heimen Stoffels authored
-
Tobias Rueetschi authored
-
- 28 Jan, 2017 1 commit
-