Register | Log in

golang-go.crypto

Supplementary Go cryptography libraries

Choose email to subscribe with

general

source: golang-go.crypto (main)
version: 1:0.0~git20190701.4def268-1
maintainer: Debian Go Packaging Team (DMD)
uploaders: Michael Stapelberg [DMD] – Anthony Fok [DMD]
arch: all
std-ver: 4.4.0
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 0.0~hg190-1
o-o-sec: 0.0~hg190-1+deb8u1
oldstable: 1:0.0~git20170407.0.55a552f+REALLY.0.0~git20161012.0.5f31782-1
old-bpo: 1:0.0~git20180513.94e3fad-2~bpo9+1
stable: 1:0.0~git20181203.505ab14-1
testing: 1:0.0~git20190701.4def268-1
unstable: 1:0.0~git20190701.4def268-1

versioned links

0.0~hg190-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
0.0~hg190-1+deb8u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:0.0~git20170407.0.55a552f+REALLY.0.0~git20161012.0.5f31782-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:0.0~git20180513.94e3fad-2~bpo9+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:0.0~git20181203.505ab14-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:0.0~git20190701.4def268-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

golang-golang-x-crypto-dev

action needed

Failed to analyze the VCS repository. Please troubleshoot and fix the issue. high

vcswatch reports that there is an error with this package's VCS, or the debian/changelog file inside it. Please check the error shown below and try to fix it. You might have to update the VCS URL in the debian/control file to point to the correct repository.

remote: Forbidden, 1 fatal: unable to access 'https://salsa.debian.org/go-team/packages/golang-go.crypto.git/': The requested URL returned error: 403

Created: 2019-08-13 Last update: 2019-08-16 15:43

2 security issues in bullseye high

There are 2 open security issues in bullseye.

2 important issues:

CVE-2019-11840: An issue was discovered in supplementary Go cryptography libraries, aka golang-googlecode-go-crypto, before 2019-03-20. A flaw was found in the amd64 implementation of golang.org/x/crypto/salsa20 and golang.org/x/crypto/salsa20/salsa. If more than 256 GiB of keystream is generated, or if the counter otherwise grows greater than 32 bits, the amd64 implementation will first generate incorrect output, and then cycle back to previously generated keystream. Repeated keystream bytes can lead to loss of confidentiality in encryption applications, or to predictability in CSPRNG applications.
CVE-2019-11841: A message-forgery issue was discovered in crypto/openpgp/clearsign/clearsign.go in supplementary Go cryptography libraries 2019-03-25. According to the OpenPGP Message Format specification in RFC 4880 chapter 7, a cleartext signed message can contain one or more optional "Hash" Armor Headers. The "Hash" Armor Header specifies the message digest algorithm(s) used for the signature. However, the Go clearsign package ignores the value of this header, which allows an attacker to spoof it. Consequently, an attacker can lead a victim to believe the signature was generated using a different message digest algorithm than what was actually used. Moreover, since the library skips Armor Header parsing in general, an attacker can not only embed arbitrary Armor Headers, but also prepend arbitrary text to cleartext messages without invalidating the signatures.

Please fix them.

Created: 2019-07-07 Last update: 2019-07-30 06:00

2 security issues in buster high

There are 2 open security issues in buster.

2 important issues:

CVE-2019-11840: An issue was discovered in supplementary Go cryptography libraries, aka golang-googlecode-go-crypto, before 2019-03-20. A flaw was found in the amd64 implementation of golang.org/x/crypto/salsa20 and golang.org/x/crypto/salsa20/salsa. If more than 256 GiB of keystream is generated, or if the counter otherwise grows greater than 32 bits, the amd64 implementation will first generate incorrect output, and then cycle back to previously generated keystream. Repeated keystream bytes can lead to loss of confidentiality in encryption applications, or to predictability in CSPRNG applications.
CVE-2019-11841: A message-forgery issue was discovered in crypto/openpgp/clearsign/clearsign.go in supplementary Go cryptography libraries 2019-03-25. According to the OpenPGP Message Format specification in RFC 4880 chapter 7, a cleartext signed message can contain one or more optional "Hash" Armor Headers. The "Hash" Armor Header specifies the message digest algorithm(s) used for the signature. However, the Go clearsign package ignores the value of this header, which allows an attacker to spoof it. Consequently, an attacker can lead a victim to believe the signature was generated using a different message digest algorithm than what was actually used. Moreover, since the library skips Armor Header parsing in general, an attacker can not only embed arbitrary Armor Headers, but also prepend arbitrary text to cleartext messages without invalidating the signatures.

Please fix them.

Created: 2019-05-29 Last update: 2019-07-30 06:00

2 security issues in sid high

There are 2 open security issues in sid.

2 important issues:

CVE-2019-11840: An issue was discovered in supplementary Go cryptography libraries, aka golang-googlecode-go-crypto, before 2019-03-20. A flaw was found in the amd64 implementation of golang.org/x/crypto/salsa20 and golang.org/x/crypto/salsa20/salsa. If more than 256 GiB of keystream is generated, or if the counter otherwise grows greater than 32 bits, the amd64 implementation will first generate incorrect output, and then cycle back to previously generated keystream. Repeated keystream bytes can lead to loss of confidentiality in encryption applications, or to predictability in CSPRNG applications.
CVE-2019-11841: A message-forgery issue was discovered in crypto/openpgp/clearsign/clearsign.go in supplementary Go cryptography libraries 2019-03-25. According to the OpenPGP Message Format specification in RFC 4880 chapter 7, a cleartext signed message can contain one or more optional "Hash" Armor Headers. The "Hash" Armor Header specifies the message digest algorithm(s) used for the signature. However, the Go clearsign package ignores the value of this header, which allows an attacker to spoof it. Consequently, an attacker can lead a victim to believe the signature was generated using a different message digest algorithm than what was actually used. Moreover, since the library skips Armor Header parsing in general, an attacker can not only embed arbitrary Armor Headers, but also prepend arbitrary text to cleartext messages without invalidating the signatures.

Please fix them.

Created: 2019-05-29 Last update: 2019-07-30 06:00

2 security issues in stretch high

There are 2 open security issues in stretch.

2 important issues:

CVE-2019-11840: An issue was discovered in supplementary Go cryptography libraries, aka golang-googlecode-go-crypto, before 2019-03-20. A flaw was found in the amd64 implementation of golang.org/x/crypto/salsa20 and golang.org/x/crypto/salsa20/salsa. If more than 256 GiB of keystream is generated, or if the counter otherwise grows greater than 32 bits, the amd64 implementation will first generate incorrect output, and then cycle back to previously generated keystream. Repeated keystream bytes can lead to loss of confidentiality in encryption applications, or to predictability in CSPRNG applications.
CVE-2019-11841: A message-forgery issue was discovered in crypto/openpgp/clearsign/clearsign.go in supplementary Go cryptography libraries 2019-03-25. According to the OpenPGP Message Format specification in RFC 4880 chapter 7, a cleartext signed message can contain one or more optional "Hash" Armor Headers. The "Hash" Armor Header specifies the message digest algorithm(s) used for the signature. However, the Go clearsign package ignores the value of this header, which allows an attacker to spoof it. Consequently, an attacker can lead a victim to believe the signature was generated using a different message digest algorithm than what was actually used. Moreover, since the library skips Armor Header parsing in general, an attacker can not only embed arbitrary Armor Headers, but also prepend arbitrary text to cleartext messages without invalidating the signatures.

Please fix them.

Created: 2019-05-29 Last update: 2019-07-30 06:00

2 security issues in jessie high

There are 2 open security issues in jessie.

1 important issue:

CVE-2019-11841: A message-forgery issue was discovered in crypto/openpgp/clearsign/clearsign.go in supplementary Go cryptography libraries 2019-03-25. According to the OpenPGP Message Format specification in RFC 4880 chapter 7, a cleartext signed message can contain one or more optional "Hash" Armor Headers. The "Hash" Armor Header specifies the message digest algorithm(s) used for the signature. However, the Go clearsign package ignores the value of this header, which allows an attacker to spoof it. Consequently, an attacker can lead a victim to believe the signature was generated using a different message digest algorithm than what was actually used. Moreover, since the library skips Armor Header parsing in general, an attacker can not only embed arbitrary Armor Headers, but also prepend arbitrary text to cleartext messages without invalidating the signatures.

1 issue skipped by the security teams:

CVE-2017-3204: The Go SSH library (x/crypto/ssh) by default does not verify host keys, facilitating man-in-the-middle attacks. Default behavior changed in commit e4e2799 to require explicitly registering a hostkey verification mechanism.

Please fix them.

Created: 2017-04-05 Last update: 2019-07-30 06:00

news

