You are not logged in.
dice wrote:Ill probably switch to iwd when/if it is ready for devuan
The iwd maintainer wouldn't add the init scripts to the package without a proper diff but they did modify it so that non-systemd dbus activation should work. This means that the version in testing/unstable should work as a backend for NetworkManager or connman but an init script would still have to be added for standalone usage.
See https://bugs.debian.org/cgi-bin/bugrepo … bug=966518 for the details.
I wonder if this eiwd is worth looking into for a no dbus dependancy, still would need an init script created for it though. Might give it a try myself. Although it looks like dylanaraps has left this project to gather some dust for one reason or another.
dice wrote:just needed to delete those foreign repositories. Replace the buster backports entries with devuans backports and update, upgrade should have fixed it
I don't think that would have removed any foreign packages that were already installed.
ah yes i left out the part about uninstalling the foreign packages first.
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.
I just find this strange behaviour, it seems the netinstall iso install just disrgarded the compose key and ctrl_alt_backspace setting that i put in dpkg-reconfigure keyboard-configuration but the refractainstall took it?
Refractainstaller runs dpkg-reconfigure in the running live system, and then the changes get copied along with the rest of the system. I'm not sure how devuan/debian installer does it. I think it just stores the values and edits the target file, but it's also possible it does it in a chroot. Either way, I don't know why the two installers would give different results.
The correct result imo is refractainstaller. It might be user error on my part but ive done a few installations of devuan and pick the same configurations each time in regards to locale, keyboard setup etc. Not a big deal, just quirks of the software i suppose.
I dont understand this but it seems maybe dwm can handle the modkeys using its own programming. I have another machine with the exact same setup not installed using refractainstaller but the beowulf netinstall iso and the /etc/default/keyboard looks like below with XKBOPTIONS= blank and the modkeys work.
I just find this strange behaviour, it seems the netinstall iso install just disrgarded the compose key and ctrl_alt_backspace setting that i put in dpkg-reconfigure keyboard-configuration but the refractainstall took it?
# KEYBOARD CONFIGURATION FILE
# Consult the keyboard(5) manual page.
XKBMODEL="pc105"
XKBLAYOUT="us"
XKBVARIANT=""
XKBOPTIONS=""
BACKSPACE="guess"
I prefer iwd over wpa_supplicant because it is lighter, more secure, has fewer dependencies and it can be used as a complete wireless networking solution by itself (it has built-in dhcp functionality). The only drawbacks are that the Devuan package lacks a sysvinit script and the version in beowulf is pre-release.
Ill probably switch to iwd when/if it is ready for devuan. Ive used it in bleeding edge arch and it works quite well, easy to configure using iwctl.
Not really that much of a frankenstein, just needed to delete those foreign repositories. Replace the buster backports entries with devuans backports and update, upgrade should have fixed it.
Pootler if you want devuan backports just add them like this from the terminal.
echo "deb http://deb.devuan.org/merged beowulf-backports main" | sudo tee -a /etc/apt/sources.list.d/devuan-backports.list
then
sudo apt update && sudo apt dist-upgrade
Hi pootler what did you install desktop wise, xfce4?
This issue possibly because you dont have libelogind0 installed?
do
sudo apt install libelogind0
and then yes to remove libsystemd0
then try to install network manager again.
I believe this is the issue, i could be wrong...
edit: I was successfully able to install network manager on devuan beowulf just now.
solved it, not sure why it changed.
In file /etc/default/keyboard i changed the line XKBOPTIONS="compose:lwin,terminate:ctrl_alt_bksp"
to XKBOPTIONS="compose:menu,terminate:ctrl_alt_bksp"
then sudo udevadm trigger --subsystem-match=input --action=change
now have both modkeys for dwm working, for now atleast.
until wicd is inserted into testing which it wont this release cycle i would be more inclined to use either network manager or connman for ease of use for newbies. Network Manager maybe bloat but it works.
In that case getting Network Manager working is probably a better idea, its usually just click and connect, disconnect.
If you have the file /etc/network/interfaces make sure to comment out any networks in relation to your wifi or ethernet as i believe Network Manager handles this in its own way.
Ive used NetworkManager in the past and it does the job.
Try installing it like this.
sudo apt install network-manager network-manager-gnome
reboot
Probably show my age here, Phoebe Cates, song is called Paradise
I gave slitaz a try today, i just love how they have created such a tiny distro that can do so much for old hardware. I managed to install it to a partition on an old laptop i had collecting dust and it works perfectly, even picked up the ancient wifi dongle i used with way back.
I dont use wifi managers like wicd or network manager so I will share my reliable method. Its all done from the terminal, this has no bells and whistles, icons etc, its all backend work. I keep an eye on my connection through a basic shell script through a status panel.
basic wifi wpa_supplicant setup.
as root user do the following.
wpa_passphrase ESSID PASSPHRASE > /etc/wpa_supplicant/wpa_supplicant.conf
edit /etc/network/interfaces to look something like below.
auto lo
iface lo inet loopback
auto wlan0
iface wlan0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
allow-hotplug usb0
iface usb0 inet dhcp
you can control wifi by using sudo ifup wlan0 to bring wifi up and sudo ifdown wlan0 to bring it down.
In any case having auto wlan0 in /etc/network/interfaces will connect automatically on boot if you are using devuan beowulf.
You can have multiple wifi wpa_supplicant networks as well and connect to them manually with a bit of editing.
i recently did a snapshot and an install using refracta tools. Everything seems good so far except i can no longer get the windows/multikey to work.
The options ive chosen below are exactly the same options as chosen in the devuan beowulf 3 install media and the multi_key was working with those defaults.
Ive tried,
sudo dpkg-reconfigure keyboard-configuration
Model = Generic 105-key PC (intl.)
Layout = English (US)
Key to function as AltGr = The Default For The Keyboard Layout
Compose Key = Left Logo Key
Still no good, unless refractasnapshot or install replaced something i was using to make MOD2KEY which is the windows key work?
In my dwm config.h i have
#include <X11/XF86keysym.h>
#define MODKEY Mod1Mask
#define MOD2KEY Mod4Mask
only MOD1MASK works, MOD4MASK no longer works?
dice wrote:head on a stick made a typo.
I'm not seeing it. # signifies root in a terminal. He just used the symbol instead of the words.
not the symbol, it was "demsg" instead of dmesg.
Did you check if the firmware was loaded?
# demsg | grep firmware
head on a stick made a typo.
as root user,
dmesg | grep firmware
also what does /etc/network/interfaces file look like?
How do you connect to the internet?
Not really understand your question but it's another computer and I have another network card if needed.
Just want to understand why I can't made this thing work and I have installed firmware-realtek too
it could be a configuration issue?
how are you connecting to the internet?
@dice . . . the surveillance state has been here for centuries in different forms. It is well explained by Eben Moglen at re:publica 2012 in Berlin. Almost 10 years later, the hole has gotten even deeper.
Eben looks like Richard Stallmans younger brother. As ((they)) say, nothing in life is free, there is always a catch!
dice wrote:i still need to figure out how to treat file extensions in and out hence trying to use ${@%.*}" which will probably work in my shell as i think sh is linked to bash in devuan?
No, /bin/sh is linked to dash in Devuan. If you want to use bashisms then don't use a /bin/sh shebang. Fortunately though the ${parameter%word} expansion is POSIX compliant — see section 2.6.2 of the official specification.
dice wrote:This uses secure-delete
Note that secure-delete is not guaranteed to completely delete files stored on a solid state device thanks to wear-levelling and over-provisioning. TRIM can help with the former (eventually) but not the latter.
ok thanks.
I was reading the faq at cryptsetup gitlab today and mentioned something similar to ssd drives.
https://gitlab.com/cryptsetup/cryptsetu … dQuestions
Also note that SSDs and also some HDDs (SMR and hybrid HDDs, for
example) may not actually overwrite the header and only do that an
unspecified and possibly very long time later. The only way to be sure
there is physical destruction. If the situation permits, do both
overwrite and physical destruction.
If you have time, overwrite the whole drive with a single pass of random
data. This is enough for most HDDs. For SSDs or FLASH (USB sticks) or
SMR or hybrid drives, you may want to overwrite the whole drive several
times to be sure data is not retained. This is possibly still insecure
as the respective technologies are not fully understood in this regard.
Still, due to the anti-forensic properties of the LUKS key-slots, a
single overwrite could be enough. If in doubt, use physical destruction
in addition. Here is a link to some current research results on erasing
SSDs and FLASH drives: https://www.usenix.org/events/fast11/te … rs/Wei.pdf
so here is the final script i have been working on. Usage inside the script.
This uses secure-delete so might be a bit slow for large files, could always replace it with rm -rf though.
#!/bin/sh
encrypt_file () {
openssl enc -aes-256-cbc -salt -pbkdf2 -iter 20000 -in "$2" -out "$2".aes -pass file:"$3"
srm -v "$2"
}
decrypt_file () {
openssl enc -d -aes-256-cbc -salt -pbkdf2 -iter 20000 -in "$2" -out "${2%.*}" -pass file:"$3"
}
encrypt_dirs () {
tar -cvzf "$2".tar.gz "$2" | openssl enc -aes256 -salt -pbkdf2 -iter 20000 -in "$2".tar.gz -out "$2".tar.gz.aes -pass file:"$3"
srm -v "$2".tar.gz
}
decrypt_dirs () {
openssl enc -d -aes256 -salt -pbkdf2 -iter 20000 -in "$2" -out "${2%.*}" -pass file:"$3"
tar xvf "${2%.*}"
srm -rv "${2%.*}"
}
usage () {
cat <<EOM
Usage:
[-e]
enc.sh -e file passfile
encrypts file with chosen passfile and removes with secure delete the file leaving only the encrypted file.aes
[-d]
enc.sh -d file passfile
decrypts file.aes with chosen passfile
[-E]
enc.sh -E directory passfile
encrypts a directory to directory.tar.gz.aes with a chosen passfile and removes with secure delete the unencrypted directory.tar.gz leaving the directory.tar.gz.aes
[-D]
enc.sh -D directory passfile
decrypts directory to directory.tar.gz with chosen passfile and extracts directory.tar.gz in place then removes with secure delete the unencrypted directory.tar.gz leaving the encrypted directory.tar.gz.aes
EOM
exit 0
}
while getopts ":edEDh" opt; do
case ${opt} in
e ) encrypt_file "$@"
;;
d ) decrypt_file "$@"
;;
E ) encrypt_dirs "$@"
;;
D ) decrypt_dirs "$@"
;;
h ) usage
;;
*)
;;
esac
done
i dont want to put in bashrc as these commands will be part of a larger script that also encrypts directories.
I was confused on the positional parameters for what i wanted to achieve.
Below is close to what i want but i still need to figure out how to treat file extensions in and out hence trying to use ${@%.*}" which will probably work in my shell as i think sh is linked to bash in devuan?
#!/bin/sh
encrypt_file () {
openssl enc -aes-256-cbc -salt -pbkdf2 -iter 20000 -in "$2" -out "$2".aes -k "$3"
}
decrypt_file () {
openssl enc -d -aes-256-cbc -salt -pbkdf2 -iter 20000 -in "$2" -out "${2%.*}" -k "$3"
}
while getopts ":ed" opt; do
case ${opt} in
e ) encrypt_file "$@"
;;
d ) decrypt_file "$@"
;;
*)
;;
esac
done
edit: i think i figured out the file extension problem i was having.
decrypt will accept as the -in argument with any file type extension eg; .txt .mp3 etc.., the -out argument with -out "${2%.*}" will bring back the file to its original thus deleting the .aes extension given to it when it was encrypted.
@ Head on a stick, my thinking initially for 2 separate scripts was to establish how to get each one to function independantly of one another and then bring them both into one script?
If I recall correctly, openssl has a relatively small upper limit of file size it can encrypt. I think it was like 1MB in my very unscientific testing.
The main way people encrypt files in a Linux and filesystem context is with GPG: https://www.howtogeek.com/427982/how-to … -on-linux/
Thanks but i just encrypted a 70mb file with openssl no problem?
Im familiar with gpg. What i am trying to accomplish with openssl is to be able to use random keyfiles for different files and directories just for experimentation.