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
[BUG] btop++ installer (makefile) changed home dir owner to 1000:1000, causing ssh login to fail #242
Comments
@laundmo @chmod 755 $(DESTDIR)$(PREFIX)/bin/btop The makfile is just a "script" so unless you've changed it yourself it can't possibly be the cause. |
@laundmo |
this is the relevant part of my history:
|
fuck that was a misclick i didnt mean to close |
Since you ran The makefile only copies files from the local folder to |
The problem is the folder structure in the tbz, because it contains a . and .. folder set to 1000 which when extracted causes those folders being overwritten. I suppose when making releases it just grabs the entire folder, which contains those as well so ideally when packaging these need to be excluded. Instead of all files being directly in the tbz instead putting them into a btop folder itself is probably the better option given that seems to be the norm with most other projects so unpacking never just dumps all the files into your current folder, which can be messy. @aristocratos Can you change the releases to not include those folders anymore? |
Got the same issue today.
After that I can't login anymore to my server via ssh/pubkey, login with password was working. Investigating the problem i saw that the
|
Describe the bug
After installink btop++ using the makefile from the directory /root/btop (~/btop) the owner of /root was changed to 1000:1000 causing ssh login to fail and having to restart the server in rescue mode.
To Reproduce
make install
Expected behavior
btop is installed and works, without changing permissions/owners of the /root folder
Screenshots
Info (please complete the following information):
Additional Context
SSH error caused by this:
The text was updated successfully, but these errors were encountered: