-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
security improvements for debian repo instructions #981
Comments
I am interested. How should I do it? |
Great @kushal140 ! The download instructions are defined in app/views/download/package.erb. If you don't already have a development environment set up, take a look at https://github.com/openSUSE/software-o-o#running-the-application-locally. If those instructions are missing something, please open a new issue. |
How to download iso fle? Due to lack of download instructions , I was unable to download Opensuse image file and set up enviornment. So , unfortunately I cannot solve the issue #981. |
It would be nice if you could give the feedback on get.opensuse.org in the correct repository, e.g. in the issue you have opened (which we've transfered to openSUSE/get-o-o).
Does that mean you don't want to try fixing the issue since you could not download the iso? There is no dependency on openSUSE distros, you could use any Rails environment you want. I don't know why the ISO download button is not working for you. This is the URL it (normally) leads to: https://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-DVD-x86_64-Current.iso |
openSUSE/get-o-o#35 |
ah, good to know |
After the information provided as above, I tried opening the file with torrent downloader , it worked. |
See #1189. |
i’d like to suggest some security improvements with regards to the auto-generated instructions for configuring debian package repositories:
/etc/apt/trusted.gpg.d/
, they should be saved to/usr/share/keyrings/
deb http://download.opensuse.org...
withdeb [signed-by=/usr/share/keyrings/<keyring.gpg>] https://download.opensuse.org...
(here, replace<keyring.gpg>
with the name of the keyring file; use HTTPS)the old and now officially deprecated way of having keyrings for third party repos in
/etc/apt/trusted.gpg.d/
is a potential security issue: it doesn’t specify which key belongs to which repository, so all package lists signed by any of those keys are accepted as trustworthy.here's a full practical example for how these instructions should rather look like:
The text was updated successfully, but these errors were encountered: