Bug#966408: RFH: libidn

Package: wnpp Severity: normal I request assistance with maintaining the libidn package. Libidn is an old library for internationalized domain names processing, being phased out in favor of libidn2 that supports the new standards. I am upstream author of both libraries, and have also been

Re: [platform-testers] second libidn 1.36 pre-test

mån 2020-06-15 klockan 09:08 +0200 skrev Dagobert Michelsen: > Hi Simon, > > > Am 10.06.2020 um 20:43 schrieb Simon Josefsson via platform-testers > > : > > > > Hi! Thanks to earlier testing of the pretest of 1.36 some changes > > were > > made, espec

Libidn 1.36 released

Libidn useful and wish to contribute back. You can contribute by reporting bugs, improve the software, or donate money or equipment. Commercial support contracts for Libidn are available, and they help finance continued maintenance. Simon Josefsson Datakonsult AB, a Stockholm based privately

Libidn 1.36 released

Libidn useful and wish to contribute back. You can contribute by reporting bugs, improve the software, or donate money or equipment. Commercial support contracts for Libidn are available, and they help finance continued maintenance. Simon Josefsson Datakonsult AB, a Stockholm based privately

Re: [DFRI-listan] Integritetsvänlig identifiering

kickar min förfrågan till ändå >> har kontaktuppgifter till mig, av andra skäl, så kan ju dessa användas >> för att skicka svaret bara till mig. En annan variant som används är >> att bara skicka till min adress enligt folkbokföringen. >> >> Men min fråga gälle

Re: [DFRI-listan] Integritetsvänlig identifiering

fre 2020-06-26 klockan 18:46 +0200 skrev Peter Michanek: > Jag behöver lite hjälp med att resonera kring vad som är det mest > integritetsvänliga sättet att identifiera sig på distans. > > Enligt Dataskyddsförordningen (GDPR) så har jag ju rätt att få ut > mina personuppgifter från en

Re: second libidn 1.36 pre-test on Mac OS X

> LDADD = ../lib/libidn.la ../gl/libgnu.la Thank you again for testing! Fixed. https://git.savannah.gnu.org/cgit/libidn.git/commit/?id=86e84739c5186faf3722a0f42e1e2db27870b3a5 /Simon signature.asc Description: This is a digitally signed message part

second libidn 1.36 pre-test

Hi! Thanks to earlier testing of the pretest of 1.36 some changes were made, especially translation and build fixes. I have made another pretest to allow for updated translations and to make sure we didn't introduce regressions. Please test this as if it were the proper release:

Re: libidn 1.36 on Solaris 11.4

Bruno Haible writes: > Hi Simon, > >> > On Solaris 11.4, the build fails like this: >> ... >> > ../libtool[1720]: eval: syntax error at line 1: `|' unexpected >> > gmake[3]: *** [Makefile:1621: libidn.la] Error 3 >> > >> > The fix is to use attachment 42206 from >> >

Re: getrandom vs. crypto/gc-random

There is a lot to be said about randomness, but for the purpose of getrandom() and getentropy(), which to my knowledge aren't globally standardized (de-factor or otherwise) and well-specified what semantics re cryptographic properties they should have, I agree it make sense to keep the

Re: [platform-testers] libidn 1.36 pre-test and last call

sön 2020-05-17 klockan 15:42 +0200 skrev Dagobert Michelsen: > Hi Simon, > > Am 17.05.2020 um 13:08 schrieb Simon Josefsson via platform-testers < > platform-test...@gnu.org>: > > Hi! I have prepared a pretest of libidn 1.36, please test this as > > if

Re: libidn 1.36 on Solaris 11.4

sön 2020-05-17 klockan 18:14 +0200 skrev Bruno Haible: > On Solaris 11.4, the build fails like this: ... > ../libtool[1720]: eval: syntax error at line 1: `|' unexpected > gmake[3]: *** [Makefile:1621: libidn.la] Error 3 > > The fix is to use attachment 42206 from < >

Re: libidn 1.36 on GNU Hurd

sön 2020-05-17 klockan 18:04 +0200 skrev Bruno Haible: > On GNU/Hurd of 2019, libidn 1.36 builds fine except for two test > failures: > test-pthread_sigmask1 > test-pthread_sigmask2 > These are known (but not yet investigated). > > Unfortunately, with the way the libidn Makefiles are made,

Re: libidn 1.36 with non-GNU make