[2019-07-30] golang-go.crypto 1:0.0~git20190701.4def268-1 MIGRATED to testing (Debian testing watch)
[2019-07-28] Accepted golang-go.crypto 1:0.0~git20190701.4def268-1 (source) into unstable (Anthony Fok)
[2019-06-30] Accepted golang-go.crypto 0.0~hg190-1+deb8u1 (source all) into oldstable (Adrian Bunk)
[2019-01-03] golang-go.crypto 1:0.0~git20181203.505ab14-1 MIGRATED to testing (Debian testing watch)
[2019-01-01] Accepted golang-go.crypto 1:0.0~git20181203.505ab14-1 (source) into unstable (Anthony Fok)
[2018-06-19] golang-go.crypto 1:0.0~git20180614.a8fb68e-1 MIGRATED to testing (Debian testing watch)
[2018-06-16] Accepted golang-go.crypto 1:0.0~git20180614.a8fb68e-1 (source) into unstable (Alexandre Viau)
[2018-06-16] golang-go.crypto 1:0.0~git20180613.37a17fe-1 MIGRATED to testing (Debian testing watch)
[2018-06-14] Accepted golang-go.crypto 1:0.0~git20180613.37a17fe-1 (source) into unstable (Dr. Tobias Quathamer)
[2018-05-22] Accepted golang-go.crypto 1:0.0~git20180513.94e3fad-2~bpo9+1 (source all) into stretch-backports, stretch-backports (Anthony Fok)
[2018-05-21] golang-go.crypto 1:0.0~git20180513.94e3fad-2 MIGRATED to testing (Debian testing watch)
[2018-05-17] Accepted golang-go.crypto 1:0.0~git20180513.94e3fad-2 (source all) into unstable (Anthony Fok)
[2018-05-14] Accepted golang-go.crypto 1:0.0~git20180513.94e3fad-1 (source all) into unstable (Anthony Fok)
[2018-04-05] golang-go.crypto 1:0.0~git20180322.88942b9-1 MIGRATED to testing (Debian testing watch)
[2018-03-30] Accepted golang-go.crypto 1:0.0~git20180322.88942b9-1 (source) into unstable (Dr. Tobias Quathamer)
[2018-02-09] golang-go.crypto 1:0.0~git20170629.0.5ef0053-2 MIGRATED to testing (Debian testing watch)
[2018-02-03] Accepted golang-go.crypto 1:0.0~git20170629.0.5ef0053-2 (source) into unstable (Michael Lustfield)
[2017-07-06] golang-go.crypto 1:0.0~git20170629.0.5ef0053-1 MIGRATED to testing (Debian testing watch)
[2017-06-30] Accepted golang-go.crypto 1:0.0~git20170629.0.5ef0053-1 (source all) into unstable (Anthony Fok)
[2017-05-04] Accepted golang-go.crypto 1:0.0~git20170425.0.c7af5bf-1 (source) into experimental (Michael Lustfield)
[2017-05-01] Accepted golang-go.crypto 1:0.0~git20170407.0.55a552f+REALLY.0.0~git20161012.0.5f31782-1~bpo8+1 (source all) into jessie-backports->backports-policy, jessie-backports (Michael Lustfield)
[2017-04-30] golang-go.crypto 1:0.0~git20170407.0.55a552f+REALLY.0.0~git20161012.0.5f31782-1 MIGRATED to testing (Debian testing watch)
[2017-04-26] Accepted golang-go.crypto 1:0.0~git20170407.0.55a552f+REALLY.0.0~git20161012.0.5f31782-1 (source) into unstable (Michael Lustfield)
[2017-04-08] Accepted golang-go.crypto 1:0.0~git20170407.0.55a552f-1 (source) into unstable (Michael Lustfield)
[2017-02-13] Accepted golang-go.crypto 1:0.0~git20161012.0.5f31782-1~bpo8+1 (source all) into jessie-backports (Martín Ferrari)
[2016-10-21] golang-go.crypto 1:0.0~git20161012.0.5f31782-1 MIGRATED to testing (Debian testing watch)
[2016-10-15] Accepted golang-go.crypto 1:0.0~git20161012.0.5f31782-1 (source all) into unstable (Anthony Fok)
[2016-09-03] golang-go.crypto 1:0.0~git20160824.0.351dc6a-1 MIGRATED to testing (Debian testing watch)
[2016-08-28] Accepted golang-go.crypto 1:0.0~git20160824.0.351dc6a-1 (source all) into unstable (Anthony Fok)
[2016-06-14] golang-go.crypto 1:0.0~git20160607.0.77f4136-1 MIGRATED to testing (Debian testing watch)

1
2

bugs [bug history graph]

all: 0

links

homepage
buildd: logs, clang, reproducibility
popcon
browse source code
edit tags
security tracker
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 1:0.0~git20180614.a8fb68e-1
1 bug

Debian Package Tracker — Copyright 2013-2018 The Distro Tracker Developers

Report problems to the tracker.debian.org pseudo-package in the Debian BTS.

Documentation — Bugs — Git Repository — Contributing