Skip to content
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

save_y2logs stores log as rw only for root #978

Open
coogor opened this issue Nov 14, 2019 · 9 comments
Open

save_y2logs stores log as rw only for root #978

coogor opened this issue Nov 14, 2019 · 9 comments
Labels
tracked Tracked elsewhere (Bugzilla, Jira, Trello)

Comments

@coogor
Copy link

coogor commented Nov 14, 2019

This has the lovely consequence, once you want to attach a saved log file to bugzilla you get an 'internal server error' , as no other user can read the log file! (and of course, you are not completely working as root, so this is a daily issue)
Maybe a chmod 666 saved_file.tat.xz as last step would fix this

@jreidinger
Copy link
Member

@coogor sadly I worry this won't be accepted by security guys as it contain many info that can be abused by potential attacker, like configuration of services, firewall configuration, etc. We filter out passwords, but there are more sensitive informations like content of journal to which common user does not have access and many others.

@coogor
Copy link
Author

coogor commented Nov 15, 2019

I see....but maybe issue a sentence that the file is rw only for root, and you may not be able to upload it if working under a different user?

@dgdavid
Copy link
Member

dgdavid commented Feb 4, 2020

Hi @coogor!

Sorry for the delay, too much stuff in the TODO queue :)

Actually, that is already mentioned in https://en.opensuse.org/openSUSE:Report_a_YaST_bug#I_attached_.2Fvar.2Flog.2FYaST2.2Fy2log_to_a_YaST2_bug.2C_and_still_I_am_asked_to_attach_y2logs._Why.3F

I'm not sure if it worth adding such information in the command output. Let's wait for more feedback and see what we finally decide.

Thanks.

@mvidner
Copy link
Member

mvidner commented Feb 4, 2020

Well, we do have a contradiction:

  1. we ask the user to upload the logs, potentially to a publicly visible bug
  2. we explicitly make the file unreadable for non-root (for "security" reasons, see bsc#673990 for the introduction of this feature 9 years ago)

@wfeldt
Copy link
Member

wfeldt commented Feb 4, 2020

I believe the link you had in mind is

https://en.opensuse.org/openSUSE:Report_a_YaST_bug#Firefox_fails_to_attach_the_.2Ftmp.2Fy2logs-.2A.tar.gz_that_I_saved_with_save_y2logs._Why.3F

We simply cannot use more liberal permissions. That you get an 'internal server error' would indicate more an issue with the web page.

A short notice about the need to adjust the permissions when you are going to upload the file might be a solution. I would nobody expect to find that cited paragraph.

@mvidner
Copy link
Member

mvidner commented Feb 4, 2020

FWIW, I find it strange to get a 500 Server error when trying to upload an unreadable file. I would expect a friendlier error from Firefox.
bugzilla500

@dgdavid
Copy link
Member

dgdavid commented Feb 4, 2020

I believe the link you had in mind is

https://en.opensuse.org/openSUSE:Report_a_YaST_bug#Firefox_fails_to_attach_the_.2Ftmp.2Fy2logs-.2A.tar.gz_that_I_saved_with_save_y2logs._Why.3F

You're right. Wrong copy&paste. Thanks @wfeldt

A short notice about the need to adjust the permissions when you are going to upload the file might be a solution. I would nobody expect to find that cited paragraph.

Which is exactly the same than @coogor requested, right?

@dgdavid
Copy link
Member

dgdavid commented Feb 6, 2020

I started a discussion in yast-devel mailing list.

@ancorgs
Copy link
Contributor

ancorgs commented Mar 15, 2021

I created a corresponding card to track this in the private trello board used by the YaST Team at SUSE to coordinate and prioritize: https://trello.com/c/uqSvbtGh/4599-improvements-in-savey2logs

@ancorgs ancorgs added the tracked Tracked elsewhere (Bugzilla, Jira, Trello) label Mar 16, 2021
@mchf mchf mentioned this issue Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tracked Tracked elsewhere (Bugzilla, Jira, Trello)
Projects
None yet
Development

No branches or pull requests

6 participants