sön 2020-05-17 klockan 18:08 +0200 skrev Bruno Haible: > On glibc systems I build with GNU make, of course. > On BSD systems and Solaris, I build with GNU make, because the native > 'make' > has problem with VPATH builds. > On AIX, on the other hand, the native 'make' is good enough for most > GNU

Re: libidn 1.36 pre-test and last call

sön 2020-05-17 klockan 18:20 +0200 skrev Bruno Haible: > Hi Simon, > > > please test this as if it were the proper release: > > > > https://josefsson.org/tmp/libidn-1.36.tar.gz > > Aside from the problems reported in the other mails, it builds fine > and passes all tests on Thank you for

Re: Are ASN.1 modules code or specification?

Andreas Metzler writes: > Hello, > > Do we consider ASN.1 modules (e.g. the specification of > AttCertValidityPeriod in rfc 3281) to be code or specification? > > On one hand the rfc coyright fixup for "code components" in newer > RFCs (post Nov 2008) explicitely includes ASN.1 modules as one of

libidn 1.36 pre-test and last call

Hi! I have prepared a pretest of libidn 1.36, please test this as if it were the proper release: https://josefsson.org/tmp/libidn-1.36.tar.gz Consider this a last call for any proposed changes that you want to see in the next libidn release! /Simon signature.asc Description: PGP signature

Re: Missing character ï in the TLD-table for .no

Trond Haugen writes: > Hi, > > A good while ago we added the char 'i with umlaut', (e.g. ï / 00EF ) > to our .no permitted TLD-characters. > > Ref. https://www.norid.no/en/om-domenenavn/regelverk-for-no/#link3 > > It would be nice if someone could add that character to the .no > TLD-table so it

Re: Question about patch for CVE-2017-14062 on stretch

Tim Rühsen writes: > Hi John, > > On 15.01.20 17:22, John McCabe wrote: >> Hi,  >> I notice that a patch for CVE-2017-14062 was made available for jessie >> (security), bullseye, sid and buster but not stretch. >> >> Could I possibly ask why stretch didn't get a fix (I assume there's a >>

Re: Guix on the MNT Reform

Christopher Lemmer Webber writes: > I'm very excited to see the MNT Reform launch: > > https://www.crowdsupply.com/mnt/reform > https://www.crowdsupply.com/mnt/reform/updates/the-campaign-is-live > > Completely hackable laptop; all the designs (that are possible) are > libre, and you can

Re: What LVM support is missing?

Michael Rohleder writes: > Hey Simon! > > Simon Josefsson writes: >> I'm thinking that having the root file system on LVM may be unsupported, >> so that manual could say that, but I'm not even sure that is true. I >> haven't tried it though. Perhaps 'lv

Re: What LVM support is missing?

Marius Bakke writes: > Simon Josefsson writes: > >> The manual is quite clear that LVM support is missing: >> >> https://guix.gnu.org/manual/en/html_node/Limitations.html >> >> This held me back from using guix as the OS for my virtualization >> se

What LVM support is missing?

The manual is quite clear that LVM support is missing: https://guix.gnu.org/manual/en/html_node/Limitations.html This held me back from using guix as the OS for my virtualization servers since I use LVM for virtual machines. However, one evening I was curious how difficult it would be to fix

[PATCH] website: Update sjd.se servers.

ix.sjd.se") - (td "x86_64-linux, i686-linux") - (td - (ul - (li (a (@ (href "http://josefsson.org;)) - "Simon Josefsson") -(tr - (td "x15.sjd.se") + (td "guix-x15.sjd.se, guix-x

Bug#938069: RM: python-pyhsm -- ROM

reassign 938069 ftp.debian.org retitle 938069 RM: python-pyhsm -- ROM severity 938069 normal thanks Upstream python-pyhsm does not support python3 [1] so I believe it make sense to remove python-pyhsm from unstable. The only in-debian reverse dependency appear to be 'yubikey-val' which has

Bug#938069: RM: python-pyhsm -- ROM

reassign 938069 ftp.debian.org retitle 938069 RM: python-pyhsm -- ROM severity 938069 normal thanks Upstream python-pyhsm does not support python3 [1] so I believe it make sense to remove python-pyhsm from unstable. The only in-debian reverse dependency appear to be 'yubikey-val' which has

[PATCH] crypto/gc-pbkdf2: New module.

/crypto/gc-pbkdf2-tests create mode 100644 tests/test-gc-pbkdf2.c diff --git a/ChangeLog b/ChangeLog index 245f2a7c1..fc48c3960 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,15 @@ +2020-01-15 Simon Josefsson + + crypto/gc-pbkdf2: New module. + * MODULES.html.sh (func_all_modules

Re: please test inetutils 1.9.5 rc1

a...@gnu.org (Alfred M. Szmidt) writes: > Thank you Simon! Great initiative! Please don't forget to update the > copyright years. :-) I followed coreutils/gnulib/etc's example of using intervals for the copyright years, it avoids a lot of line wrapping. Let me know if you spot any mistakes.

Re: please test inetutils 1.9.5 rc1

Assaf Gordon writes: >> https://josefsson.org/tmp/inetutils-1.9.4.50-9410.tar.xz >> > > Test results from various systems (just running "configure && make && > make check): > > No failures on the following: > Debian 8.11 (mips64) > Debian unstable (sparc64) > FreeBSD 12.1-RELEASE-p1

Bug#926025: emacs-gtk: Crash in redisplay_internal() due to use of emacs_abort()

FWIW, I also get this crash when opening one of my folders (nnimap) using Gnus that is shipped with Emacs. A more complete backtrace can be found below. /Simon Fatal error 6: Aborted Thread 1 "emacs" received signal SIGABRT, Aborted. raise (sig=sig@entry=6) at

Re: please test inetutils 1.9.5 rc1

Simon Josefsson writes: > I noticed Guix installs ping and ping6 from inetutils with the setuid > bit enabled. There is new support for non-setuid usage in this release, > however I was not able to get it to work. Comparing with iputils' ping > it looks like what w

drop net-tools from %base-packages?

will notice if there are problems if it is applied. :-) /Simon From 3ac6e4c9853a0cbc6fb42a2d263bb03bb9583c34 Mon Sep 17 00:00:00 2001 From: Simon Josefsson Date: Wed, 1 Jan 2020 18:05:47 +0100 Subject: [PATCH] system: Drop net-tools from %BASE-PACKAGES (replaced by iproute2). * gnu/system.scm (%base

Re: please test inetutils 1.9.5 rc1

Ludovic Courtès writes: > Hello Simon, > > Simon Josefsson skribis: > >> The first release candidate of GNU InetUtils 1.9.5 is out: >> >> https://josefsson.org/tmp/inetutils-1.9.4.50-9410.tar.xz > > I’ve run: > > guix build inetutils \ > --wi

GNU SASL 1.8.1 released

is cryptographically signed by the author using an OpenPGP key identified by the following information: pub rsa3744 2014-06-22 [SC] 9AA9 BDB1 1BB1 B99A 2128 5A33 0664 A769 5426 5E8C uid [ultimate] Simon Josefsson sub rsa2048 2014-06-22 [S] sub rsa2048 2014-06-22 [E] sub rsa2048 2014-06

[SCM] GNU Inetutils branch, master, updated. inetutils-1_9_4-53-g1480573

ow. - Log - http://git.savannah.gnu.org/cgit/inetutils.git/commit/?id=1480573a908254662074865406ac6fbde4694e5d commit 1480573a908254662074865406ac6fbde4694e5d Author: Simon Josefsson Date: Wed Jan 1 15:28:54 2020 +0100 telnet: Validate supplied environment vari

[SCM] GNU Inetutils branch, master, updated. inetutils-1_9_4-51-ge1e70c8

u.org/cgit/inetutils.git/commit/?id=e1e70c849b5285419e445f6e049ef8e204a03491 commit e1e70c849b5285419e445f6e049ef8e204a03491 Author: Guillem Jover Date: Fri Aug 16 00:33:07 2019 +0200 ping: Fix typo in output Signed-off-by: Simon Josefsson diff --git a/ChangeLog b/ChangeLog ind

please test inetutils 1.9.5 rc1

Hello! The first release candidate of GNU InetUtils 1.9.5 is out: https://josefsson.org/tmp/inetutils-1.9.4.50-9410.tar.xz Please test and send reports to: bug-inetutils@gnu.org My focus is to avoid regressions since 1.9.4 so please compare any issues with the previous release:

[SCM] GNU Inetutils branch, master, updated. inetutils-1_9_4-50-g9410c4d

u.org/cgit/inetutils.git/commit/?id=9410c4d1fd6cf46c87892bb295645bc7ba675470 commit 9410c4d1fd6cf46c87892bb295645bc7ba675470 Author: Simon Josefsson Date: Wed Jan 1 14:25:36 2020 +0100 bootstrap: Updated from gnulib. diff --git a/bootstrap b/bootstrap index 8abc6b2..70fd73c 100755 --- a

[SCM] GNU Inetutils branch, master, updated. inetutils-1_9_4-45-g3857a7d

ow. - Log - http://git.savannah.gnu.org/cgit/inetutils.git/commit/?id=3857a7dc1d13927bb5280c18d324f60317ab40af commit 3857a7dc1d13927bb5280c18d324f60317ab40af Author: Simon Josefsson Date: Wed Jan 1 12:53:05 2020 +0100 bootstrap: Updated from gnulib.

Re: Telnet -E(no escape) is treating _POSIX_VDISABLE char as escape

Mikhail Bychek writes: > I stumbled upon this bug when I was trying to send binary data through > telnet connection. Came up with the trivial fix, but then I've found > identical patch: > https://github.com/freebsd/freebsd/commit/c3694d985891efb8a156e933600d23132577a053 >

[SCM] GNU Inetutils branch, master, updated. inetutils-1_9_4-43-g69196f8

u.org/cgit/inetutils.git/commit/?id=69196f8b6c02d6b5f7857db69f628c04e4b4bb58 commit 69196f8b6c02d6b5f7857db69f628c04e4b4bb58 Author: Simon Josefsson Date: Wed Jan 1 12:38:52 2020 +0100 telnet: Telnet -E(no escape) is treating _POSIX_VDISABLE char as escape. Reported by Mikh

Accepted oz 0.17.0-2 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 23 Aug 2019 05:42:17 +0200 Source: oz Binary: oz Architecture: source all Version: 0.17.0-2 Distribution: unstable Urgency: low Maintainer: Simon Josefsson Changed-By: Simon Josefsson Description: oz - install

Bug#935594: RM: yubikey-ksm -- ROM; depends on missing php mcrypt, low popcon, alternatives exists

Package: ftp.debian.org X-Debbugs-CC: pkg-auth-maintain...@lists.alioth.debian.org Please remove "yubikey-ksm" from "unstable". The package has low popcon, last upstream release in 2014, and there are better alternatives (pyhsm) already in Debian, and it depends on PHP mcrypt which has been

Bug#935593: RM: yubikey-val -- ROM; low popcon

Package: ftp.debian.org X-Debbugs-CC: pkg-auth-maintain...@lists.alioth.debian.org Please remove "yubikey-val" from "unstable". The package has low popcon, and the few people who would use the package would likely not run it without local customizations since upstream made no releases since

Bug#925709: gsasl: ftbfs with GCC-9

tags 925709 + upstream moreinfo fixed thanks Thanks for the report. I have uploaded 1.8.1-1 that from what I can tell fixes this, but it would be good if you could confirm that it builds fine for you too? /Simon signature.asc Description: This is a digitally signed message part

Bug#925709: gsasl: ftbfs with GCC-9

tags 925709 + upstream moreinfo fixed thanks Thanks for the report. I have uploaded 1.8.1-1 that from what I can tell fixes this, but it would be good if you could confirm that it builds fine for you too? /Simon signature.asc Description: This is a digitally signed message part

Accepted oz 0.17.0-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 15 Aug 2019 13:56:40 +0200 Source: oz Architecture: source Version: 0.17.0-1 Distribution: unstable Urgency: low Maintainer: Simon Josefsson Changed-By: Simon Josefsson Closes: 933509 Changes: oz (0.17.0-1) unstable

Re: Investigating the reverse dependencies of python-monotonic.

Once python3-m2crypto is in Debian, I will port oz to python3. /Simon > 13 aug. 2019 kl. 21:46 skrev Thomas Goirand : > >> On 8/13/19 12:38 PM, peter green wrote: >> Hi >> >> I've been looking at various python 2 cruft packages (packages no longer >> built by the corresponding source packages)

Bug#934512: lintian false positive for source-is-missing for pmccabe2html output

Package: lintian Hi. Lintian complains about gsasl -- see https://lintian.debian.org/maintainer/pkg-xmpp-de...@lists.alioth.debian.org.html#gsasl E: gsasl source: source-is-missing doc/cyclo/cyclo-gsasl.html line length is 567 characters (>512) The source of the following file is missing.

Bug#934512: lintian false positive for source-is-missing for pmccabe2html output

Package: lintian Hi. Lintian complains about gsasl -- see https://lintian.debian.org/maintainer/pkg-xmpp-de...@lists.alioth.debian.org.html#gsasl E: gsasl source: source-is-missing doc/cyclo/cyclo-gsasl.html line length is 567 characters (>512) The source of the following file is missing.

Bug#934333: Oz needs python-monotonic

Great! Yes I agree porting to python 3 is the best. I had completed it for oz when I realized m2crypto wasn’t python 3 ready. /Simon > 10 aug. 2019 kl. 11:45 skrev Ondrej Novy : > > Hi, > > python3-m2crypto is ready in git: > https://salsa.debian.org/python-team/modules/m2crypto > > -- >

Bug#934333: Oz needs python-monotonic

Package: python-monotonic The 'oz' package uses python 2.x because m2crypto in debian does not support python 3.x yet. Would you consider re-adding the python 2.x python-monotonic binary package, so that oz can build in sid? What was the reason for dropping python 2.x support? The changelog

Accepted gss 1.0.3-4 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 08 Aug 2019 20:07:46 +0200 Source: gss Architecture: source Version: 1.0.3-4 Distribution: unstable Urgency: low Maintainer: Debian GSS Team Changed-By: Simon Josefsson Changes: gss (1.0.3-4) unstable; urgency=low

Accepted gsasl 1.8.1-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 02 Aug 2019 15:15:01 +0200 Source: gsasl Architecture: source Version: 1.8.1-1 Distribution: unstable Urgency: low Maintainer: Debian XMPP Maintainers Changed-By: Simon Josefsson Closes: 838032 865164 Changes: gsasl (1.8.1

[PATCH] crypto/gc: Cope with libgcrypt without SM3.

* lib/gc-libgcrypt.c (gc_hash_open): Guard SM3 usage. --- ChangeLog | 5 + lib/gc-libgcrypt.c | 2 ++ 2 files changed, 7 insertions(+) diff --git a/ChangeLog b/ChangeLog index 9b994381b..539e7a09f 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2019-07-24 Simon Josefsson

Accepted shishi 1.0.2-7 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 23 Jul 2019 11:14:28 +0200 Source: shishi Architecture: source Version: 1.0.2-7 Distribution: unstable Urgency: medium Maintainer: Debian Shishi Team Changed-By: Simon Josefsson Changes: shishi (1.0.2-7) unstable; urgency

Accepted libidn2 2.2.0-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 20 Jul 2019 22:35:12 +0200 Source: libidn2 Architecture: source Version: 2.2.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Libidn team Changed-By: Simon Josefsson Closes: 882581 929879 Changes: libidn2

Bug#882581: libidn2: debian/upstream/signing-key.asc is 15M and contains unrelated public keys

al >> > --armor to include only the public key, user IDs and self-signatures, and >> > not signatures by other people, to reduce the size further). It has two >> > user >> > IDs: >> > >> > % gpg --list-packets libidn2_2.0.4-1.1.debian/upstream-s

Bug#882581: libidn2: debian/upstream/signing-key.asc is 15M and contains unrelated public keys

al >> > --armor to include only the public key, user IDs and self-signatures, and >> > not signatures by other people, to reduce the size further). It has two >> > user >> > IDs: >> > >> > % gpg --list-packets libidn2_2.0.4-1.1.debian/upstream-s

Accepted libntlm 1.5-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 20 Jul 2019 20:57:31 +0200 Source: libntlm Architecture: source Version: 1.5-2 Distribution: unstable Urgency: low Maintainer: Debian Authentication Maintainers Changed-By: Simon Josefsson Changes: libntlm (1.5-2) unstable

Accepted python-yubico 1.3.2-2 (source all) into unstable

Changed-By: Simon Josefsson Description: python-yubico - Python library for talking to Yubico YubiKeys python-yubico-tools - Tools for Yubico YubiKeys Changes: python-yubico (1.3.2-2) unstable; urgency=medium . * Acknowledge NMU. * Move package from github to salsa, updating Vcs-* URLs

Bug#879007: cyrus-imapd does not accept new connections

Hi. Just another person to confirm this bug, it took me some time to track down and then notice it was already reported. I upgraded my mail server to debian 9 and cyrus imapd always stop working after a couple of days due to this. Fortunately my mail server is pretty low traffic, so I'm hoping

Bug#879007: cyrus-imapd does not accept new connections

Hi. Just another person to confirm this bug, it took me some time to track down and then notice it was already reported. I upgraded my mail server to debian 9 and cyrus imapd always stop working after a couple of days due to this. Fortunately my mail server is pretty low traffic, so I'm hoping

Accepted jabberd2 2.7.0-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 28 Jan 2019 22:29:15 +0100 Source: jabberd2 Binary: jabberd2 jabberd2-dbgsym Architecture: source amd64 Version: 2.7.0-1 Distribution: unstable Urgency: medium Maintainer: Debian XMPP Maintainers Changed-By: Simon Josefsson

Bug#917758: A fix candidate

Hi Sergei! We worked on this precisely at the same time! I just uploaded 2.7.0-1 which incorporates upstream's solution to this problem. I think it is a cleaner approach than to patch 2.6.1, and we still have time before the freeze. Sorry for not noticing your push before doing the upload, but

Bug#917758: A fix candidate

Hi Sergei! We worked on this precisely at the same time! I just uploaded 2.7.0-1 which incorporates upstream's solution to this problem. I think it is a cleaner approach than to patch 2.6.1, and we still have time before the freeze. Sorry for not noticing your push before doing the upload, but

Accepted python-pyhsm 1.2.1-1 (source all) into unstable

: Debian Authentication Maintainers Changed-By: Simon Josefsson Description: python-pyhsm - Python code for talking to a Yubico YubiHSM hardware yhsm-daemon - YubiHSM server daemon yhsm-tools - Common files for YubiHSM applications yhsm-validation-server - Validation server using YubiHSM yhsm

Accepted yubikey-piv-manager 1.4.2-2 (source all) into unstable

-By: Simon Josefsson Description: yubikey-piv-manager - Graphical tool for managing your PIV-enabled YubiKey Changes: yubikey-piv-manager (1.4.2-2) unstable; urgency=medium . * Update Standards-Version from 3.9.8 to 4.2.1. * Move packaging to Salsa, fix Vcs-Browser/Vcs-Git/README.source URLs

Accepted ykclient 2.15-2 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 26 Sep 2018 11:34:05 +0200 Source: ykclient Binary: libykclient3 libykclient-dev Architecture: source amd64 Version: 2.15-2 Distribution: unstable Urgency: low Maintainer: Debian Authentication Maintainers Changed-By: Simon

Accepted yubico-piv-tool 1.6.2-1 (source amd64) into unstable

Maintainers Changed-By: Simon Josefsson Description: libykpiv-dev - Development files for the YubiKey PIV Library libykpiv1 - Library for communication with the YubiKey PIV smartcard ykcs11 - PKCS#11 module for the YubiKey PIV applet yubico-piv-tool - Command line tool for the YubiKey PIV

Accepted oz 0.16.0-2 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Sep 2018 15:17:57 +0200 Source: oz Binary: oz Architecture: source all Version: 0.16.0-2 Distribution: unstable Urgency: low Maintainer: Simon Josefsson Changed-By: Simon Josefsson Description: oz - install

Bug#909389: virt-inst --location security concern

Package: virtinst Version: 1:1.4.0-5 I rediscovered a problem I found a couple of years ago, and thought I'd report it properly this time. The problem is that "virt-install --location" does not verify checksums/signatures of what is downloaded, and is thus vulnerable to a network attack where

[SCM] GNU Inetutils branch, master, updated. inetutils-1_9_4-40-gaee355c

ow. - Log - http://git.savannah.gnu.org/cgit/inetutils.git/commit/?id=aee355ca51c02877b771180ab485acbb37055e87 commit aee355ca51c02877b771180ab485acbb37055e87 Author: Simon Josefsson Date: Thu Sep 6 19:06:46 2018 +0200 README-alpha (Development): Remove broken li

Accepted libntlm 1.5-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 24 Aug 2018 22:03:11 +0200 Source: libntlm Binary: libntlm0-dev libntlm0 Architecture: source Version: 1.5-1 Distribution: unstable Urgency: low Maintainer: Debian Authentication Maintainers Changed-By: Simon Josefsson

Re: [TLS] [Editorial Errata Reported] RFC8422 (5468)

I think “namedCurve” is better, it matches ASN.1 usage. /Simon > 17 aug. 2018 kl. 04:21 skrev RFC Errata System : > > The following errata report has been submitted for RFC8422, > "Elliptic Curve Cryptography (ECC) Cipher Suites for Transport Layer Security > (TLS) Versions 1.2 and Earlier". >

Bug#906138: [Pkg-auth-maintainers] Bug#906138: Bug#906138: libykneomgr: out of bounds read/writes

Done, see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906319 /Simon > 14 aug. 2018 kl. 23:51 skrev Salvatore Bonaccorso : > > Hi Simon, > >> On Tue, Aug 14, 2018 at 10:35:26PM +0200, Simon Josefsson wrote: >> Yes, removing the package from testing seems reason

Bug#906138: [Pkg-auth-maintainers] Bug#906138: Bug#906138: libykneomgr: out of bounds read/writes

Done, see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906319 /Simon > 14 aug. 2018 kl. 23:51 skrev Salvatore Bonaccorso : > > Hi Simon, > >> On Tue, Aug 14, 2018 at 10:35:26PM +0200, Simon Josefsson wrote: >> Yes, removing the package from testing seems reason

Bug#906319: remove deprecated packages

Package: ftp.debian.org Control: affects -1 src:libykneomgr The package is deprecated upstream: https://developers.yubico.com/libykneomgr/ And has unresolved security bugs: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906138 The replacement is already packaged in Debian:

Re: [TLS] [Editorial Errata Reported] RFC8422 (5466)

I would also remove the spurious paren instead -- having a MUST NOT inside a paren seems suboptimal to me. /Simon fre 2018-08-17 klockan 14:09 +1000 skrev Martin Thomson: > Looks good.  I would remove the trailing paren instead though. > On Fri, Aug 17, 2018 at 12:08 PM RFC Errata System >

Bug#906138: [Pkg-auth-maintainers] Bug#906138: libykneomgr: out of bounds read/writes

Yes, removing the package from testing seems reasonable to me. /Simon > 14 aug. 2018 kl. 20:39 skrev Salvatore Bonaccorso : > > Source: libykneomgr > Version: 0.1.8-1 > Severity: grave > Tags: security upstream > > Hi > > See https://www.x41-dsec.de/lab/advisories/x41-2018-004-libykneomgr/ >

Bug#906138: [Pkg-auth-maintainers] Bug#906138: libykneomgr: out of bounds read/writes

Yes, removing the package from testing seems reasonable to me. /Simon > 14 aug. 2018 kl. 20:39 skrev Salvatore Bonaccorso : > > Source: libykneomgr > Version: 0.1.8-1 > Severity: grave > Tags: security upstream > > Hi > > See https://www.x41-dsec.de/lab/advisories/x41-2018-004-libykneomgr/ >

Accepted yubico-pam 2.26-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 04 Aug 2018 08:50:40 +0200 Source: yubico-pam Binary: libpam-yubico Architecture: source amd64 Version: 2.26-1 Distribution: unstable Urgency: low Maintainer: Debian Authentication Maintainers Changed-By: Simon Josefsson

Accepted yubico-piv-tool 1.5.0-1 (source amd64) into unstable

Maintainers Changed-By: Simon Josefsson Description: libykpiv-dev - Development files for the YubiKey PIV Library libykpiv1 - Library for communication with the YubiKey PIV smartcard ykcs11 - PKCS#11 module for the YubiKey PIV applet yubico-piv-tool - Command line tool for the YubiKey PIV

Re: "best" ed25519/curve25519 setup?

Guilhem Moulin <guil...@fripost.org> writes: > Hi Simon, > > On Mon, 01 Jan 2018 at 14:28:34 +0100, Simon Josefsson wrote: >> I want to use ed25519/curve25519, but right now I have an offline >> master RSA key with three subkeys. Does it work well to add new >&g

Re: [Replicant] Replicant on Nexus One

Kurtis Hanna writes: >> Jeremy_Rand[m]: [...] most dumbphones haven't been audited >> for the ability of the carrier to remotely turn on the microphone, and >> we know from court documents that this capability exists on a lot of >> phones. Most Replicant supported phones have

Accepted jabberd2 2.6.1-3 (source amd64) into unstable

org> Changed-By: Simon Josefsson <si...@josefsson.org> Description: jabberd2 - Jabber instant messenger server Closes: 858935 Changes: jabberd2 (2.6.1-3) unstable; urgency=medium . * Update Vcs-Browser and Vcs-Git URLs to salsa. * Use libssl instead of libssl1.0. Closes: #858935. Ch

