[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#854022: marked as done (Not able anymore to contact debian bts)

Your message dated Sun, 6 Dec 2020 18:10:43 +0100
with message-id <7c7a52be-2c52-1790-60e1-65737eb458f7@web.de>
and subject line Re: Bug#854022: Not able anymore to contact debian bts)
has caused the Debian Bug report #854022,
regarding Not able anymore to contact debian bts
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
854022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854022
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Package: reportbug
Version: 7.1.4
Severity: important

Reportbug is not able to contact bts and download already fieled bugs.

The error is:
Unable to connect to Debian BTS (error: "SSLError(1, '[SSL:
CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:720)')");
continue [y|N|?]?

- -- Package-specific info:
** Environment settings:
EDITOR="vim"
PAGER="less"
VISUAL="vim"
EMAIL="Klaus Ethgen <Klaus@Ethgen.de>"
DEBFULLNAME="Klaus Ethgen"
INTERFACE="text"

** /home/klaus/.reportbugrc:
reportbug_version "2.20"
mode expert
ui text
realname "Klaus Ethgen"
email "Klaus@Ethgen.de"

- -- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.1 (SMP w/8 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages reportbug depends on:
ii  apt                1.4~beta4
ii  python3-reportbug  7.1.4
pn  python3:any        <none>

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail                                 <none>
ii  debconf-utils                              1.5.60
ii  debsums                                    2.2
ii  dlocate                                    1.07+nmu1
pn  emacs23-bin-common | emacs24-bin-common    <none>
ii  exim4                                      4.89~RC1-1
ii  exim4-daemon-light [mail-transport-agent]  4.89~RC1-1
ii  file                                       1:5.29-3
ii  gir1.2-gtk-3.0                             3.22.7-2
pn  gir1.2-vte-2.91                            <none>
ii  gnupg                                      2.1.18-3
ii  python3-gi                                 3.22.0-2
ii  python3-gi-cairo                           3.22.0-2
pn  python3-gtkspellcheck                      <none>
ii  python3-urwid                              1.3.1-2+b1
ii  xdg-utils                                  1.1.1-1

Versions of packages python3-reportbug depends on:
ii  apt                1.4~beta4
ii  file               1:5.29-3
ii  python3-debian     0.1.30
ii  python3-debianbts  2.6.1
ii  python3-requests   2.12.4-1
pn  python3:any        <none>

python3-reportbug suggests no packages.

- -- Configuration Files:
/etc/reportbug.conf changed:
submit
mutt
query-bts
cc
config-files
compress
sign gpg
verify
mode expert
mbox_reader_cmd "mutt -f %s"


- -- no debconf information

- -- 
Klaus Ethgen                                       http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16            Klaus Ethgen <Klaus@Ethgen.ch>
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-----BEGIN PGP SIGNATURE-----
Comment: Charset: ISO-8859-1

iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAliULWwACgkQpnwKsYAZ
9qxfFAv9FjcJXlTZn6juZVOBSNsjg7AgDFWHEKowbWmDb8w2ka389g+bn4uN3fiA
7oJubaUUdY8uTk18xTtg4Vkj15WAI8c/WrY7UiwqvjVe0lg5SmpDLqIWH93LosqF
o5ujjQw8zFOprantqOJD5nJJoQwCEQ3BwI66ACJSoqHeC0AX4uTNmcMPURrkXUgl
nPR+KGN0mSaPAJnXoJiIiNtejvA9M5LJhX6nNIksKZiugBrSMApqk/7YJp4VZzT5
TJ/HnKPtsK0QwSlAIBN/Rfj6CaWV8SxFEv7rlsPK81woqTf4HXiMH0wOVdth3asM
ay46P//q/psCUx9zvodfAAxKn5YLIYhKWnlHrVQ8KHl6yd+HV8NGjtYGmpF5Oz4p
InPS6PJTSgeF1HikhRsof5SGBQ2KDsM613pnWVqoA/hkvwtu6aJv5YfL9SqOZlBK
WFJclcg01daKlbwn9wWdEfWGbp8Moqj3tyh9pnRYoMhOWH9GKrDiLIPQWgMMnw2V
Sew/ZiZL
=STz+
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
On 3 Feb 2017 Klaus Ethgen wrote:

Am Fr den  3. Feb 2017 um 19:56 schrieb Don Armstrong:

As near as I can tell, the certificates for the BTS are just fine:



% openssl s_client -showcerts -connect bugs.debian.org:443 </dev/null|openssl x509 -text|grep -e verify -e GMT -i
depth=2 O = Digital Signature Trust Co., CN = DST Root CA X3
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3
verify return:1
depth=0 CN = bugs.debian.org
verify return:1
DONE
            Not Before: Jan  6 10:58:00 2017 GMT
            Not After : Apr  6 10:58:00 2017 GMT


Ah, so debian changed the CA? Was that published somewhere? I do not
usually trust certificates coming from a different CA.


So if you're getting this error, it's either that reportbug is
connecting to the wrong URI, you don't have the appropriate CAs
installed, or something else is going on.


Well, as I told, I do not trust CAs per default. I usually check
certificates very good. As good as possible. And I cannot find any
documentation that debian switched or want to switch.

So, yes, that might be the reason, but please do document that proper.
I understand that there is no problem with reportbug here, and no more information has been provided in the last nearly four years either. Hence I'm closing this bug.
--- End Message ---
Reply to: