A set of Graphical Apps to simplify use of JWM (Joe's Window Manager)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
JWM_Kit/doc/README_logout.txt

142 lines
6.7 KiB

######### Purpose of this document ###########################################
This document explain the process of configuring how
JWM Kit Logout and JWM Kit Time request authentication.
############ IMPORTANT NOTICE ##################################################
Please consider these command parameters defined in the document as outdated.
You can use waste a lot of time reading this document and manually configuring
your system, or you can simply configure these options with JWM Kit First Run.
######### * Graphical configuration * ##########################################
Just type the following into a your terminal:
jwmkit_first_run
Then click the "Permissions" button and select your options from the GUI.
Don't forget to press the 'save' button when done.
######### * Manual configuration * #############################################
Two options to specify how JWM Kit Logout peforms reboot and shutdown.
1. Specify a parameter when starting jwmkit_logout. example: jwmkit_logout nosu
2. Specify the parameter in the file ~/.config/jwmkit/setting_su
Details of the file ~/.config/jwmkit/setting_su
- The file configures jwmkit_logout & jwmkit_time
- Example of setting_su file: (replace sudop with your own choice)
logout=sudop
time=sudop
- The configure the line in the setting_su file using the same arguments use
for the command line parameters So for example above the line logout=sudop
means that the logout prompt will use sudo and the JWM Kit's built in
authentication prompt.
- The tools defaults are used if the lines are missing, commented out or
the setting_su file does not exist.
Notice 1: setting_su is ignored when starting jwmkit_logout with a parameter
Notice 2: Restore points do not include settings_su. It would not be wise to
including a system specific file in a restore point that can be
shared and used on different systems.
Parameters #####################################################################
- Most Parameters use /sbin/reboot and /sbin/poweroff
- symbols
* More details provided below in Advanced Parameters section
** Does not use the default /sbin/poweroff and /sbin/reboot
+ Means the option is not available for jwmkit_time
Parmeters term, sup, sudop, sysd, and elogind require a version > 20210910
default**+ (No Parameters)--used dbus with ConsoleKit **+
sudo ---------------------sudo without password for permission
gksu_r ---------------------gksu ( real ) for permssion
gksu ----------------------gksu ( fake ) for permission
gksudo_r -------------------gksudo ( real ) for permssion
gksudo --------------------gksudo ( fake ) for permission
term* ----------------------specify a terminal and permission method *
custom* --------------------specify a custom command for poweroff and reboot *
su* ------------------------use su ( terminal for password prompt ) *
sudop ----------------------use sudo with JWM Kit's built in graphic password prompt
sudoa ----------------------use sudo -A ( sudo --askpass )
sysd** ---------------------use systemd ( systemctl or timedatectl ) **
elogind**+------------------use elogind ( loginctl ) **+
x -------------------------use su-to-root -X -c
nox* -----------------------use su-to-root -c ( terminal for password prompt )
puppy**+ -------------------use wmreboot found in puppy linux **+
nosu ----------------------issue commands with out requesting permission
Alias Parameters ###############################################################
Alias parmeters have been retired to simply code. If your configuration uses an
alias parameter it will continue to work for now, but eventually this function
will be removed. Please update your configuration to use one of the parameters
listed above.
######### Advanced Parameters (with examples) #################################
* custom : custom:[reboot command]:[shutdown command]
- Example 1 : jwmkit_logout custom:~/sbin/reboot.sh:~/sbin/poweroff.sh
- Example 2 : jwmkit_logout custom:gksu ~/sbin/reboot.sh:gksu ~/sbin/poweroff.sh
* term : term:[chosen terminal]:[choosen permission tool and it's parmaters]
- Example 1 : jwmkit_logout term:xfce4-terminal:sudo
- Example 2 : jwmkit_logout term:xterm:doas
- Example 3 : jwmkit_logout "term:xterm:doas -u username"
* su : su:[chosen terminal]
- Example : jwmkit_logout su:lxterminal
uses lxterminal to issue command su -c /sbin/poweroff (or reboot)
* nox : nox:[chosen terminal]
- Example : jwmkit_logout nox:xterm
uses xterm to issue command su-to-root -c /sbin/poweroff (or reboot)
######### Examples #############################################################
jwmkit_logout ---------will use dbus with ConsoleKit
jwmkit_logout nosu ----will use /sbin/poweroff (or reboot)
jwmkit_logout term:lxterminal:sudo - use sudo and lxterminal for password input
jwmkit_logout custom:"/usr/local/reboot.sh":"/usr/local/poweroff.sh"
sudo jwmkit_logout nosu --This is kind of a hail mary command. By launching
jwmkit_logout with sudo/doas/gksudo/etc you are giving jwmkit_logout
root permission meaning it can peform a shutdown and reboot without
configuring the system. While a useful and simple option, it is not
an option you'd see recommended by a security expert. While the command
is not forbidden there are better solution.
ADDITIONAL INFO / REVIEW OF INFO ###############################################
It seems to be necessary for me to expand on the capablities of JWM Kit.
JWM Kit has no secret function for gaining the permission it needs to peform
It is the users responsiblity to ensure their system is properly configured
and to select the proper option for authentication.
----- Review of parmater requirements and how it gains permission -------------
default - Requires dbus and ConsoleKit to be installed and configured.
sudo - Requires sudo to be installed and the sudoer file must be configured
to execute poweroff and reboot without a password
gksu - Requires gksu or a "fake" gksu configuration
gksudo - Requires gksudo or a "fake" gksudo configuration
su-to-root (all parmeters) must have a su-to-root installed and configured.
no sudo - Requires permission to execute poweroff and reboot.
How do you get this permission:
1. Run JWM Kit Logout as root
2. Give poweroff and reboot execute permission
3. set UID of poweroff and reboot
sysd - Requires systemd
sudop - Requires sudo be installed and the sudoer file must be configured
su - Requires su and a terminal emulator. - pretty sure you have it ;)
NOTE : gksu and gksudo have been depreciated by most major distros. You can
use the built in sup and sudop instead.
Need help configuring one of these options? Just search online. There is an
amazing amount of tutorials/advice/etc addressing these specific configurations
on trust worthy site like stackexchange, askubuntu, various linux forums.