Re: Stepping down

Tomasz Sterna writes: > Hello. > > This e-mail is to make it official, that I am stepping down as a > maintainer of jabberd2 project. Hi! I am sorry to hear this! I want to thank you for everything you did for jabberd2, and wish you well on your

Accepted jabberd2 2.6.1-2 (source amd64) into unstable

org> Changed-By: Simon Josefsson <si...@josefsson.org> Description: jabberd2 - Jabber instant messenger server Changes: jabberd2 (2.6.1-2) unstable; urgency=medium . * Remove trailing whitespace. Fix lintian file-contains-trailing-whitespace. * Bump debhelper compat to 11. -

"best" ed25519/curve25519 setup?

Hi. I want to use ed25519/curve25519, but right now I have an offline master RSA key with three subkeys. Does it work well to add new subkeys for Ed25519/Curve25519? What is the user experience in various applications? I'm thinking MUAs, SSH, git, gpg itself, and also more exotic approaches

[Replicant] Usage notes: backup

Hi. I just found the useful wiki page https://redmine.replicant.us/projects/replicant/wiki/UsageNotes Some additions: Regarding backups, I would like to suggest adding SMS Backup+. It can backup your SMSs and call logs to an IMAP server, and restore them. Every time I reinstall Replicant,

Bug#884557: diffoscope: please support Android ROM boot.img introspection

Yay that was quick, thank you! I look forward to test it through backports once version 89 is released. /Simon

Bug#884557: diffoscope: please support Android ROM boot.img introspection

Yay that was quick, thank you! I look forward to test it through backports once version 89 is released. /Simon ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org

Bug#884557: diffoscope: please support Android ROM boot.img introspection

Den 2017-12-17 kl. 11:26, skrev Chris Lamb: Hi Simon, Hello. I'd like to see reproducible builds of Replicant (an Android clone), and diffoscope support for Android boot.img files would be useful. Sure! I was wondering if you could links/URIs to provide two, small, example files? :)

Bug#884557: diffoscope: please support Android ROM boot.img introspection

Den 2017-12-17 kl. 11:26, skrev Chris Lamb: Hi Simon, Hello. I'd like to see reproducible builds of Replicant (an Android clone), and diffoscope support for Android boot.img files would be useful. Sure! I was wondering if you could links/URIs to provide two, small, example files? :)

Bug#884557: diffoscope: please support Android ROM boot.img introspection

Package: diffoscope Version: 88 Severity: wishlist Hello. I'd like to see reproducible builds of Replicant (an Android clone), and diffoscope support for Android boot.img files would be useful. See diffoscope --debug output below. It can be done through

Bug#884557: diffoscope: please support Android ROM boot.img introspection

Package: diffoscope Version: 88 Severity: wishlist Hello. I'd like to see reproducible builds of Replicant (an Android clone), and diffoscope support for Android boot.img files would be useful. See diffoscope --debug output below. It can be done through

[Replicant] diffoscope output of two local 6.0-0003 builds

Hi all! To inspire reproducible builds of Replicant, I built 6.0-0003 twice from scratch (including two different builds of the toolchain) and ran diffoscope on the resulting images. The two builds uses the same signing key to reduce differences. https://josefsson.org/local1-vs-local2.html

Re: [Replicant] Calendar and address book syncing without google. Not working.

Hi. DAVDroid has worked really stable for me several years now. Are you sure you gave it permission to calendar/contacts? Sometimes on re- install I forget this because it doesn't ask for it directly. If you get crashes, I would suspect that something is wrong with your phone -- DAVDroid nor

Accepted libidn2 2.0.3-1 (source amd64 all) into unstable, unstable

<help-lib...@gnu.org> Changed-By: Simon Josefsson <si...@josefsson.org> Description: idn2 - Internationalized domain names (IDNA2008/TR46) command line tool libidn2-0 - Internationalized domain names (IDNA2008/TR46) library libidn2-0-dev - Internationalized domain names (I

Re: [Replicant] Fdroid 1.0.1 with privileged extension causes crashes

that whatever problem there is with the DAVDroid/CallRecorder-apps, it should not be possible for an app to cause these kind of problems with the phone. /Simon mån 2017-11-06 klockan 09:27 +0100 skrev Simon Josefsson: > lör 2017-11-04 klockan 12:09 +0100 skrev maur...@prtrc.net: > >

<    6   7   8   9   10   11   12   13   14   15   >