You are not logged in.
@dice: Thanks for the info on how to get the key into the initramfs to avoid having to give the password more than once. That might get included in a future version of the installer. It already does full-disk encryption.
you're welcome, i followed this quide not long ago and can confirm working in beowulf . Would be a nice addition to refractainstaller.
thanks fsmithred i will look into those today.
head on a stick, yes i forgot to remove those. I copied over that part of the script from anther script which is using them. Thanks for pointing that out and cheers for the whiptail reference.
And no, there isn't any "more configuration to do"; ecyptfs hooks into PAM (I think) and decrypts and mounts my /home/user seamlessly, whether it's a console or desktop log-in. I've never had an issue, and I've used this method since before I moved to Devuan - in fact it used to be the default behaviour on Ubuntu if you selected to encrypt your home during installation.
I meant if it were to be a part of an installer.
There are methods to create full disk encryption, i would prefer to have the whole disk encrypted if it were a laptop.
See here for a nice guide: https://www.dwarmstrong.org/fde-debian/
This method only asks for a password once and if it fails, grub goes straight to recovery.
This something to make my life easier, it just basically opens and mounts/unmounts a luke encrypted usb drive, could be any sort of pluggable drive i suppose. Thinking of adding some options to easily create full disk encryption to go along with these options as well.
Just thought i would share.
all that needs to be done is to have a usb or disk with a partuuid and a label and those are the parameters it opens and mounts by. But these parameters need to be added to the script manually.
so usage is as root cryptmount -m to open and mount
and cryptmount -u to unmount and close
#!/bin/sh
u=$(logname)
crypt_mount () {
cryptsetup luksOpen "/dev/disk/by-partuuid/00000-1" usb;
mount -L "BACKUPS" /media/"${u}"
}
crypt_umount () {
umount -R /media/"${u}";
cryptsetup close usb
}
while getopts ":mu" opt; do
case "${opt}" in
m ) crypt_mount
;;
u ) crypt_umount
;;
*)
;;
esac
done
I would like to explore how to make this a kind of menu where you could pick available devices to encrypt and mount
ecryptfs looks user specific, not something i would want added to an installer. ecryptfs might work for ones home directory but cryptsetup is the gold standard imo. I believe there is a lot more configuration to be done for ecryptfs as you need to first create the encryption while logged in then log out and migrate the user from another account probably root and then unwrap the passphrase, that seems out of bounds for an installer imo.
dice wrote:if i want to edit a file as root
Why not just use sudoedit? Oh no, wait...
Well if one does not want to use sudo, they could edit a file that way using su.
There is also a minimalist alternative to privilege escalation that allows normal users
to run other programs as a different user and group..
https://github.com/parazyd/sup
Ive also started to create scripts to handle everyday tasks from the user account using su.
For instance if i want to edit a file as root i have the below script i call "sue"
#!/bin/sh
su -c "$EDITOR $@"
To be on topic, and probably to repeat earlier stuff which I'm not bothering to read: A lot of packages drop files into systemd locations. It doesn't harm a system to have /usr/lib/systemd/system/$FOOBAR.service as a file. It just doesn't help either.
There's rumblings of a devuan-sanity-systemctl package that will provide a systemctl translator script to actually provide the real behavior from the "systemctl" invocations, for the Ceres (unstable) release, but I don't know if that's going anywhere. If you download that yourself, be sure to put it in /usr/bin and not /usr/sbin. But be advised that the script will just run the real "service $FOOBAR stop" commands and not actually use the /usr/lib/systemd/system/$FOOBAR.service service entries. It isn't systemd, after all.
If you would like to contribute to how Devuan operates, we meet weekly. You can read the announcement for how to attend the meetings: https://lists.dyne.org/lurker/message/2 … 7c.en.html.
This reads to me like damage control. Systemd is causing devuan to mitigate the blow systemd is going to strike in the future?
if you havent apt updated in a while today would be the day to do it if you use sudo.
https://haxf4rall.com/2021/01/27/cve-20 … ity-alert/
On January 27, 2021, RedHat issued a risk notice for heap-based buffer overflow vulnerability, the vulnerability number is CVE-2021-3156. The vulnerability level is a high risk. CVSS v3 Base Score is 7.0.
Attackers can use heap-based buffer overflow vulnerability to gain root privileges after obtaining server permissions. Currently, Debian has fixed the vulnerability, Centos is still affected.Vulnerability Detail
A heap-based buffer overflow was found in the way sudo parsed command line parameters. Any local user (normal user and system user, sudoer and non-sudoers) can exploit this vulnerability without authentication, and the attacker does not need to know the user’s password. Successfully exploiting this vulnerability to gain root privileges.How to exploit this bug
Log in to the system as a non-root user and use the command sudoedit -s /
-If you see an error that starts with sudoedit:, it indicates that there is a vulnerability.
-If you see an error starting with usage:, then the patch has taken effect.
Demo
Affected version
sudo: 1.8.2 – 1.8.31p2
sudo: 1.9.0 – 1.9.5p1
Solution
In this regard, we recommend that users upgrade sudo to the latest version in time.
The post CVE-2021-3156: Sudo Heap-Based Buffer Overflow Vulnerability Alert appeared first on InfoTech News.Post navigation
dice wrote:GLib-GIO-Message: 23:45:04.055: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
Is the dconf-gsettings-backend package installed?
And how did you install MATE? I would use the desktop task:
# apt install task-mate-desktop
^ That installs everything required for the full MATE desktop, just as if it had been selected from a netinstall ISO image.
Yeah i just installed it from the commanline sudo apt install mate-desktop which i thought should bring in all the dependancies, obviously not though as dconf-gsettings-backend was missing. Thanks this is solved.
Thanks anyway rolfie.
Just to add, i installed this on top of an already established system that is only using a window manager setup, so it is mostly just basic X stuff being used, xinitrc, dwm, st terminal, web browser.
same thing, apt wants to remove mate. It might need to be done, doesnt make much sense though.
thanks for helping me rolfie, but i had the issue of not being able to change the wallpaper and themes before i installed consolekit.
If i apt install libpolkit-gobject-elogind-1-0
this happens...
sudo apt install libpolkit-gobject-elogind-1-0
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
accountsservice blueman bluez caja-eiciel caja-extensions-common caja-gtkhash caja-image-converter caja-open-terminal
caja-rename caja-seahorse caja-sendto caja-wallpaper compton dconf-cli dconf-editor eom eom-common ethtool ffmpegthumbnailer
fonts-cantarell gir1.2-appindicator3-0.1 gir1.2-bamf-3 gir1.2-caja gir1.2-caja-2.0 gir1.2-wnck-3.0 gtkhash libaccountsservice0
libappindicator3-1 libayatana-appindicator3-1 libayatana-ido3-0.4-0 libayatana-indicator3-7 libb2-1 libcgmanager0
libck-connector0 libconfig9 libcpufreq0 libcryptui0a libdbus-1-dev libdbus-glib-1-dev libdbus-glib-1-dev-bin libdw1
libffmpegthumbnailer4v5 libgssdp-1.0-3 libgucharmap-2-90-7 libgupnp-1.0-4 libimagequant0 libmate-slab0 libmate-window-settings1
libmateweather-common libmateweather1 libnih-dbus1 libnih1 liboobs-1-5 libsbc1 libx86-1 menu menu-xdg pm-utils
pulseaudio-module-bluetooth python-caja python-caja-common python3-cairo python3-dbus python3-gi-cairo python3-olefile
python3-pil python3-psutil python3-xdg python3-xlib seahorse seahorse-daemon system-tools-backends vbetool
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
caja-admin consolekit gnome-system-tools libpam-ck-connector libpolkit-backend-consolekit-1-0 libpolkit-gobject-consolekit-1-0
lightdm mate-applet-brisk-menu mate-applets mate-control-center mate-core mate-desktop-environment mate-desktop-environment-core
mate-desktop-environment-extra mate-desktop-environment-extras mate-dock-applet mate-indicator-applet mate-panel mate-polkit
mate-polkit-bin mate-power-manager mate-settings-daemon mate-settings-daemon-dev mate-tweak mate-window-buttons-applet
mate-window-menu-applet mate-window-title-applet policykit-1 policykit-1-gnome rtkit
The following NEW packages will be installed:
libpolkit-gobject-elogind-1-0
0 upgraded, 1 newly installed, 30 to remove and 0 not upgraded.
Need to get 44.7 kB of archives.
After this operation, 19.8 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
No, it's not all things!
But others lines concern iface lo and eth0. Do you want really?!The file start with this line:
source /etc/network/interfaces.d/* (…) allow-hotplug wlx00e0250d7ef2 iface wlx00e0250d7ef2 inet dhcp # wpa-driver wext # wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf wpa-ssid SH wpa-psk ***xyz***
well when someone tells me a story i dont want to hear just the end of it !
Beowulf.
I installed consolkit after i installed the full mate desktop, was like over 300 megabytes in size in total for mate desktop, so many dependancies. If i try to uninstall consolekit it wants to remove most of mate now, that is really stupid.
release notes dont say anything about mate desktop. It looks like dbus is having issues connecting to mate?
is that all you have in /etc/network/interfaces: ?
i dont believe you need the wpa-ssid and wpa-psk in /etc/wpa_supplicant/wpa_supplicant.conf if you already have them in /etc/network/interfaces ?
see head on a sticks comment from another thread on wpagui wpa_supplicant.
I thought i would try the mate desktop out, it installed fine but i cannot change the themes, background wallpaper. Any changes i make do not stick, even the wallpaper wont change when i click a background in the desktop background settings ?
Im not familiar with the mate desktop, im just setting this up for a friend and thought the mate desktop would be good for a mate.
I have elogind installed and consolekit, not sure if both should be installed. Xsession errors below.
Xsession: X session started for dave at Tue 26 Jan 23:45:03 AEST 2021
localuser:dave being added to access control list
dbus-update-activation-environment: systemd --user not found, ignoring --systemd argument
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: systemd --user not found, ignoring --systemd argument
dbus-update-activation-environment: setting USER=dave
dbus-update-activation-environment: setting LANGUAGE=en_AU:en
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting HOME=/home/dave
dbus-update-activation-environment: setting DESKTOP_SESSION=lightdm-xsession
dbus-update-activation-environment: setting XDG_SESSION_COOKIE=laptop-1611668703.321140-1129740149
dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-DsOq1ofy35,guid=e3c35923a01060c1225c15f560101cdf
dbus-update-activation-environment: setting GNOME_KEYRING_CONTROL=/home/dave/.cache/keyring-ZPF0X0
dbus-update-activation-environment: setting LOGNAME=dave
dbus-update-activation-environment: setting GTK_OVERLAY_SCROLLING=0
dbus-update-activation-environment: setting LIBOVERLAY_SCROLLBAR=0
dbus-update-activation-environment: setting PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting LANG=en_AU.UTF-8
dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=lightdm-xsession
dbus-update-activation-environment: setting XAUTHORITY=/home/dave/.Xauthority
dbus-update-activation-environment: setting XDG_GREETER_DATA_DIR=/var/lib/lightdm/data/dave
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting GDMSESSION=lightdm-xsession
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting PWD=/home/dave
dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/mate:/usr/local/share/:/usr/share/
(x-session-manager:2098): dbind-WARNING **: 23:45:03.883: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
x-session-manager[2098]: WARNING: Unable to find provider '' of required component 'dock'
GLib-GIO-Message: 23:45:04.055: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
(mate-settings-daemon:2139): dbind-WARNING **: 23:45:04.065: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(marco:2142): dbind-WARNING **: 23:45:04.422: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GLib-GIO-Message: 23:45:04.425: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
(mate-panel:2151): dbind-WARNING **: 23:45:04.619: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GLib-GIO-Message: 23:45:04.624: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
(caja:2176): dbind-WARNING **: 23:45:04.959: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GNOME_KEYRING_CONTROL=/home/dave/.cache/keyring-ZPF0X0
SSH_AUTH_SOCK=/home/dave/.cache/keyring-ZPF0X0/ssh
GNOME_KEYRING_CONTROL=/home/dave/.cache/keyring-ZPF0X0
SSH_AUTH_SOCK=/home/dave/.cache/keyring-ZPF0X0/ssh
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
GNOME_KEYRING_CONTROL=/home/dave/.cache/keyring-ZPF0X0
SSH_AUTH_SOCK=/home/dave/.cache/keyring-ZPF0X0/ssh
(mate-volume-control-applet:2189): dbind-WARNING **: 23:45:05.021: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(mate-screensaver:2191): dbind-WARNING **: 23:45:05.027: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GLib-GIO-Message: 23:45:05.029: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
(mate-maximus:2203): dbind-WARNING **: 23:45:05.033: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GLib-GIO-Message: 23:45:05.087: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
no maximize: true
(mate-power-manager:2208): dbind-WARNING **: 23:45:05.102: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(polkit-mate-authentication-agent-1:2206): dbind-WARNING **: 23:45:05.107: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GLib-GIO-Message: 23:45:05.130: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
Initializing caja-open-terminal extension
GLib-GIO-Message: 23:45:05.221: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
(mate-optimus-applet:2190): dbind-WARNING **: 23:45:05.445: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(blueman-applet:2204): dbind-WARNING **: 23:45:05.446: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
No nvidia-settings and prime-select detected.
GLib-GIO-Message: 23:45:05.614: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
(mate-power-manager:2208): Gdk-CRITICAL **: 23:45:05.738: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
Initializing caja-image-converter extension
RuntimeError: object at 0x7f9a84ae9370 of type RenameMenu is not initialized
(mate-appearance-properties:2309): dbind-WARNING **: 23:45:09.220: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(mate-appearance-properties:2307): dbind-WARNING **: 23:45:09.221: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GLib-GIO-Message: 23:45:09.368: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
(mate-appearance-properties:2309): Gtk-WARNING **: 23:45:13.239: Theme parsing error: gtk.css:1368:85: 'font-feature-settings' is not a valid property name
(mate-appearance-properties:2309): Gtk-WARNING **: 23:45:13.397: Theme parsing error: gtk.css:1350:88: 'font-feature-settings' is not a valid property name
I/O error : No such file or directory
I/O error : No such file or directory
(caja:2314): dbind-WARNING **: 23:45:30.206: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
RuntimeError: object at 0x7f9a84ae9370 of type RenameMenu is not initialized
(caja:2176): Gtk-CRITICAL **: 23:45:40.228: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed
(caja:2176): Gtk-CRITICAL **: 23:45:40.229: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed
(caja:2176): Gtk-CRITICAL **: 23:45:40.229: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed
(caja:2176): Gtk-CRITICAL **: 23:45:40.229: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed
(caja:2176): Gtk-CRITICAL **: 23:45:40.229: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed
(caja:2176): Gtk-CRITICAL **: 23:45:40.229: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed
Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen!
(blueman-applet:2204): Gdk-CRITICAL **: 23:46:19.703: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
[1611668704,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application
Gdk-Message: 23:46:19.776: mate-volume-control-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Gdk-Message: 23:46:19.777: mate-maximus: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Gdk-Message: 23:46:19.777: mate-screensaver: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Gdk-Message: 23:46:19.779: blueman-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
what is the output of the file /etc/network/interfaces
as ralph mentions you should read the manual for wpa_supplicant
Can't reach this website. ChangTzu, do you have another link?
Probably was something similar to privacytools.io
Hei Andy, I'll check, back soon.
Oh noes, F_Sauce might be caught in a time warp.
dice wrote:I have some old hardware i use on a daily basis with devuan, lately ive found that if i use anything bleeding edge like archlinux, voidlinux, artixlinux, i will get complete lockups/freezes but using devuan stable, debian stable my old machine runs fine. I cant figure this out. I have been running the backported 5.9 kernel for a few days with no issues, yet if i run archlinux linux-lts or even in voidlinux the 4.19 kernel it will just lockup/freeze unable ssh or get a tty. Might be time to update but as long as devuan still works i dont see a reason too, im hoping when chimeara becomes stable i wont have these issues and can run the computer for another few years.
Small problem, voidlinux isn't bleeding edge, its rolling release with a focus on stability.
So I guess you could say its semi rolling release. I think? I haven't used it a whole lot, but, I also noticed that using musl's voidlinux is a little more buggy.
Yeah it says stable rolling release, for me not so stable and this was not the musl variation but the glibc variation via netinstall (yes it can be done in voidlinux, similar to the arch way). I installed it the other day and no word of a lie the computer froze in the first 2 minutes. Basic xfce4 install. Im not about to complain to them though, the laptop i tested it on is ten years old. Anyhow i might be able to get my hands on a later model laptop from 2015/16, a lenovo x250 - i5, has a tiny screen though at 13.3 inches, im used to 15 inches on my toshiba sat.
Might be time to say goodbye to the toshiba, but i live in hope of making this thing work for 15 years, hopefully devuan can get me there
Edit: i have an even older dell laptop from around 2008 that is now happily buzzing away streaming some youtube at low res using slitaz linux, pretty sure it will last another 2 - 3 years with a battery upgrade.
dice wrote:What would you recommend doing?
The kernel probably did log some information, but they never made it on time to the disk. If your laptop has got a serial port, set the kernel to use it as console (add console=ttyS[X] as boot option); you will see the messages there from another machine as it happens. If not, you can use an Ethernet port and try netconsole.
Good idea!
iwd doesn't have a dbus dependency and works just fine without it, dbus activation is only needed if iwd is being used as a backend for NetworkManager or connman.
@OP: sorry for the diversion, I'll stop now.
so why would dylanaraps go to all the trouble of building iwd without dbus?
iwd without dbus
----------------This is a complete rewrite of the original eiwd with
the new focus being to modify as little as possible
from upstream.All that has changed in the iwd code is the insertion
of ifdefs to block away dbus code when desired.
https://github.com/dylanaraps/eiwd
Why are you sorry, the OP has probably gone back to windows or ubuntu, mint.
Yeah, kernel regressions are unfortunately common in Linux. The developers are too busy cramming in new features so old hardware support can suffer. You should probably file a bug report with the kernel developers because they can't fix it if they don't know about it and you won't be able to keep using old kernels indefinitely.
True but id like to know how to debug it first. Ive tried seeing if i can catch dmesg output for when it freezes with dmeshg-wH but when it freezes nothing is caught in in dmesg or any error logs. What would you recommend doing?