profile
viewpoint

TWL007/Amazon-downloader 1

Two perl scripts to download and parse Amazon's reviews

TWL007/jira 1

Dockerized Atlassian Jira

TWL007/gfwlist 0

The one and only one gfwlist here

TWL007/jquery-html5storage 0

jQuery HTML5 Storage

TWL007/kubernetes-rbac-policies 0

Kubernetes RBAC Policies for cluster services

TWL007/Microsoft-Azure 0

[READ ONLY] Subtree split of the SocialiteProviders/Microsoft-Azure Provider (see SocialiteProviders/Providers)

TWL007/pd 0

Placement driver for TiKV

TWL007/textmate 0

TextMate is a graphical text editor for OS X 10.7+

issue commentdocker/for-linux

Incorrect Ubuntu Bionic InRelease file

You should note, about overriding this check with commands described above (... --allow-releaseinfo-change...): those circumvent security features of APT, that have been put in place for a reason (see eg. https://manpages.debian.org/unstable/apt/apt-secure.8.en.html#INFORMATION_CHANGES).

Yes, in this case it might be just a "false alarm" caused by configuration error in Docker repository release process, but it also could be a (semi-)successful breach and eg. watering hole attack.

Anyways, this currently blocks eg. automated system upgrades and stuff like that, so hopefully they fix it soon...

You are right, it has security risks. I am doing test now, so later I will wipe out host and re=install everything. For other people, they do need to know if they decide to do this or not.

TWL007

comment created time in 5 months

issue commentdocker/for-linux

Incorrect Ubuntu Bionic InRelease file

sudo apt-get --allow-releaseinfo-change update -y

Strange, it did work for me. apt-get --allow-releaseinfo-change update

TWL007

comment created time in 5 months

issue commentdocker/for-linux

Incorrect Ubuntu Bionic InRelease file

Current Repo label:

500 https://download.docker.com/linux/ubuntu bionic/stable amd64 Packages release o=Docker,a=bionic,l=Docker EE,c=stable,b=amd64 origin download.docker.com

TWL007

comment created time in 5 months

issue commentdocker/for-linux

Incorrect Ubuntu Bionic InRelease file

Seems to affect other releases too, head of InRelease file for Ubuntu Disco

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Architectures: armhf arm64 amd64 
Components: test edge stable nightly
Date: Thu, 10 Oct 2019 01:08:14 +0000
Label: Docker EE
Origin: Docker
Suite: disco

and for Debian Buster

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Architectures: armhf arm64 amd64 
Components: test edge stable nightly
Date: Thu, 10 Oct 2019 01:01:59 +0000
Label: Docker EE
Origin: Docker
Suite: buster
MD5Sum:

It should be also noted: if someone now installs the repository, she will probably get similar complaints if/when Label changes back to Docker CE, ie. "something should be done ASAP", or users will need to fix this manually on many setups...

I agree. I also send a meesage in the slack channel.

TWL007

comment created time in 5 months

issue openeddocker/for-linux

Incorrect Ubuntu Bionic InRelease file

<!-- This issue tracker is for bug reports and feature requests. For questions, and getting help on using docker:

  • Docker documentation - https://docs.docker.com
  • Docker Forums - https://forums.docker.com
  • Docker community Slack - https://dockercommunity.slack.com/ (register here: http://dockr.ly/community)
  • Post a question on StackOverflow, using the Docker tag -->
  • [x] This is a bug report

<!-- DO NOT report security issues publicly! If you suspect you discovered a security issue, send your report privately to security@docker.com. -->

Expected behavior

The label is in the InRelease should be Docker CE.

Actual behavior

The label is in the InRelease is Docker EE. This problem will only affect Ubuntu Bionic for now, here is the file location: https://download.docker.com/linux/ubuntu/dists/bionic/InRelease

Steps to reproduce the behavior

<!-- Describe the exact steps to reproduce. If possible, provide a minimum reproduction example; take into account that others do not have access to your private images, source code, and environment.

REMOVE SENSITIVE DATA BEFORE POSTING (replace those parts with "REDACTED") -->

Output of docker version:

(paste your output here)

Output of docker info:

(paste your output here)

Additional environment details (AWS, VirtualBox, physical, etc.)

created time in 5 months

more