[DNG] removal of angband.pl nosystemd-* repos
Hi! Some of you still use my nosystemd repos (753 unique IP accesses within last two weeks). They haven't been updated in a long while, and I believe that by now they do more harm than good: outdated packages suffer from either uninstability, unfixed bugs, or even security issues. Thus, I've dropped the nosystemd-buster repo; -stretch/-jessie are left for the time being but please migrate away. If you want a Debian derivative that doesn't suffer from systemd infestation, I think readers of this list might not have problems finding one... On my personal machines, I'm experimenting with elogind on unmodified Debian -- but alas, didn't have the tuits to include it in the official Debian archive yet. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ What Would Jesus Do, MUD/MMORPG edition: ⣾⠁⢰⠒⠀⣿⡁ • multiplay with an admin char to benefit your mortal [Mt3:16-17] ⢿⡄⠘⠷⠚⠋⠀ • abuse item cloning bugs [Mt14:17-20, Mt15:34-37] ⠈⠳⣄ • use glitches to walk on water [Mt14:25-26] signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] How to test the backend of simple-netaid
Hi,
El 08/09/18 a las 11:47, aitor_czr escribió:
Hi again,
El 07/09/18 a las 19:50, aitor_czr escribió:
Hi,
El 07/09/18 a las 19:37, aitor_czr escribió:
This is the simple script used for the wireless connection attempts:
ifdown
ip link set up
pkill wpa_supplicant
wpa_passphrase >
wpa_supplicant -B -c -i
rm -f /run/network/ifstate.
ip link set up
sleep 1
ifup
Maybe, the lines nº 6 and nº7 are superfluous. The line nº8 (that
is, "sleep 1") is important, believe it.
As sysadmins, what do you think about the use of "pkill wpa_supplicant"?
 Aitor.
This script needs granted permissions; so, it's included in a suid
binary. Once i talked about a security key for this binary.
The security key would be generated during the compilation of the
application in a way that only those binaries built *together* with
the suid binary will know it.
First of all, i have to deal with the add_custom_command() function
of CMake, in order to control the preference of the targets.
The first step should be to generate this key, before all the
executables.
Cheers,
 Aitor.
The idea is very simple. The GUI and the suid binary will contain a
non-existent header:
#include "key.h"
The key.h file will contain an unique line (the random definition of
the KEY varible) edited by CMake during the compilation. For example:
var1="#define KEY "
var2=`tr -cd '[:alnum:]' < /dev/urandom | fold -w32 | head -n1`
echo "${var1}\"${var2}\"" > key.h
would generate something like this:
#define KEY "X1AULvFge6Tgq1p9BZat4EEVqAwaCnsB"
and then, the suid binary only will be able to be run from the GUI,
built together with it.
Cheers,
 Aitor.
I had an issue packaging simple-netaid. The target of the shared library
"libnetaid.so" was being obj-x86-64-linux-gnu, and trying to use the
variable $(DEB_HOST_MULTIARCH)
in "libnetaid.install", this variable was not replaced by its value:
`x86-64-linux-gnu`. I've just found the following solution for that
doing the "libnetaid.install" executable:
#! /usr/bin/dh-exec
obj-*-linux-gnu/backend_src/libnetaid.so usr/lib/${DEB_HOST_MULTIARCH}
Cheers,
Aitor.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ..torbrowser-launcher 0.2.9-4~bpo9+1 still fails with torbrowser 8.0, is fix coming?
On Mon, 10 Sep 2018 06:36:40 +0200, Arnt wrote in message <20180910063640.34f10234@d44>: > On Fri, 7 Sep 2018 08:14:15 +0200, Arnt wrote in message > <20180907081415.07ea500f@d44>: > > > Hi, > > > > ..torbrowser-launcher fails with torbrowser 8.0, fix is coming: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908068 > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908068#10 > > > > ..meanwhile, delay your torbrowser upgrade to 8.0 until bugfix > > (8.0.1?) is out, or, find another way to start it. > > > > ..we now need to fork torbrowser and torbrowser-launcher? > torbrowser-launcher_0.2.9-4~bpo9+1 now launches torbrowser, > _but_, before you copy my naïve mistake, FIRST try: > ~/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/start-tor-browser > --verbose > > ..if that works the way it should, _stay_ on that working version > until we know WTF up with torbrowser-launcher and torbrowser. ..diagnosed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908463 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908463#15 ..0.2.9-5/fix discussion: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908463#37 -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
