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

Identify the boot loader #20

Open
pizzamaker opened this issue Jan 15, 2016 · 11 comments
Open

Identify the boot loader #20

pizzamaker opened this issue Jan 15, 2016 · 11 comments

Comments

@pizzamaker
Copy link

Whether it's BIOS, EFI, UEFI, Coreboot or Libreboot.

@woodruffw
Copy link
Owner

Do you have any thoughts on how do to this/documentation you can point me to?

@joedf
Copy link

joedf commented Jan 15, 2016

A good place to start 👍
http://sourceforge.net/projects/bootinfoscript/

@woodruffw
Copy link
Owner

Thanks!
It looks like this requires root privileges, but I'll look through it for data that can be accessed by a non-root user.

@joedf
Copy link

joedf commented Jan 15, 2016

Great :)

@pizzamaker
Copy link
Author

sudo dmidecode -s bios-vendor

Not very reliable, but it should add a basic support to it.

@woodruffw
Copy link
Owner

Both of these methods require root privileges, so I'm hesitant to add them to screenfetch-c.
I'll continue looking for filesystem indicators/another way to get this information, but I'm not
sure it's possible under the current security context that screenfetch-c is expected to be run (non-root users).

@joedf
Copy link

joedf commented Jan 16, 2016

Maybe just add a check, if it is a non root user, then simply don't display it.

@woodruffw
Copy link
Owner

That's do-able, but running screenfetch-c as root will cause additional problems (particularly with opening connections to X11 for graphical information). I also don't want to encourage people to run it as root regularly - there have been a fair share of fatal bugs in screenfetch-c and any one of them while running as a superuser could cause a crash.

I do like the idea of adding bootloader information to screenfetch-c, but unfortunately I don't think it's possible with current techniques without requiring users to trust it with heightened access. I'll leave this issue open for the time being in the event that another way of obtaining this information is found.

@joedf
Copy link

joedf commented Jan 16, 2016

I see... Usually, it's the other way around. Haha

@woodruffw
Copy link
Owner

Yeah, it's more of an architecture problem than anything else.
I wrote screenfetch-c over 3 years ago as a way to teach myself C, and its structure leaves a lot to be desired. I've been planning a rewrite for a few months that'll modularize a large part of the detection system, but I haven't had time to work on it. When I get around to that, adding detections that specifically require root access should be more doable.

@joedf
Copy link

joedf commented Jan 16, 2016

Ahhh ok :)

@woodruffw woodruffw added the 2.x label Feb 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants