Bug#919977: security-tracker: https://security-tracker.debian.org/tracker/data/json returns stale data

2019-02-11 Thread Julien Cristau
On 2/10/19 5:24 PM, Salvatore Bonaccorso wrote:
> Looks this is happening again (or similarly):
> 
> curl -I https://security-tracker.debian.org/tracker/data/json
> HTTP/2 200
> date: Sun, 10 Feb 2019 16:23:01 GMT
> [...]
> last-modified: Wed, 06 Feb 2019 10:18:16 GMT
> cache-control: max-age=3600
> expires: Wed, 06 Feb 2019 15:19:13 GMT
> x-clacks-overhead: GNU Terry Pratchett
> server: NetDNA-cache/2.2
> x-cache: UPDATING
> 
Purged once again, but it sounds like we'll need to investigate. :(

Cheers,
Julien



External check

2019-02-11 Thread Security Tracker
Loaded CA certificate '/etc/ssl/ca-global/ca-certificates.crt'
failed: No route to host.
failed: No route to host.
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.



Bug#919977: security-tracker: https://security-tracker.debian.org/tracker/data/json returns stale data

2019-02-11 Thread Salvatore Bonaccorso
Hi Julien,

On Mon, Feb 11, 2019 at 10:48:01AM +0100, Julien Cristau wrote:
> On 2/10/19 5:24 PM, Salvatore Bonaccorso wrote:
> > Looks this is happening again (or similarly):
> > 
> > curl -I https://security-tracker.debian.org/tracker/data/json
> > HTTP/2 200
> > date: Sun, 10 Feb 2019 16:23:01 GMT
> > [...]
> > last-modified: Wed, 06 Feb 2019 10:18:16 GMT
> > cache-control: max-age=3600
> > expires: Wed, 06 Feb 2019 15:19:13 GMT
> > x-clacks-overhead: GNU Terry Pratchett
> > server: NetDNA-cache/2.2
> > x-cache: UPDATING
> > 
> Purged once again, but it sounds like we'll need to investigate. :(

Sorry for the late reply. Thank you for workarounding it again.

Agreed on leaving the bug open until clearer what is going on?

Regards,
Salvatore



DSA candidates

2019-02-11 Thread Security Tracker
otrs2
--
agg/stable
--
borgbackup/stable
--
cacti/stable
--
cairo/stable
--
ceph/stable
--
elfutils/stable
--
exiv2/stable
--
flatpak/stable
--
freerdp/stable
--
gnome-shell/stable
--
gnutls28/stable
--
gpac/stable
--
gsoap/stable
--
guacamole-client/stable
--
gvfs/stable
--
icingaweb2/stable
--
jackson-databind/stable
--
jupyter-notebook/stable
--
kauth/stable
--
liblivemedia/stable
--
libpng1.6/stable
--
libraw/stable
--
libsdl1.2/stable
--
libsdl2/stable
--
lua5.3/stable
--
mate-screensaver/stable
--
mupdf/stable
--
mxml/stable
--
nettle/stable
--
nss/stable
--
open-build-service/stable
--
openvswitch/stable
--
paramiko/stable
--
php-horde/stable
--
php-horde-core/stable
--
php-horde-kronolith/stable
--
phpmyadmin/stable
--
poppler/stable
--
pyopenssl/stable
--
python-django/stable
--
python-gnupg/stable
--
qemu/stable
--
radare2/stable
--
rails/stable
--
rdflib/stable
--
resiprocate/stable
--
ruby-doorkeeper/stable
--
ruby-rails-admin/stable
--
ruby-rails-html-sanitizer/stable
--
ruby-zip/stable
--
runc/stable
--
salt/stable
--
slixmpp/stable
--
symfony/stable
--
tomcat8/stable
--
vips/stable
--
wordpress/stable
--
--
The above is a list of DSA candidates based on the tracker's information.
One should evaluate the candidates and either add them to dsa-needed.txt
or consider tagging them no-dsa.