The officially official Devuan Forum!

You are not logged in.

#1 Re: Installation » sans-dbus, Questions, Tips and Tricks on its Implementation » Today 05:28:56

chillfan wrote:

There's a little confusion about my name, I go by dev1fanboy only on the wiki but it remains under that name so that users can still find what they are looking for. A little bit of changing in links were required due to naming the pages after releases, because it's clearer what releases they can be used for. On the other hand, because it's frustrating for users the wiki pages should mirror the git repo soon. So I'll have a contributors area and a more readable area for users.

If you could point out which links are breaking that would be helpful. I'll of course fix those, or redirect to the renamed pages.

Just looked up, This old page still holds! See:

Uninstalling dbus and *kits (to Unfacilitate Remote Seats)
https://forums.gentoo.org/viewtopic-t-9 … ml#7837424
(of course, just search for string 'dev1fanboy')

However, let me see...  In this very topic, from the start:

https://git.devuan.org/dev1fanboy/Upgra … tall-guide

and you get:

Empty page
You are not allowed to create wiki pages

and likely more on this very topic, just search for  'git.devuan.org/dev1fanboy' this time.

It's two or three, look it up that way, which is without intermediaries...

About the D-Bus pages, ascii has surf2 so when ascii is released I may just use that instead of Firefox.

I'll likely keep with Pale Moon, I'm happy with it, and dbus isn't mandatory for it. I used to compile it in Gentoo as well. No issues. (Well... issues yes, but not those, and for other reasons... Good browser.).

#2 Re: Installation » sans-dbus, Questions, Tips and Tricks on its Implementation » Yesterday 22:18:37

It's not clear to me, maybe because you haven't made it clear, but are dev1fanboy and chillfan  the same one Dev1galaxy member?
If I don't start with the assumption that they are the same one, I can't understand the reply... So probably yes...
Hmmmh, sorry, poor quoting, more is unclear... Read on....

chillfan wrote:
miroR wrote:

...I posted that I would contact dev1fanboy ...
dev1fanboy, pls. either revert to the old locations that you previously had, or at least do not change those addresses any more...
( I'm referring to your Devuan Install, and esp. sans-dbus wiki pages. )

And also, consider my new posts, as well as:
sans-dbus in Devuan: low level core installation of dbus remain
https://dev1galaxy.org/viewtopic.php?id=1825

Correct me if I'm wrong, or confirm my research if you find it correct!

There's a fair bit of reading for the topic(s) but if I understand, there is something wrong with the Ceres APT pinning?

I don't think so... I think the man apt_preferences is the same for even Jessie, by now.

chillfan wrote:

I believe in Ceres you won't be able to avoid systemd that way if you use either dbus or xorg, and will have to make do with libsystemd0 being installed (also for ascii in some areas).

# apt-cache policy libsystemd0
libsystemd0:
  Installed: 236-3
  Candidate: 236-3
  Version table:
 *** 236-3 500
        500 tor+https://pkgmaster.devuan.org/merged ceres/main amd64 Packages
        500 tor+https://packages.devuan.org/merged ceres/main amd64 Packages
        100 /var/lib/dpkg/status
     236-3~bpo9+1 100
        100 tor+https://pkgmaster.devuan.org/merged ascii-backports/main amd64 Packages
        100 tor+https://pkgmaster.devuan.org/merged testing-backports/main amd64 Packages
     232-25+deb9u1 500
        500 tor+https://pkgmaster.devuan.org/merged ascii/main amd64 Packages
        500 tor+https://pkgmaster.devuan.org/merged testing/main amd64 Packages

You're right about that, apparently.

And this is only clear after repasting my own old quote:

chillfan wrote:
miroR wrote:

dev1fanboy, pls. either revert to the old locations that you previously had, or at least do not change those addresses any more...
( I'm referring to your Devuan Install, and esp. sans-dbus wiki pages. )

I am actually considering removing that document, since it's not that useful anymore for that reason.. unless anyone finds it still useful somehow?

I wrote it as kindly and I could, and I believe you're wrong by breaking links to your documents. It's even a little bit worse than just inconsiderate, but it'll be as you will decide, I can't try to exert any nicer lobbying for the non-breaking of your own pages than this... For the love of God or Free Software, whichever you like better, I linked to those pages of your even from Gentoo Forums... Why, on Earth, do would you rename pages and bring to dead links quite a few pages from also DNG Devuan Mailing List, which is also brought and accessible elsewhere as well (www.mailarchive.com IIRC or similar network name)... It's plain wrong...

Bringing a system to go without D-Bus (or dbus) is obvious good. Gentoo can do without it... And, yes, I now remember, it's not a matter of Jessie, Ascii or Ceres, Devuan/Debian as is available for us now, can't go without the low level core dbus API, the libdbus...

How do I know? Because I demonstrated it.
Back in the new, of just yester day:
sans-dbus in Devuan: low level core install of dbus remains
https://dev1galaxy.org/viewtopic.php?id=1825#p7173
or the very first post, where you can find that the same libdbus-1.so.3.14.11, pasting over what I have in the dd'ed image of 2007-08-27:

# ls -l /mnt/H0827-r/lib/x86_64-linux-gnu/libdbus-1.so.3*

lrwxrwxrwx 1 root root     20 2017-06-12 21:54 /mnt/H0827-r/lib/x86_64-linux-gnu/libdbus-1.so.3 -> libdbus-1.so.3.14.11
-rw-r--r-- 1 root root 321288 2017-06-12 21:54 /mnt/H0827-r/lib/x86_64-linux-gnu/libdbus-1.so.3.14.11

( H stands for year 2017 (my shortcut (for all of 2009-2018 and on) starting with 2009, which is just 9, 2010 ->A ... 2017 ->H sorry to have forgot to redact it to make the dates clear)

Back then it was Jessie, which I hadn't converted to sans-dbus. But in later dates of the post. it was Ascii, and now Ascii/Ceres (not clear Ceres: The libdbus is a constant, the procedure that we thought rids us of dbus, doesn't do it...

(But pls. that's not a reason to delete the post and break whatever links to it! Good practice in such situation is explanation, not obscuration...)

So, the below, IMO (and with the above facts) does not hold:

chillfan wrote:

As far as full D-Bus removal it's very difficult if you need a fully featured browser from the Devuan repos. Firefox was mentioned mostly because you don't need to have the dbus daemon installed and running, so maybe your suggestion is not to be concerned about features and go with no dbus at all?

You had written about browsers that can go without dbus in your posts on that wiki, I hope you hadn't deleted those posts as well... My Pale Moon I can compile without dbus... Browser should not be an issue...

Pls. remember, and it's in that link to the new realization topic of mine linked above, I ran Gentoo truly and effectively, and ran it with all that I needed in computing (I learned, and it's in the link that bobjohnson gave in:
sans-dbus, Questions, Tips and Tricks on its Implementation
https://dev1galaxy.org/viewtopic.php?id=761#p6866
...this link:
https://github.com/apple/cups/issues/5143
more and more programs offer to run and install without dbus. Cups being one... So it's not a lost cause, I'd argue...

jsmeix wrote:

As expected building CUPS without DBUS support
(via configure --disable-dbus) avoids the issue.

Nice news, if I don't miss something there...

chillfan wrote:

The changes to the wiki do seem to be confusing people, what I'll point to.. is that contributors can't easily view the source of those pages with the older location. Just as a note you can update older posts on d1g, but I may have to revert things anyway if enough people are finding it confusing. Does anyone agree with that? It would be good to have some feedback about that.

Pls. do! And thanks in advance if you do... I learned a lot from those pages... And that was an argument that I presented to others as well, and many have taken it into consideration... (But if you want to see the hits you had, I can't help, other than saying, some of the hits you owe to my linking to it...)

Unfortunately, our cause is not over, D-Bus is still there, low-level, core... Let's do what we can to get that freedom to users like some other distros as well offter
(
which I don't know of, other than Gentoo, I'm not so familiar with distros other than Debain, Devuan and Gentoo; and also I aware that I only had incomplete distro when I removed dbus in Debian, in 2015 or 2016 using... Aaargh, where's that one, I need to post that link too...
MirDebian “WTF” Repository
https://www.mirbsd.org/~tg/Debs/debidx.htm
[[[ Yeah, that's the tutorial and the package repo that I used back than, but I didn't have audio and my TV-cards didn't have it... and I got that page from:
Will there be a MirDevuan
https://lists.dyne.org/lurker/message/2 … 6a.en.html
which luckily, I had linked to the thread of above in my reply to bobjohnson...

Maybe that's the way to go --in that thread there's also links to a mail or two, no, there's more the thread linked above, which the above email belongs to --and pls. consider that links just should not be broken, see how potentially useful it is that I can give these links here?--
And in that thread there's also not just links, but also a mail from the initiator of sans-dbus, Thorsten Glaser:
Will there be a MirDevuan
https://lists.dyne.org/lurker/message/2 … 9e.en.html

Yeah, maybe that's the way to go, or at least learn from...
).

Regards!

#3 Re: Installation » sans-dbus, Questions, Tips and Tricks on its Implementation » Yesterday 04:11:07

golinux wrote:
miroR wrote:

... related to sans-dbus.  ...

Hi miroR . . . I sent a short email to  dev1fanboy asking him to have a look at your post..

Thx! smile

#4 Re: Installation » sans-dbus, Questions, Tips and Tricks on its Implementation » 2018-01-17 22:31:36

And I don't even remember where I posted that I would contact dev1fanboy about something related to sans-dbus. I can tell that I tried (and contacted wrong Devuaner instead -- Ralph Ronquest I PM'ed, having mixed the nicknames somehow... But dev1fanboy's old email expired, which I had from Devuan DNG ML. So I have to post it here:

dev1fanboy, pls. either revert to the old locations that you previously had, or at least do not change those addresses any more...
( I'm referring to your Devuan Install, and esp. sans-dbus wiki pages. )

And also, cosider my new posts, as well as:
sans-dbus in Devuan: low level core installation of dbus remain
https://dev1galaxy.org/viewtopic.php?id=1825

Correct me if I'm wrong, or confirm my research if you find it correct!

#5 Re: Installation » sans-dbus, Questions, Tips and Tricks on its Implementation » 2018-01-17 22:09:47

First, as fsmithred wrote, just a bit further above, in the  post:
https://dev1galaxy.org/viewtopic.php?pid=6865#p6865
nothing is needed for not installing systemd.

Second, I'm on a combo ascii/ceres, so far from jessie, but maybe half way ahead of ascii... The Ceres being not yet completely formed Devuan out of Debian sources, IIUC (as  golinux pointed out to me somewhere in this forum...

And what I want to post about, this old method, these (abreviating it here, already removed systemd-related lines, and some other, but see the post further above https://dev1galaxy.org/viewtopic.php?pid=6831#p6831 for complete presentation of that old method):

miroR wrote:

... /etc/apt/preferences.d/avoid-systemd in dev1fanboy's wiki ... months ago now, picked it from there, to my best recollection:

# ls -ABRgo /etc/apt/preferences*
-rw-r--r-- 1  262 2017-12-01 14:30 /etc/apt/preferences

/etc/apt/preferences.d:
total 4
-rw-r--r-- 1 62 2015-04-20 22:25 avoid-systemd

So:

# cat /etc/apt/preferences
Package: *dbus*
Pin: origin ""
Pin-Priority: -1

...

Package: *pulse*
Pin: origin ""
Pin-Priority: -1

...

#

...

(Nor pulseaudio either. And my audio is functioning well, in PaleMoon, FFmpeg, MPlayer, Mencoder, Mpv, Vlc...)

Regards!

That old method doesn't work anymore... It worked in Jessie way back in the days we, on Debian forum thought about the ways to pin-away in /etc/apt/preferences systemd so it not be installed... And it (EDIT just minutes after posting) didn't work in Jessie a few months ago, at the time I posted all the old posts in this topic... The remove/purge'ing and the /etc/apt/apt.conf.d/01lean did remove, if we consider the dbus only, all the high-level dbus, and kept it removed, not the pinning... (END OF EDIT)

But does not work now anymore...

Here's why:

# man apt_preferences | col -b  > [this text that I'm preparing]

APT_PREFERENCES(5)                                  APT                                  APT_PREFERENCES(5)

NAME
       apt_preferences - Preference control file for APT

DESCRIPTION
       The APT preferences file /etc/apt/preferences and the fragment files in the /etc/apt/preferences.d/
       folder can be used to control which versions of packages will be selected for installation.

       Several versions of a package may be available for installation when the sources.list(5) file
       contains references to more than one distribution (for example, stable and testing). APT assigns a
       priority to each version that is available. Subject to dependency constraints, apt-get selects the
       version with the highest priority for installation. The APT preferences override the priorities that
       APT assigns to package versions by default, thus giving the user control over which one is selected
       for installation.

       Several instances of the same version of a package may be available when the sources.list(5) file
       contains references to more than one source. In this case apt-get downloads the instance listed
       earliest in the sources.list(5) file. The APT preferences do not affect the choice of instance, only
       the choice of version.

... [ 424 lines cut here ] ...

APT 1.6~alpha6                                 15 August 2015                            APT_PREFERENCES(5)

And the important part is:

The APT preferences do not affect the choice of instance, only
       the choice of version.

IOW, you can't set your /etc/apt/preferences in such way as to disable/preclude/call-it-otherwise that some package be installed.

Pls. somebody correct me if I'm wrong!

#6 Re: Installation » sans-dbus in Devuan: low level core install of dbus remains » 2018-01-17 20:48:03

Just to be in the clear of how deep that libdbus-1-3 is, by means of dependencies, rooted in Devuan:
# apt-get remove libdbus-1-3

Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
  adwaita-icon-theme coinor-libcbc3 coinor-libcgl1 coinor-libclp1
  coinor-libcoinmp1v5 coinor-libcoinutils3v5 coinor-libosi1v5 fonts-opensymbol
  gconf2-common gir1.2-atk-1.0 gir1.2-freedesktop gir1.2-gdkpixbuf-2.0
  gir1.2-glib-2.0 gir1.2-harfbuzz-0.0 gir1.2-pango-1.0 gnome-icon-theme
  gtk-update-icon-cache hexchat-common icu-devtools liba52-0.7.4 libaa1
  libasyncns0 libatk1.0-0 libatk1.0-data libatk1.0-dev libaudio2 libavc1394-0
  libbasicusageenvironment1 libboost-date-time1.62.0 libboost-iostreams1.62.0
  libcaca0 libcairo-gobject2 libcairo-perl libcairo-script-interpreter2
  libcairo2-dev libcanberra0 libcddb2 libcdio-cdda2 libcdio-paranoia2
  libcdio17 libcdr-0.1-1 libclucene-contribs1v5 libclucene-core1v5
  libcmis-0.5-5v5 libcolamd2 libdc1394-22 libdca0 libdconf1
  libdouble-conversion1 libdv4 libdvbpsi10 libdvdnav4 libdvdread4 libenca0
  libeot0 libepoxy0 libetonyek-0.1-1 libexpat1-dev libexttextcat-2.0-0
  libexttextcat-data libfaad2 libfontconfig1-dev libfreehand-0.1-1
  libfreetype6-dev libgdk-pixbuf2.0-dev libgirepository-1.0-1 libglib-perl
  libglib2.0-bin libglib2.0-dev libglib2.0-dev-bin libgltf-0.1-1 libgpgmepp6
  libgraphite2-dev libgroupsock8 libgs9-common libgtk2.0-common
  libharfbuzz-dev libharfbuzz-gobject0 libharfbuzz-icu0 libhunspell-1.6-0
  libhyphen0 libicu-dev libiec61883-0 libijs-0.35 libiso9660-10
  libjack-jackd2-0 libjansson4 libjbig2dec0 libkate1 liblangtag-common
  liblangtag1 libldb1 liblirc-client0 liblivemedia61 liblzo2-2 libmad0
  libmhash2 libmpcdec6 libmpeg2-4 libmspub-0.1-1 libmtp-common libmtp9
  libmwaw-0.3-3 libmythes-1.2-0 libneon27-gnutls libnl-route-3-200 libnotify4
  libodfgen-0.1-1 libopenal-data libopenal1 libopenmpt-modplug1
  liborcus-0.12-0 libpagemaker-0.0-0 libpango-perl libpango1.0-dev libpcre16-3
  libpcre2-16-0 libpcre3-dev libpcre32-3 libpcrecpp0v5 libpixman-1-dev
  libpng-dev libproxy1v5 libpython2.7 libpython3.6 libqt5core5a libraptor2-0
  librasqal3 libraw1394-11 librdf0 libreoffice-common libreoffice-style-galaxy
  libreoffice-style-tango libresid-builder0c2a librevenge-0.0-0 libshout3
  libsidplay2 libsndio6.1 libspeexdsp1 libstaroffice-0.0-0 libstdc++-6-dev
  libsuitesparseconfig4 libtag1v5 libtag1v5-vanilla libtalloc2 libtdb1
  libtevent0 libuchardet0 libupnp6 libusageenvironment3 libva-wayland2
  libvcdinfo0 libvisio-0.1-1 libvorbisidec1 libwayland-cursor0
  libwayland-egl1-mesa libwbclient0 libwpd-0.10-10 libwpg-0.3-3 libwps-0.4-4
  libxatracker2 libxcb-icccm4 libxcb-image0 libxcb-keysyms1 libxcb-randr0
  libxcb-render-util0 libxcb-render0-dev libxcb-shm0-dev libxcb-xinerama0
  libxcb-xkb1 libxcb-xv0 libxcomposite-dev libxcursor-dev libxdamage-dev
  libxext-dev libxfixes-dev libxfont2 libxft-dev libxi-dev libxinerama-dev
  libxkbcommon-x11-0 libxkbcommon0 libxml2-utils libxmlsec1 libxmlsec1-nss
  libxrandr-dev libxrender-dev libxvmc1 libyajl2 libzmf-0.0-0 lp-solve
  python-talloc sound-theme-freedesktop uno-libs3 ure vlc-data vlc-l10n
  x11proto-composite-dev x11proto-damage-dev x11proto-fixes-dev
  x11proto-randr-dev x11proto-render-dev x11proto-xext-dev
  x11proto-xinerama-dev xdg-utils zlib1g-dev
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  libwireshark-data libwireshark10 libwiretap7 libwscodecs1 libwsutil8 tshark
  vlc-data wireshark-common
Suggested packages:
  snmp-mibs-downloader wireshark-doc
Recommended packages:
  geoip-database geoip-database-extra
The following packages will be REMOVED:
  ffmpeg gconf-service ghostscript gir1.2-gtk-2.0 hexchat libasound2-plugins
  libavahi-client3 libavdevice57 libcups2 libcupsimage2 libdbus-1-3
  libdbus-glib-1-2 libgconf-2-4 libglade2-0 libgs9 libgtk2-perl libgtk2.0-0
  libgtk2.0-bin libgtk2.0-dev libpulse0 libqgsttools-p1 libqt5dbus5 libqt5gui5
  libqt5multimedia5 libqt5multimedia5-plugins libqt5multimediawidgets5
  libqt5network5 libqt5opengl5 libqt5printsupport5 libqt5svg5 libqt5widgets5
  libqt5x11extras5 libreoffice-base libreoffice-base-core
  libreoffice-base-drivers libreoffice-calc libreoffice-core libreoffice-draw
  libreoffice-impress libreoffice-report-builder-bin libsdl-image1.2
  libsdl1.2debian libsdl2-2.0-0 libsmbclient libvlc-bin libvlc5 libvlccore8
  mencoder mplayer mpv ntfs-config palemoon python-glade2 python-gtk2
  python3-uno samba-libs vlc vlc-bin vlc-plugin-base vlc-plugin-qt
  vlc-plugin-video-output wireshark wireshark-qt xserver-xorg
  xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
  xserver-xorg-input-evdev-dbg xserver-xorg-input-libinput
  xserver-xorg-input-mouse xserver-xorg-input-synaptics
  xserver-xorg-input-wacom xserver-xorg-video-all xserver-xorg-video-amdgpu
  xserver-xorg-video-ati xserver-xorg-video-cirrus xserver-xorg-video-fbdev
  xserver-xorg-video-intel xserver-xorg-video-mach64 xserver-xorg-video-mga
  xserver-xorg-video-neomagic xserver-xorg-video-nouveau
  xserver-xorg-video-openchrome xserver-xorg-video-qxl xserver-xorg-video-r128
  xserver-xorg-video-radeon xserver-xorg-video-savage
  xserver-xorg-video-siliconmotion xserver-xorg-video-sisusb
  xserver-xorg-video-tdfx xserver-xorg-video-trident xserver-xorg-video-vesa
  xserver-xorg-video-vmware
The following packages will be upgraded:
  libwireshark-data libwireshark10 libwiretap7 libwscodecs1 libwsutil8 tshark
  vlc-data wireshark-common
8 upgraded, 0 newly installed, 93 to remove and 88 not upgraded.
Need to get 739 kB/16.2 MB of archives.
After this operation, 475 MB disk space will be freed.
Do you want to continue? [Y/n] Abort.

If ever there's a solution, and Devuan can really run dbus-free like Gentoo, I'm all ears!
And if I got something wrong, somebody pls. correct me!

#7 Installation » sans-dbus in Devuan: low level core install of dbus remains » 2018-01-17 20:24:51

miroR
Replies: 1

title: sans-dbus in Devuan: low level core installation of dbus remains

Try to find anything that really runs dbus in this old dd'ed image of my Gentoo system:

find /mnt/170428-r/ -name '*dbus*' | grep -v '\/usr\/portage\|\/usr\/src\/linux\|\/home\/miro'
( that's 2017-04-28, complete / system of my then Gentoo installation, that partition, when it was alive, comprised /usr /var and all, just not the /boot dir which was on a separate partition )

/mnt/H0428-r/etc/lvm/profile/lvmdbusd.profile
/mnt/H0428-r/etc/dbus-1
/mnt/H0428-r/usr/bin/qdbus
/mnt/H0428-r/usr/bin/qdbusviewer
/mnt/H0428-r/usr/bin/qdbuscpp2xml
/mnt/H0428-r/usr/bin/qdbusxml2cpp
/mnt/H0428-r/usr/bin/gdbus-codegen
/mnt/H0428-r/usr/bin/gdbus
/mnt/H0428-r/usr/lib64/qt5/mkspecs/features/dbuscommon.pri
/mnt/H0428-r/usr/lib64/qt5/mkspecs/features/dbusadaptors.prf
/mnt/H0428-r/usr/lib64/qt5/mkspecs/features/dbusinterfaces.prf
/mnt/H0428-r/usr/lib64/python-exec/python2.7/gdbus-codegen
/mnt/H0428-r/usr/lib64/python-exec/python3.4/gdbus-codegen
/mnt/H0428-r/usr/lib64/python2.7/site-packages/gdbus_codegen
/mnt/H0428-r/usr/lib64/python2.7/site-packages/gdbus_codegen/dbustypes.py
/mnt/H0428-r/usr/lib64/python2.7/site-packages/gdbus_codegen/dbustypes.pyc
/mnt/H0428-r/usr/lib64/python2.7/site-packages/gdbus_codegen/dbustypes.pyo
/mnt/H0428-r/usr/lib64/python2.7/site-packages/gdbus_codegen-2.50.3-py2.7.egg-info
/mnt/H0428-r/usr/lib64/python3.4/site-packages/gdbus_codegen
/mnt/H0428-r/usr/lib64/python3.4/site-packages/gdbus_codegen/dbustypes.py
/mnt/H0428-r/usr/lib64/python3.4/site-packages/gdbus_codegen/__pycache__/dbustypes.cpython-34.pyc
/mnt/H0428-r/usr/lib64/python3.4/site-packages/gdbus_codegen/__pycache__/dbustypes.cpython-34.pyo
/mnt/H0428-r/usr/lib64/python3.4/site-packages/gdbus_codegen-2.50.3-py3.4.egg-info
/mnt/H0428-r/usr/lib64/libreoffice/share/autotext/en-US/crdbus50.bau
/mnt/H0428-r/usr/include/qt5/QtPlatformSupport/5.7.1/QtPlatformSupport/private/qdbusmenuconnection_p.h
/mnt/H0428-r/usr/include/qt5/QtPlatformSupport/5.7.1/QtPlatformSupport/private/qdbusmenubar_p.h
/mnt/H0428-r/usr/include/qt5/QtPlatformSupport/5.7.1/QtPlatformSupport/private/qdbusmenuadaptor_p.h
/mnt/H0428-r/usr/include/qt5/QtPlatformSupport/5.7.1/QtPlatformSupport/private/qdbusmenuregistrarproxy_p.h
/mnt/H0428-r/usr/include/qt5/QtPlatformSupport/5.7.1/QtPlatformSupport/private/dbusconnection_p.h
/mnt/H0428-r/usr/include/qt5/QtPlatformSupport/5.7.1/QtPlatformSupport/private/qdbustraytypes_p.h
/mnt/H0428-r/usr/include/qt5/QtPlatformSupport/5.7.1/QtPlatformSupport/private/qdbustrayicon_p.h
/mnt/H0428-r/usr/include/qt5/QtPlatformSupport/5.7.1/QtPlatformSupport/private/qdbusmenutypes_p.h
/mnt/H0428-r/usr/include/qt5/QtPlatformSupport/5.7.1/QtPlatformSupport/private/qdbusplatformmenu_p.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/dbusactiongroup.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/dbusaddress.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/dbusinterface.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/dbusmenumodel.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/dbuswatchname.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/dbuserrorutils.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/dbusauthobserver.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/dbusmessage.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/dbusmethodinvocation.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/dbusinterfaceskeleton.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/private/dbusobject_p.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/private/dbuserrorutils_p.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/private/dbusinterface_p.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/private/dbusinterfacevtable_p.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/private/dbusmessage_p.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/private/dbusproxy_p.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/private/dbusserver_p.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/private/dbusinterfaceskeleton_p.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/private/dbusmenumodel_p.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/private/dbusmethodinvocation_p.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/private/dbusconnection_p.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/private/dbusaddress_p.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/private/dbusactiongroup_p.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/private/dbussubtreevtable_p.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/private/dbusutils_p.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/private/dbuswatchname_p.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/private/dbusintrospection_p.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/private/dbuserror_p.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/private/dbusauthobserver_p.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/private/dbusownname_p.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/dbusserver.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/dbusobject.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/dbusconnection.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/dbusproxy.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/dbusinterfacevtable.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/dbusutils.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/dbusintrospection.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/dbussubtreevtable.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/dbusownname.h
/mnt/H0428-r/usr/include/giomm-2.4/giomm/dbuserror.h
/mnt/H0428-r/usr/include/glib-2.0/gio/gdbusobjectskeleton.h
/mnt/H0428-r/usr/include/glib-2.0/gio/gdbusutils.h
/mnt/H0428-r/usr/include/glib-2.0/gio/gdbuserror.h
/mnt/H0428-r/usr/include/glib-2.0/gio/gdbusobject.h
/mnt/H0428-r/usr/include/glib-2.0/gio/gdbusnamewatching.h
/mnt/H0428-r/usr/include/glib-2.0/gio/gdbusauthobserver.h
/mnt/H0428-r/usr/include/glib-2.0/gio/gdbusactiongroup.h
/mnt/H0428-r/usr/include/glib-2.0/gio/gdbusmenumodel.h
/mnt/H0428-r/usr/include/glib-2.0/gio/gdbusmethodinvocation.h
/mnt/H0428-r/usr/include/glib-2.0/gio/gdbusobjectmanagerserver.h
/mnt/H0428-r/usr/include/glib-2.0/gio/gdbusconnection.h
/mnt/H0428-r/usr/include/glib-2.0/gio/gdbusintrospection.h
/mnt/H0428-r/usr/include/glib-2.0/gio/gdbusmessage.h
/mnt/H0428-r/usr/include/glib-2.0/gio/gdbusserver.h
/mnt/H0428-r/usr/include/glib-2.0/gio/gtestdbus.h
/mnt/H0428-r/usr/include/glib-2.0/gio/gdbusproxy.h
/mnt/H0428-r/usr/include/glib-2.0/gio/gdbusaddress.h
/mnt/H0428-r/usr/include/glib-2.0/gio/gdbusobjectmanager.h
/mnt/H0428-r/usr/include/glib-2.0/gio/gdbusinterfaceskeleton.h
/mnt/H0428-r/usr/include/glib-2.0/gio/gdbusnameowning.h
/mnt/H0428-r/usr/include/glib-2.0/gio/gdbusinterface.h
/mnt/H0428-r/usr/include/glib-2.0/gio/gdbusobjectmanagerclient.h
/mnt/H0428-r/usr/include/glib-2.0/gio/gdbusobjectproxy.h
/mnt/H0428-r/usr/local/src/wireshark-2.2.6/epan/dissectors/packet-dbus.c
/mnt/H0428-r/usr/share/bash-completion/completions/qdbus
/mnt/H0428-r/usr/share/bash-completion/completions/gdbus
/mnt/H0428-r/usr/share/man/man1/gdbus.1.bz2
/mnt/H0428-r/usr/share/man/man1/gdbus-codegen.1.bz2
/mnt/H0428-r/usr/share/nmap/scripts/modbus-discover.nse
/mnt/H0428-r/usr/share/openrc/support/init.d.examples/dbus
/mnt/H0428-r/usr/share/vim/vimfiles/syntax/dbusglib.vim
/mnt/H0428-r/usr/share/gtk-doc/html/gio/gdbus.html
/mnt/H0428-r/usr/share/gtk-doc/html/gio/gdbus-convenience.html
/mnt/H0428-r/usr/share/gtk-doc/html/gio/gdbus-lowlevel.html
/mnt/H0428-r/usr/share/gtk-doc/html/gio/gdbus-codegen.html
/mnt/H0428-r/usr/share/gtk-doc/html/gio/gdbus-example-gdbus-codegen.html
/mnt/H0428-r/usr/share/vala-0.34/vapi/dbus-glib-1.vapi
/mnt/H0428-r/usr/share/dbus-1
/mnt/H0428-r/usr/share/qt4/mkspecs/features/dbusadaptors.prf
/mnt/H0428-r/usr/share/qt4/mkspecs/features/dbusinterfaces.prf
/mnt/H0428-r/usr/share/qt4/mkspecs/features/qdbus.prf
/mnt/H0428-r/usr/share/doc/glibmm-2.50.1/examples/dbus
/mnt/H0428-r/var/db/pkg/dev-util/gdbus-codegen-2.50.3
/mnt/H0428-r/var/db/pkg/dev-util/gdbus-codegen-2.50.3/gdbus-codegen-2.50.3.ebuild

The '\/usr\/portage\|\/usr\/src\/linux\|\/home\/miro' is, escaped backslashes reverted: '/usr/portage\|/usr/src/linux\|/home/miro', and, explanation for the less advanced, the \| is just to get the grep to look for the strings separated by that escaped backslash \| (else it would search for /usr/portage|/usr/src/linux|/home/miro which of course doesn't exist.

More explanation for the less advanced, or simply unfamiliar with Gentoo. I didn't search /usr/portage and /usr/src/linux because in the former are all the ebuilds for all the packages available --not installed, but available-- in Gentoo, and the latter is the sources where I run my compilations of linux kernels, which neither contains anything that is installed in the system.

Gentoo had the USE flag that could be set, namely -dbus (the default of which was just dbus meaning: do install dbus and dbus-related packages) and once you set that flag, which, among other flags in my:
# cat /mnt/H0428-r/etc/portage/make.conf

...
# These are the USE flags that were used in addition to what is provided by the
# profile used for building.
USE="a52 alsa apache2 audit bash-completion berkdb bzip2 caps cdr crypt \
     cscope css -dbus dri dvb dvdr fam ffmpeg fontconfig gdbm \
     -geoip gif git -gnome gnutls gpm gstreamer gzip hardened \
     imagemagick -introspection jack jpeg jpeg2k -kde lame libcaca -libav \
         mad maildir mhash mng mplayer ncurses nls ogg opengl -pam pie png -policykit \
         readline sasl sdl -selinux -systemd sysvipc smp sound sox sqlite sqlite3 \
     ssl subversion svg tiff truetype -udev unicode v4l vim-syntax vorbis \
     X x264 xattr xine xv xvid zlib -pulseaudio"
...

which (it's in the second row of flags: -dbus), among other flags in my, looked like that (pls. do note the
-systemd and -pulseaudio flags as well, and, I guess irrelevant at this age -policykit and maybe so is -libav, the would-be obsoleter of ffmpeg, but we'd be going into digression here, won't happen, long stories, no time...)

Gentoo respected those... I was dbus-free truly, as well as systemd-free, with Gentoo.

To make the story more complete, because the next is within the topic, I had excluded \/home\/miro from the grep search, because there are finds in there. I excluded them because they're not installed files by Gentoo Package Management System. But I want to show you what was there:

# find /mnt/H0428-r/ -name '*dbus*' | grep '\/home\/miro' >> /Cmn/mr/Dev1_180117_sans-dbus_invalid.txt

...
/mnt/H0428-r/home/miro/h_H.bak.PREV/Downloads/Upgrade-Install-Devuan.wiki/Devuan-without-dbus.markdown
/mnt/H0428-r/home/miro/h_H.bak.PREV/Downloads/Upgrade-Install-Devuan.wiki/polish-devuan-without-dbus.md
/mnt/H0428-r/home/miro/h_H.bak.PREV/Downloads/Upgrade-Install-Devuan.wiki/dbus-free-software.md
/mnt/H0428-r/home/miro/h_H.bak.PREV/Downloads/Upgrade-Install-Devuan.wiki/polish-dbus-independent-software.md

See:
https://git.devuan.org/dev1fanboy/Upgra … ut-dbus.md
(or if the link gets renamed, search it from: https://git.devuan.org/dev1fanboy/Upgra … ll-Devuan/ )

That's just the dev1-fanboy's tutorial there, that I saved and studied, and applied only  a few months later. So I really was looking for that sans-dbus feature with some expectation.

First, this (primitive) research of mine was triggered when I noticed libdbus-1-3 asking to get installed:

# apt-get upgrade |& tee ~mr/LOG_/apt-get_upgrade_$(date +%y%m%d_%H%M%S)_5

Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages have been kept back:
  apache2 apache2-bin apache2-data apache2-utils bind9-host dnsutils
  libbind9-160 libcolamd2 libdns169 libisc166 libisccc160 libisccfg160
  liblwres160 libparams-classify-perl libvlc-bin libvlc5 libzmq5
  linux-image-amd64 maildrop python3-distutils vlc vlc-bin vlc-data vlc-l10n
  vlc-plugin-base vlc-plugin-qt vlc-plugin-video-output
The following packages will be upgraded:
  apache2-doc apt-listchanges aptitude-common console-setup
  console-setup-linux debian-reference-common debian-reference-en discover
  eudev glibc-doc gpm keyboard-configuration libbsd0 libc-bin libc-dev-bin
  libc-l10n libc6 libc6-dev libdbus-1-3 libdebconfclient0 libdiscover2
  libdns-export169 libegl-mesa0 libegl1-mesa libeudev-dev libeudev1
  libfastjson4 libgbm1 libgc1c2 libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa
  libglx-mesa0 libgmp-dev libgmp10 libgmpxx4ldbl libgpm2 libimlib2
  libisc-export166 libjs-sphinxdoc libldb1 liblogging-stdlog0 libmilter1.0.1
  libpagemaker-0.0-0 libperl5.26 libsmbclient libsystemd0 libudev-dev libudev1
  liburi-perl libwayland-egl1-mesa libwbclient0 libwireshark-data
  libwireshark10 libwiretap7 libwscodecs1 libwsutil8 libxatracker2 lintian
  linux-doc-4.14 linux-libc-dev locales mesa-common-dev multiarch-support
  mysql-common nano openssh-client perl perl-base perl-doc perl-modules-5.26
  rsyslog rsyslog-doc samba-libs tor tshark udev wireshark wireshark-common
  wireshark-doc wireshark-qt
81 upgraded, 0 newly installed, 0 to remove and 27 not upgraded.
Need to get 102 MB of archives.
After this operation, 1,076 kB of additional disk space will be used.
Do you want to continue? [Y/n]

And then I decided to try and find if my Devuan system is and has been since ever really dbus-free as I had expected. I have mounted a few dd'ed system images (they all are entire system under / partition, except for /boot, like the Gentoo of 2017-04-28 above), but that actually did in fact later...

I first have run:
# apt-get source libdbus-1-3
which got me the entire dbus package source, not just libdbus (regarding of which see the README further below: IIUC, libdbus is just the low level core installation of dbus):
# ls -l

total 2088
drwxr-xr-x 12 mr mr    4096 2018-01-17 13:05 dbus-1.12.2
-rw-r--r--  1 mr mr   59740 2017-11-13 16:53 dbus_1.12.2-1.debian.tar.xz
-rw-r--r--  1 mr mr    3684 2017-11-13 16:53 dbus_1.12.2-1.dsc
-rw-r--r--  1 mr mr 2063143 2017-11-13 16:53 dbus_1.12.2.orig.tar.gz
-rw-r--r--  1 mr mr     833 2017-11-13 16:53 dbus_1.12.2.orig.tar.gz.asc


# du -hs dbus-1.12.2/

11M     dbus-1.12.2/

# grep -B2 -A39 "desktop session bus" dbus-1.12.2/README

If you're considering D-Bus for use in a project, you should be aware
that D-Bus was designed for a couple of specific use cases, a "system
bus" and a "desktop session bus". These are documented in more detail
in the D-Bus specification and FAQ available on the web site.

If your use-case isn't one of these, D-Bus may still be useful, but
only by accident; so you should evaluate carefully whether D-Bus makes
sense for your project.

Security
==

If you find a security vulnerability that is not known to the public,
please report it privately to dbus-security@lists.freedesktop.org
or by reporting a freedesktop.org bug that is marked as
restricted to the "D-BUS security group" (you might need to "Show
Advanced Fields" to have that option).

On Unix systems, the system bus (dbus-daemon --system) is designed
to be a security boundary between users with different privileges.

On Unix systems, the session bus (dbus-daemon --session) is designed
to be used by a single user, and only accessible by that user.

We do not currently consider D-Bus on Windows to be security-supported,
and we do not recommend allowing untrusted users to access Windows
D-Bus via TCP.

Note: low-level API vs. high-level binding APIs
===

A core concept of the D-Bus implementation is that "libdbus" is
intended to be a low-level API. Most programmers are intended to use
the bindings to GLib, Qt, Python, Mono, Java, or whatever. These
bindings have varying levels of completeness and are maintained as
separate projects from the main D-Bus package. The main D-Bus package
contains the low-level libdbus, the bus daemon, and a few command-line
tools such as dbus-launch.

If you use the low-level API directly, you're signing up for some
pain. Think of the low-level API as analogous to Xlib or GDI, and the
high-level API as analogous to Qt/GTK+/HTML.

IIUC, I only have libdbus, which is the "core of D-Bus" and its "low-level API"... And I'm not free of it... I'm only free from its more high level stuff, I'm afraid...

I was dbus-free in Gentoo, completely (actually Gentoo devs decided to use just the gdbus, which gdbus I have not time to research right now)... I was dbus-free in Gentoo, completely, or almost completely.

But I'm not dbus-free in Devuan, I'm not... And have never been, in the 8 months that I'm running only Devuan in my SOHO...

I did the research, and here's what I found, looking for [the mount point]/lib/x86_64-linux-gnu/libdbus-1.so.3* in various remaining old dd'ed images of Devuan:

# ls -l /mnt/H1124-r/lib/x86_64-linux-gnu/libdbus-1.so.3*

lrwxrwxrwx 1 root root     20 2017-06-12 21:54 /mnt/H1124-r/lib/x86_64-linux-gnu/libdbus-1.so.3 -> libdbus-1.so.3.14.11
-rw-r--r-- 1 root root 321288 2017-06-12 21:54 /mnt/H1124-r/lib/x86_64-linux-gnu/libdbus-1.so.3.14.11

# ls -l /mnt/H1010-r/lib/x86_64-linux-gnu/libdbus-1.so.3*

lrwxrwxrwx 1 root root     20 2017-06-12 21:54 /mnt/H1010-r/lib/x86_64-linux-gnu/libdbus-1.so.3 -> libdbus-1.so.3.14.11
-rw-r--r-- 1 root root 321288 2017-06-12 21:54 /mnt/H1010-r/lib/x86_64-linux-gnu/libdbus-1.so.3.14.11

# ls -l /mnt/H0827-r/lib/x86_64-linux-gnu/libdbus-1.so.3*

lrwxrwxrwx 1 root root     20 2017-06-12 21:54 /mnt/H0827-r/lib/x86_64-linux-gnu/libdbus-1.so.3 -> libdbus-1.so.3.14.11
-rw-r--r-- 1 root root 321288 2017-06-12 21:54 /mnt/H0827-r/lib/x86_64-linux-gnu/libdbus-1.so.3.14.11

As you can see, I really should have spared you, gentle reader, this presenting of my search... Namely, it's obvious that the same "2017-06-12 21:54"-timestamped "core of D-Bus" was there all the time, and the instructions from the wiki which I explained how I long followed/wished for (actually I also somewhat inspired it), and gave link to above, those procedures, for some reason, effectively never removed it...

#8 Re: Installation » sans-dbus, Questions, Tips and Tricks on its Implementation » 2018-01-17 20:22:09

I'm sorry for some links not pointing to pages. It's not my fault, but the links were renamed after I posted them above...

Currently, the relevant link is:

https://git.devuan.org/dev1fanboy/Upgra … ut-dbus.md

But, I've just finished a (primitive) research on dbus (or D-Bus) in Devuan, and I've just opened:

sans-dbus in Devuan: low level core installation of dbus remain
https://dev1galaxy.org/viewtopic.php?id=1825

#9 Re: Documentation » Grsecurity/Pax installation on Devuan GNU/Linux » 2017-12-29 17:31:05

golinux wrote:

Wishing you a happy new year MiroR.  And everyone else too of course . . .

Thanks! To everyone Happy New Year (and Merry Xmas for those who wish)!

#11 Re: Installation » sans-dbus, Questions, Tips and Tricks on its Implementation » 2017-12-24 13:29:14

As usual, fsmithred has very useful insights/corrections. You actually saved my instllations from going the wrong way at least once. And

fsmithred wrote:

Pinning systemd-sysv to -1 is sufficient to prevent installation of systemd. In fact, you don't even need that. I just tried installing systemd after removing /etc/apt/preferences.d/avoid-systemd and it's not possible.

root@ascii:/home/user# aptitude -s install systemd
...

Ah, likely. I might remove that entry from my preferences{.d/some-name}, but it's not urgent. I have no issues whatsoever with systemd (and neither dbus nor pulse). I'm also aware that I have superfluouse entry for pulseaudio, but that either doesn't hurt. And also consolekit might be a thing of the past, but also: no hurt.

And very interesting is, as well, this:

bobjohnson wrote:

On this forum, there is a guy, presumably an employee at Open Suse who directly says DBUS makers are malicious.

But that was only licentia poetica (I just read the whole story.) It's (probably) only sloppy programming, that case:

https://github.com/apple/cups/issues/5143

jsmeix commented on Oct 20 •

Unbelievable!
It seems the D-Bus makers are intentionally malicious
because as far as I see in dbus-1.10.20 source code
there is in dbus/dbus-sysdeps.c

Yeah, that's not exploit facilitating or the next of kin to it: surveillance enabling.
And what I suspected with dbus, the reason for which I tried for years to get rid of it in my systems is those kindred just above.
If you visit this Gentoo Forum topic:
Updating and keeping your Gentoo non-poetterized
https://forums.gentoo.org/viewtopic-t-1012022.html
and skim through the (often too verbose) introductory page or two of the first post, but remaining in the first post, then search for
And, from what steveL wrote about that *!~@ware,
It's not my words, but they bring all the main reasons not to use dbus togetther in not-too lengthy text of less then 2800 chars. I regard it as precious enough to paste it in here:

steveL wrote:

...[snip]...
I agree dbus is a busted idea,
...[snip]...

miroR wrote:

It'd be huge work for me to try KDE out. It's beyond what I can do at this time. Too stretched. But I take your word on the sanity of KDE.

Just, can it be installed without dbus? I don't think so...

I did give KDE a try, some two weeks ago, on a cloned Gentoo machine (same MBOs, a few boxes in my SOHO, perfectly clonable from one onto another, dd dumping and dd restoring...), and tried to get Kaffeine.

Nope! It was dbus back in there. And it just wouldn't install without replacing my gnupg-1, which I want, with gnupg-2 which introduces GUI and other overhead...(

Yeah KDE requires dbus. I didn't have a problem with dbus when it came out, but over time I've realised it's a nutty idea. You're still tied to an ABI when you use it, irrespective of whether the underlying protocol can handle it, so all it does is act as an inappropriate bottleneck.

Strategically, it allows RedHat to sell its customers an opt-out from the GPL, while still effectively linking to GPL codebases. That hasn't been tested in Court of course, and I for one wouldn't believe any lawyer nor snake-oil salesman that it would stand up to inspection.

If anything, I'd fire the lawyer who dreamt it up or okayed it, as he's a liability.

Localising RPC doesn't stop it being a function-call; that's the whole point of RPC. All they're doing is exactly that, and labelling it IPC.

Indeed when I ran the above analysis of the motivation, past an embedded developer, his immediate response was "Yeah, that's exactly why we [his company] love dbus: because we can ignore the GPL."

That conversation also confirmed to me that another practitioner doesn't see any difference between calling a function via an API, and via an API wrapping an RPC call; from the code perspective it's exactly the same. Again, that's the whole point of RPC, so it would be very strange for anyone to argue otherwise.

Nor are any of those embedded companies anything other than practitioners, since they employ software developers to do this work.

So if I were them, I'd seriously start pulling myself out of that game, as they know full well they're breaking the law. There is no excuse of ignorance even feasible.

Technically speaking it's a terrible idea to think you can multiplex better than the kernel, when that is most of what the kernel does.

It is thus a liability in terms of efficiency, robustness and overall performance.

IPC should be left to the kernel to manage, since it has so many implications. By all means provide domain-specific convenience abstractions, where domain is data-related (ie user context); rather than desktop vs anything else.

Just don't be a muppet and buy into the emperor's "new clothes for old rope".
...[snip]...

And there's other reasons and things against the use of dbus. One other notorious one is that GnuPG developers just wouldn't want to use dbus because they didn't trust it.

However, proving that it is an exploit facillitator and surveillance enabler would not be easy in the least. I'm not that advanced, and may never become. But that is my strong feeling, just like I strongly feel that systemd was made for the same, well, for the latter one: the surveillance enabling, the purpose of which is the control over users, the point of entry to intrusion into the FOSS and of its corruption. Because for the big guys who want to dominate the world, FOSS is too pure, too honest, too unfriendly to introduce control over its users.

[[ Just don't forget, anybody reading here, that those dominators have --verging often on total-- control over alomost all Windows and Mac users, desktop or smartphones or other. and much more.  What they felt they were terribly missing is Linux... Therefore the LSM and SELinux, now almost a failure... Therefore the ripoff of grsecurity code that left GNU/Linux deprived of the two geniuses who kept fixeing the kernel: spender and PaX Team... but read the links in my sig for that... ]]

Regards!

#12 Re: Installation » sans-dbus, Questions, Tips and Tricks on its Implementation » 2017-12-24 11:33:03

As usual, fsmithred has very useful insights/corrections. You actually saved my instllations from going the wrong way at least once. And your Refracta is great, which I always use when I backup and clone my Air-Gap.

fsmithred wrote:

Pinning systemd-sysv to -1 is sufficient to prevent installation of systemd. In fact, you don't even need that. I just tried installing systemd after removing /etc/apt/preferences.d/avoid-systemd and it's not possible.

root@ascii:/home/user# aptitude -s install systemd
No candidate version found for systemd   
Unable to apply some actions, aborting
root@ascii:/home/user# aptitude -s install systemd-sysv
No candidate version found for systemd-sysv
Unable to apply some actions, aborting

I'll need to study the above a little...

And very interesting is, as well, this:

bobjohnson wrote:

On this forum, there is a guy, presumably an employee at Open Suse who directly says DBUS makers are malicious.

https://github.com/apple/cups/issues/5143


cut and pasted
------------------------------------------------------------------------
jsmeix commented on Oct 20 •

Unbelievable!
It seems the D-Bus makers are intentionally malicious
because as far as I see in dbus-1.10.20 source code
there is in dbus/dbus-sysdeps.c

------------------------------------------------------------------
cut and pasted



Is this the kind of thing that made you setup a non dbus system MiroR?

Not that I knew of the exploits allowed, catered for, or facillitated, or similar, by dbus developers, if that is what that linke turns out to be showing (haven't yet read it).
But it's this, what my reasoning was, way back 3 and a half years ago:
Uninstalling dbus and *kits (to Unfacilitate Remote Seats)
https://forums.gentoo.org/viewtopic-t-992146.html
and later on there was more, but I can't find it... Hmmhh... maybe, wait...
...
I did find something...
Re: [DNG] Will there be a MirDevuan "WTF"?
https://lists.dyne.org/lurker/thread/20 … 5.7371808e
where you can see I participated in the discussion (miro.rovis).

But I wrote much more, with very detailed explanation of my suspicion on dbus and why I was so suspicious...

Oh, yeah, this one it is:
Will there be a MirDevuan "WTF"?
https://lists.dyne.org/lurker/message/2 … 6a.en.html

It was harsh tones at first on almost all sides...

But it has been accepted, eventually, by our leaders. See Jaromil's email in the same thread:
https://lists.dyne.org/lurker/message/2 … 61.en.html
where he wrote the fine and memorable:

Jaromil wrote:
miroR wrote:

And to me, that really has much more weight than the little hardship
that made me a little annoyed and, also spiteful, in one or two
occasions. I hope this matter need not cause unrest to anyone any
longer now.

just water over the dam.

And I'm still happy about it smile. (Some people here know that I'm politically on opposite side than some of our leaders, but politics must not matter in free software)

#13 Re: Installation » Keeping track of no-apt installs (installing out-of Devuan PM) » 2017-12-21 19:53:12

Regarding these hashes of files in my cloned system for online:

miroR wrote:

...
...

# cat /var/log/no-apt/getmail_5.5.files.sum
6b728dc21586d609a4ef3e4658166c8d345d1a8070d58992ae6c1103309a1d74  /usr/lib/python2.7/dist-packages/getmail-5.5-py2.7.egg-info
ed7fbfc1c821a7fbe59185f2a5330433b66d3695d2448b41aa0645c7111da72a  /usr/lib/python2.7/dist-packages/getmailcore/utilities.pyc
3f95f910f5f12a1f5274996545878f5c08ea030661b8a6eae06423dd6826aaca  /usr/lib/python2.7/dist-packages/getmailcore/_pop3ssl.pyc
...
04cfb870dbf73217c71e8746a2c36233c673a68eaa8635056074e1d2bfa0af98  /usr/bin/getmail
977a97233b042c74d7dcae25585d1638616934b0250d6226463ff4ceb5408265  /usr/bin/getmail_maildir
c351e9fc1f6a632c2482ff5dbd44d4a6e4707d5eda1ad9a8995147f23d11cd94  /usr/bin/getmail_fetch

Not only are these pertaining to my install only. They are also pertaining only to this in-the-clone and not in-the-Air-Gap system.

Read:
Updating the Air-Gapped System
https://dev1galaxy.org/viewtopic.php?id=763
to learn about the drawbacks of Air-Gapping. A number of things like this one, have to be replicated in the Air-Gap... Aarrghh... But when I think how good it is to be confident of your backup, plus the abilitiy to recover your systems from attacks... Then I can still enjoy doing it again. It's simply worth the while.

#14 Re: Installation » Keeping track of no-apt installs (installing out-of Devuan PM) » 2017-12-21 19:30:48

Here's the email that I sent:
https://marc.info/?l=getmail&m=151388419504433&w=2

And the attachment to that email, the link under this string (in bottom)
["getmail_171221_180802_gdOv.log.xz" (application/x-xz)]
https://marc.info/?l=getmail&m=151388419504433&q=p5
for whoever cares to check it, show how my Getmail 5.5 works, apparently, so far, just fine.

#15 Re: Installation » Keeping track of no-apt installs (installing out-of Devuan PM) » 2017-12-21 17:59:23

So, the too early promised installation of Getmail should finally follow here.

I got the package as I explained, and the README says:

...
getmail is Copyright (C) 1998-2009 Charles Cazabon.
...

To install:  getmail v.4 uses the standard Python distutils.  Do the following
  as a regular user:

    python setup.py build

  Then (probably as root), do:

    python setup.py install

  This will install the software as follows:

    -the four scripts will be installed in <PREFIX>/bin/
    -the Python files will be installed under the site-packages directory of
     your Python installation (typically /usr/local/lib/pythonXXX or
     /usr/lib/pythonXXX, but may be elsewhere -- this is detected automatically)
    -the documentation will be installed under <PREFIX>/doc/getmail-<version>/
    -the man pages will be installed under <PREFIX>/man/

Of the listing of the removed getmail, in the text of the README I only do not see:

/var/lib/dpkg/info/getmail4.list
/var/lib/dpkg/info/getmail4.prerm
/var/lib/dpkg/info/getmail4.postinst
/var/lib/dpkg/info/getmail4.md5sums

but that's perfectly fine. Those are dpkg/apt -installed files, not Getmail per se.

Now this:

  <PREFIX> is the directory Python was configured to install under (typically
  either /usr/local/ or /usr/, but may be another value).  See the file
  docs/documentation.html or docs/documentation.txt for details on installing
  files to directories other than these defaults.

I will reference just after I comment the rest of this README.

Taking not of this paragraph for possible later troubleshooting:

The four scripts included in the package (getmail, getmail_maildir,
getmail_mbox, and getmail_fetch) will have their "#!"-interpreter line
automatically modified to invoke the Python interpreter you run the setup
script with.  If you later remove this version of Python, and the newer version
does not provide a link to the interpreter with that name, you will have to
modify the scripts or re-run the setup.py script.

And I'll reread the rest of this README here under later, once I have Getmail installed in the system, and listed like I have Gradm installed and listed and can check that its files are still in the correct state.

See the HTML documentation for details on setting up and using getmail.  It is
included in the docs subdirectory of the distribution tarball, and will be
installed in <PREFIX>/doc/getmail-<version>/ (by default).  10-second summary
for personal use:

  1. Install getmail
  2. mkdir -m 700 ~/.getmail
  3. Create ~/.getmail/getmailrc by following the instructions.
  4. Run `getmail`.

See docs/BUGS for instructions on reporting bugs in this software.

And the line just above is for you go to shout and scream at smile Joking of course.

I've just commented this README, and now let's go to:

  docs/documentation.html or docs/documentation.txt for details on installing
  files to directories other than these defaults.

which is:
http://pyropus.ca/software/getmail/docu … -altprefix

containing (I don't like installing in /usr/local/ but the usual locations even when I install no-apt):

# python setup.py install --prefix=<path>

which means, I'd say, in my case (and generally for Devuan/Debian):

# python setup.py install --prefix=/usr

So first issue a new:

# find / -xdev -name '*' > FIND_$(date +%y%m%d_%H%M%S)

because I don't want no Pale Moon caches and stuff in the listing, I only want the changes that matter for my getmail listing in my /var/log/no-apt/ dir.

Then I enter where I decompressed the getmail package:

$ cd src/getmail-5.5/

and run:

mr@gdOv:~/src/getmail-5.5$ python setup.py build |& tee ~mr/LOG_/getmail_$(date +%y%m%d_%H%M%S)_python_setup.py_build

to get a log for troubleshooting if things go wrong for some reason.

This is what it got me:

mr@gdOv:~/src/getmail-5.5$ cat ~mr/LOG_/getmail_171221_164741_python_setup.py_build
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.7
creating build/lib.linux-x86_64-2.7/getmailcore
copying getmailcore/_pop3ssl.py -> build/lib.linux-x86_64-2.7/getmailcore
copying getmailcore/exceptions.py -> build/lib.linux-x86_64-2.7/getmailcore
copying getmailcore/imap_utf7.py -> build/lib.linux-x86_64-2.7/getmailcore
copying getmailcore/_retrieverbases.py -> build/lib.linux-x86_64-2.7/getmailcore
copying getmailcore/message.py -> build/lib.linux-x86_64-2.7/getmailcore
copying getmailcore/baseclasses.py -> build/lib.linux-x86_64-2.7/getmailcore
copying getmailcore/logging.py -> build/lib.linux-x86_64-2.7/getmailcore
copying getmailcore/__init__.py -> build/lib.linux-x86_64-2.7/getmailcore
copying getmailcore/filters.py -> build/lib.linux-x86_64-2.7/getmailcore
copying getmailcore/destinations.py -> build/lib.linux-x86_64-2.7/getmailcore
copying getmailcore/retrievers.py -> build/lib.linux-x86_64-2.7/getmailcore
copying getmailcore/compatibility.py -> build/lib.linux-x86_64-2.7/getmailcore
copying getmailcore/utilities.py -> build/lib.linux-x86_64-2.7/getmailcore
copying getmailcore/constants.py -> build/lib.linux-x86_64-2.7/getmailcore
running build_scripts
creating build/scripts-2.7
copying and adjusting getmail -> build/scripts-2.7
copying and adjusting getmail_fetch -> build/scripts-2.7
copying and adjusting getmail_maildir -> build/scripts-2.7
copying and adjusting getmail_mbox -> build/scripts-2.7
changing mode of build/scripts-2.7/getmail from 644 to 755
changing mode of build/scripts-2.7/getmail_fetch from 644 to 755
changing mode of build/scripts-2.7/getmail_maildir from 644 to 755
changing mode of build/scripts-2.7/getmail_mbox from 644 to 755

Again the find run:

# find / -xdev -name '*' > FIND_$(date +%y%m%d_%H%M%S)

And I checked the two FIND_xxx's. Here:

# diff FIND_171221_164*
183a184
> /home/mr/FIND_171221_164908
11619a11621
> /home/mr/LOG_/getmail_171221_164741_python_setup.py_build
#

Something went wrong! What am I going to do now? wink Nothing is wrong. I just won't have the listing of files changed by that python script. The reason nothing is listed is because the ~mr/src is just:

$ ls -l ~mr/src
lrwxrwxrwx 1 mr mr 8 2017-12-21 16:42 /home/mr/src -> /Cmn/src
$

a symlink, and I got -xdev flag in the find command. All is still well.

And now:

root@gdOv:/home/mr/src/getmail-5.5# python setup.py install |& tee ~mr/LOG_/getmail_$(date +%y%m%d_%H%M%S)_python_setup.py_install

which got me (the log):

root@gdOv:/home/mr/src/getmail-5.5# cat /home/mr/LOG_/getmail_171221_165421_python_setup.py_install
running install
running build
running build_py
running build_scripts
running install_lib
creating /usr/local/lib/python2.7/dist-packages/getmailcore
copying build/lib.linux-x86_64-2.7/getmailcore/_pop3ssl.py -> /usr/local/lib/python2.7/dist-packages/getmailcore
copying build/lib.linux-x86_64-2.7/getmailcore/exceptions.py -> /usr/local/lib/python2.7/dist-packages/getmailcore
copying build/lib.linux-x86_64-2.7/getmailcore/imap_utf7.py -> /usr/local/lib/python2.7/dist-packages/getmailcore
copying build/lib.linux-x86_64-2.7/getmailcore/_retrieverbases.py -> /usr/local/lib/python2.7/dist-packages/getmailcore
copying build/lib.linux-x86_64-2.7/getmailcore/message.py -> /usr/local/lib/python2.7/dist-packages/getmailcore
copying build/lib.linux-x86_64-2.7/getmailcore/baseclasses.py -> /usr/local/lib/python2.7/dist-packages/getmailcore
copying build/lib.linux-x86_64-2.7/getmailcore/logging.py -> /usr/local/lib/python2.7/dist-packages/getmailcore
copying build/lib.linux-x86_64-2.7/getmailcore/__init__.py -> /usr/local/lib/python2.7/dist-packages/getmailcore
copying build/lib.linux-x86_64-2.7/getmailcore/filters.py -> /usr/local/lib/python2.7/dist-packages/getmailcore
copying build/lib.linux-x86_64-2.7/getmailcore/destinations.py -> /usr/local/lib/python2.7/dist-packages/getmailcore
copying build/lib.linux-x86_64-2.7/getmailcore/retrievers.py -> /usr/local/lib/python2.7/dist-packages/getmailcore
copying build/lib.linux-x86_64-2.7/getmailcore/compatibility.py -> /usr/local/lib/python2.7/dist-packages/getmailcore
copying build/lib.linux-x86_64-2.7/getmailcore/utilities.py -> /usr/local/lib/python2.7/dist-packages/getmailcore
copying build/lib.linux-x86_64-2.7/getmailcore/constants.py -> /usr/local/lib/python2.7/dist-packages/getmailcore
byte-compiling /usr/local/lib/python2.7/dist-packages/getmailcore/_pop3ssl.py to _pop3ssl.pyc
byte-compiling /usr/local/lib/python2.7/dist-packages/getmailcore/exceptions.py to exceptions.pyc
byte-compiling /usr/local/lib/python2.7/dist-packages/getmailcore/imap_utf7.py to imap_utf7.pyc
byte-compiling /usr/local/lib/python2.7/dist-packages/getmailcore/_retrieverbases.py to _retrieverbases.pyc
byte-compiling /usr/local/lib/python2.7/dist-packages/getmailcore/message.py to message.pyc
byte-compiling /usr/local/lib/python2.7/dist-packages/getmailcore/baseclasses.py to baseclasses.pyc
byte-compiling /usr/local/lib/python2.7/dist-packages/getmailcore/logging.py to logging.pyc
byte-compiling /usr/local/lib/python2.7/dist-packages/getmailcore/__init__.py to __init__.pyc
byte-compiling /usr/local/lib/python2.7/dist-packages/getmailcore/filters.py to filters.pyc
byte-compiling /usr/local/lib/python2.7/dist-packages/getmailcore/destinations.py to destinations.pyc
byte-compiling /usr/local/lib/python2.7/dist-packages/getmailcore/retrievers.py to retrievers.pyc
byte-compiling /usr/local/lib/python2.7/dist-packages/getmailcore/compatibility.py to compatibility.pyc
byte-compiling /usr/local/lib/python2.7/dist-packages/getmailcore/utilities.py to utilities.pyc
byte-compiling /usr/local/lib/python2.7/dist-packages/getmailcore/constants.py to constants.pyc
running install_scripts
copying build/scripts-2.7/getmail -> /usr/local/bin
copying build/scripts-2.7/getmail_mbox -> /usr/local/bin
copying build/scripts-2.7/getmail_fetch -> /usr/local/bin
copying build/scripts-2.7/getmail_maildir -> /usr/local/bin
changing mode of /usr/local/bin/getmail to 755
changing mode of /usr/local/bin/getmail_mbox to 755
changing mode of /usr/local/bin/getmail_fetch to 755
changing mode of /usr/local/bin/getmail_maildir to 755
running install_data
creating /usr/share/doc/getmail-5.5
copying ./README -> /usr/share/doc/getmail-5.5
copying ./getmail.spec -> /usr/share/doc/getmail-5.5
copying docs/BUGS -> /usr/share/doc/getmail-5.5
copying docs/COPYING -> /usr/share/doc/getmail-5.5
copying docs/CHANGELOG -> /usr/share/doc/getmail-5.5
copying docs/TODO -> /usr/share/doc/getmail-5.5
copying docs/THANKS -> /usr/share/doc/getmail-5.5
copying docs/configuration.html -> /usr/share/doc/getmail-5.5
copying docs/configuration.txt -> /usr/share/doc/getmail-5.5
copying docs/documentation.html -> /usr/share/doc/getmail-5.5
copying docs/documentation.txt -> /usr/share/doc/getmail-5.5
copying docs/faq.html -> /usr/share/doc/getmail-5.5
copying docs/faq.txt -> /usr/share/doc/getmail-5.5
copying docs/getmaildocs.css -> /usr/share/doc/getmail-5.5
copying docs/getmailrc-examples -> /usr/share/doc/getmail-5.5
copying docs/troubleshooting.html -> /usr/share/doc/getmail-5.5
copying docs/troubleshooting.txt -> /usr/share/doc/getmail-5.5
copying docs/getmail.1 -> /usr/share/man/man1
copying docs/getmail_fetch.1 -> /usr/share/man/man1
copying docs/getmail_maildir.1 -> /usr/share/man/man1
copying docs/getmail_mbox.1 -> /usr/share/man/man1
running install_egg_info
Writing /usr/local/lib/python2.7/dist-packages/getmail-5.5.egg-info

and the new files in the system under / are:

# diff FIND_171221_164908 FIND_171221_165641 | grep '> ' | sed 's/> //'
/usr/local/lib/python2.7/dist-packages/getmail-5.5.egg-info
/usr/local/lib/python2.7/dist-packages/getmailcore
/usr/local/lib/python2.7/dist-packages/getmailcore/utilities.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/_pop3ssl.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/compatibility.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/__init__.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/compatibility.py
/usr/local/lib/python2.7/dist-packages/getmailcore/_retrieverbases.py
/usr/local/lib/python2.7/dist-packages/getmailcore/__init__.py
/usr/local/lib/python2.7/dist-packages/getmailcore/destinations.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/filters.py
/usr/local/lib/python2.7/dist-packages/getmailcore/constants.py
/usr/local/lib/python2.7/dist-packages/getmailcore/imap_utf7.py
/usr/local/lib/python2.7/dist-packages/getmailcore/baseclasses.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/destinations.py
/usr/local/lib/python2.7/dist-packages/getmailcore/message.py
/usr/local/lib/python2.7/dist-packages/getmailcore/logging.py
/usr/local/lib/python2.7/dist-packages/getmailcore/logging.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/exceptions.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/message.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/retrievers.py
/usr/local/lib/python2.7/dist-packages/getmailcore/retrievers.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/exceptions.py
/usr/local/lib/python2.7/dist-packages/getmailcore/_pop3ssl.py
/usr/local/lib/python2.7/dist-packages/getmailcore/utilities.py
/usr/local/lib/python2.7/dist-packages/getmailcore/filters.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/constants.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/imap_utf7.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/_retrieverbases.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/baseclasses.py
/usr/local/bin/getmail_mbox
/usr/local/bin/getmail
/usr/local/bin/getmail_maildir
/usr/local/bin/getmail_fetch
/usr/share/doc/getmail-5.5
/usr/share/doc/getmail-5.5/TODO
/usr/share/doc/getmail-5.5/troubleshooting.txt
/usr/share/doc/getmail-5.5/documentation.txt
/usr/share/doc/getmail-5.5/faq.txt
/usr/share/doc/getmail-5.5/getmailrc-examples
/usr/share/doc/getmail-5.5/getmail.spec
/usr/share/doc/getmail-5.5/getmaildocs.css
/usr/share/doc/getmail-5.5/README
/usr/share/doc/getmail-5.5/troubleshooting.html
/usr/share/doc/getmail-5.5/COPYING
/usr/share/doc/getmail-5.5/BUGS
/usr/share/doc/getmail-5.5/configuration.txt
/usr/share/doc/getmail-5.5/faq.html
/usr/share/doc/getmail-5.5/CHANGELOG
/usr/share/doc/getmail-5.5/documentation.html
/usr/share/doc/getmail-5.5/configuration.html
/usr/share/doc/getmail-5.5/THANKS
/usr/share/man/man1/getmail_maildir.1
/usr/share/man/man1/getmail_mbox.1
/usr/share/man/man1/getmail.1
/usr/share/man/man1/getmail_fetch.1

But I forgot to give it the --prefix=/usr flag. And this, while probably not really wrong, is not to my liking.

So I saved that to:

# diff FIND_171221_164908 FIND_171221_165641 | grep '> ' | sed 's/> //' > TMP

and ran:

# rm -v $(cat TMP)
# rmdir -v $(cat TMP)

( and find runs previous and afterwards, and I can tell you I'm at the state pretty much clearly at before the install without the --prefix=/usr .

These:

# diff FIND_171221_170048  FIND_171221_170119 | grep '< ' | sed 's/< //'
/usr/local/lib/python2.7/dist-packages/getmail-5.5.egg-info
/usr/local/lib/python2.7/dist-packages/getmailcore
/usr/local/lib/python2.7/dist-packages/getmailcore/utilities.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/_pop3ssl.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/compatibility.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/__init__.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/compatibility.py
/usr/local/lib/python2.7/dist-packages/getmailcore/_retrieverbases.py
/usr/local/lib/python2.7/dist-packages/getmailcore/__init__.py
/usr/local/lib/python2.7/dist-packages/getmailcore/destinations.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/filters.py
/usr/local/lib/python2.7/dist-packages/getmailcore/constants.py
/usr/local/lib/python2.7/dist-packages/getmailcore/imap_utf7.py
/usr/local/lib/python2.7/dist-packages/getmailcore/baseclasses.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/destinations.py
/usr/local/lib/python2.7/dist-packages/getmailcore/message.py
/usr/local/lib/python2.7/dist-packages/getmailcore/logging.py
/usr/local/lib/python2.7/dist-packages/getmailcore/logging.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/exceptions.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/message.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/retrievers.py
/usr/local/lib/python2.7/dist-packages/getmailcore/retrievers.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/exceptions.py
/usr/local/lib/python2.7/dist-packages/getmailcore/_pop3ssl.py
/usr/local/lib/python2.7/dist-packages/getmailcore/utilities.py
/usr/local/lib/python2.7/dist-packages/getmailcore/filters.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/constants.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/imap_utf7.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/_retrieverbases.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/baseclasses.py
/usr/local/bin/getmail_mbox
/usr/local/bin/getmail
/usr/local/bin/getmail_maildir
/usr/local/bin/getmail_fetch
/usr/share/doc/getmail-5.5
/usr/share/doc/getmail-5.5/TODO
/usr/share/doc/getmail-5.5/troubleshooting.txt
/usr/share/doc/getmail-5.5/documentation.txt
/usr/share/doc/getmail-5.5/faq.txt
/usr/share/doc/getmail-5.5/getmailrc-examples
/usr/share/doc/getmail-5.5/getmail.spec
/usr/share/doc/getmail-5.5/getmaildocs.css
/usr/share/doc/getmail-5.5/README
/usr/share/doc/getmail-5.5/troubleshooting.html
/usr/share/doc/getmail-5.5/COPYING
/usr/share/doc/getmail-5.5/BUGS
/usr/share/doc/getmail-5.5/configuration.txt
/usr/share/doc/getmail-5.5/faq.html
/usr/share/doc/getmail-5.5/CHANGELOG
/usr/share/doc/getmail-5.5/documentation.html
/usr/share/doc/getmail-5.5/configuration.html
/usr/share/doc/getmail-5.5/THANKS
/usr/share/man/man1/getmail_maildir.1
/usr/share/man/man1/getmail_mbox.1
/usr/share/man/man1/getmail.1
/usr/share/man/man1/getmail_fetch.1
/usr/local/lib/python2.7/dist-packages/getmail-5.5.egg-info
/usr/local/lib/python2.7/dist-packages/getmailcore
/usr/local/lib/python2.7/dist-packages/getmailcore/utilities.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/_pop3ssl.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/compatibility.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/__init__.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/compatibility.py
/usr/local/lib/python2.7/dist-packages/getmailcore/_retrieverbases.py
/usr/local/lib/python2.7/dist-packages/getmailcore/__init__.py
/usr/local/lib/python2.7/dist-packages/getmailcore/destinations.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/filters.py
/usr/local/lib/python2.7/dist-packages/getmailcore/constants.py
/usr/local/lib/python2.7/dist-packages/getmailcore/imap_utf7.py
/usr/local/lib/python2.7/dist-packages/getmailcore/baseclasses.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/destinations.py
/usr/local/lib/python2.7/dist-packages/getmailcore/message.py
/usr/local/lib/python2.7/dist-packages/getmailcore/logging.py
/usr/local/lib/python2.7/dist-packages/getmailcore/logging.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/exceptions.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/message.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/retrievers.py
/usr/local/lib/python2.7/dist-packages/getmailcore/retrievers.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/exceptions.py
/usr/local/lib/python2.7/dist-packages/getmailcore/_pop3ssl.py
/usr/local/lib/python2.7/dist-packages/getmailcore/utilities.py
/usr/local/lib/python2.7/dist-packages/getmailcore/filters.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/constants.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/imap_utf7.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/_retrieverbases.pyc
/usr/local/lib/python2.7/dist-packages/getmailcore/baseclasses.py
/usr/local/bin/getmail_mbox
/usr/local/bin/getmail
/usr/local/bin/getmail_maildir
/usr/local/bin/getmail_fetch
/usr/share/doc/getmail-5.5
/usr/share/doc/getmail-5.5/TODO
/usr/share/doc/getmail-5.5/troubleshooting.txt
/usr/share/doc/getmail-5.5/documentation.txt
/usr/share/doc/getmail-5.5/faq.txt
/usr/share/doc/getmail-5.5/getmailrc-examples
/usr/share/doc/getmail-5.5/getmail.spec
/usr/share/doc/getmail-5.5/getmaildocs.css
/usr/share/doc/getmail-5.5/README
/usr/share/doc/getmail-5.5/troubleshooting.html
/usr/share/doc/getmail-5.5/COPYING
/usr/share/doc/getmail-5.5/BUGS
/usr/share/doc/getmail-5.5/configuration.txt
/usr/share/doc/getmail-5.5/faq.html
/usr/share/doc/getmail-5.5/CHANGELOG
/usr/share/doc/getmail-5.5/documentation.html
/usr/share/doc/getmail-5.5/configuration.html
/usr/share/doc/getmail-5.5/THANKS
/usr/share/man/man1/getmail_maildir.1
/usr/share/man/man1/getmail_mbox.1
/usr/share/man/man1/getmail.1
/usr/share/man/man1/getmail_fetch.1

must not be there anymore:

root@gdOv:/home/mr# for i in $(cat TMP.ls-1); do if [ -e "$i" ] ; then ls -l $i ; fi ;  done ;
root@gdOv:/home/mr# 

And they're not.
Now (I hope) more correctly:

root@gdOv:/home/mr/src/getmail-5.5# python setup.py install --prefix=/usr |& tee ~mr/LOG_/getmail_$(date +%y%m%d_%H%M%S)_python_setup.py_install_prefix_usr

( in this output I manually deleting the norelated stuff such as the line

/var/lib/clamav/clamav-f57f9106483b495ef8877d9d2fde2ab5.tmp

because Clamav attemped to get updated, and I cut the connection while it was doing so, at my earlier looking for the docs on pyropus.ca to find the right line to get --prefix=/usr

/usr/lib/python2.7/site-packages
/usr/lib/python2.7/site-packages/getmail-5.5-py2.7.egg-info
/usr/lib/python2.7/site-packages/getmailcore
/usr/lib/python2.7/site-packages/getmailcore/utilities.pyc
/usr/lib/python2.7/site-packages/getmailcore/_pop3ssl.pyc
/usr/lib/python2.7/site-packages/getmailcore/compatibility.pyc
/usr/lib/python2.7/site-packages/getmailcore/__init__.pyc
/usr/lib/python2.7/site-packages/getmailcore/compatibility.py
/usr/lib/python2.7/site-packages/getmailcore/_retrieverbases.py
/usr/lib/python2.7/site-packages/getmailcore/__init__.py
/usr/lib/python2.7/site-packages/getmailcore/destinations.pyc
/usr/lib/python2.7/site-packages/getmailcore/filters.py
/usr/lib/python2.7/site-packages/getmailcore/constants.py
/usr/lib/python2.7/site-packages/getmailcore/imap_utf7.py
/usr/lib/python2.7/site-packages/getmailcore/baseclasses.pyc
/usr/lib/python2.7/site-packages/getmailcore/destinations.py
/usr/lib/python2.7/site-packages/getmailcore/message.py
/usr/lib/python2.7/site-packages/getmailcore/logging.py
/usr/lib/python2.7/site-packages/getmailcore/logging.pyc
/usr/lib/python2.7/site-packages/getmailcore/exceptions.pyc
/usr/lib/python2.7/site-packages/getmailcore/message.pyc
/usr/lib/python2.7/site-packages/getmailcore/retrievers.py
/usr/lib/python2.7/site-packages/getmailcore/retrievers.pyc
/usr/lib/python2.7/site-packages/getmailcore/exceptions.py
/usr/lib/python2.7/site-packages/getmailcore/_pop3ssl.py
/usr/lib/python2.7/site-packages/getmailcore/utilities.py
/usr/lib/python2.7/site-packages/getmailcore/filters.pyc
/usr/lib/python2.7/site-packages/getmailcore/constants.pyc
/usr/lib/python2.7/site-packages/getmailcore/imap_utf7.pyc
/usr/lib/python2.7/site-packages/getmailcore/_retrieverbases.pyc
/usr/lib/python2.7/site-packages/getmailcore/baseclasses.py
/usr/share/doc/getmail-5.5
/usr/share/doc/getmail-5.5/TODO
/usr/share/doc/getmail-5.5/troubleshooting.txt
/usr/share/doc/getmail-5.5/documentation.txt
/usr/share/doc/getmail-5.5/faq.txt
/usr/share/doc/getmail-5.5/getmailrc-examples
/usr/share/doc/getmail-5.5/getmail.spec
/usr/share/doc/getmail-5.5/getmaildocs.css
/usr/share/doc/getmail-5.5/README
/usr/share/doc/getmail-5.5/troubleshooting.html
/usr/share/doc/getmail-5.5/COPYING
/usr/share/doc/getmail-5.5/BUGS
/usr/share/doc/getmail-5.5/configuration.txt
/usr/share/doc/getmail-5.5/faq.html
/usr/share/doc/getmail-5.5/CHANGELOG
/usr/share/doc/getmail-5.5/documentation.html
/usr/share/doc/getmail-5.5/configuration.html
/usr/share/doc/getmail-5.5/THANKS
/usr/share/man/man1/getmail_maildir.1
/usr/share/man/man1/getmail_mbox.1
/usr/share/man/man1/getmail.1
/usr/share/man/man1/getmail_fetch.1
/usr/bin/getmail_mbox
/usr/bin/getmail
/usr/bin/getmail_maildir
/usr/bin/getmail_fetch

And if these files are installed, I can check every one of them, such as with a loop like this:

Ooopss... Have to interrupt me. I can't yet... Wait...

No. I can't yet... For some reason:

mr@gdOv:~$ getmail --version
ImportError:  No module named getmailcore
mr@gdOv:~$

something has gone wrong...

Let me see. It could be the grsec. It's much greater protection, but it is a little more difficult to manage than usual and more vulnerable system...

I'll try and see in the logs.

No, nothing, not " denied " or "segmentation fault" or similar lines typical for when grsec identifies a problem, or hasn't got a perm for something because of insufficiently well setup policy with its gradm package that allows great RBAC (Role Based Access) control.

It apparently was just this. In the Devuan package it is:

# cat /var/log/no-apt/getmail_4.53.0-2_REMOVED.files
/usr/lib/python2.7/dist-packages/getmail-4.54.0.egg-info
/usr/lib/python2.7/dist-packages/getmailcore
/usr/lib/python2.7/dist-packages/getmailcore/utilities.pyc
...

But in this from source install it is:

/usr/lib/python2.7/site-packages
/usr/lib/python2.7/site-packages/getmail-5.5-py2.7.egg-info
/usr/lib/python2.7/site-packages/getmailcore
/usr/lib/python2.7/site-packages/getmailcore/utilities.pyc
...

After copying the new from source to the /usr/lib/python2.7/dist-packages/, it is now working... How well, yet to learn... Phew! But it's so good to have a backup to go to smile ... Even if this should fail, it's just time, my system can't --well, not easily-- be lost.

So, what I did was just something to the effect of:

# cp -ai /usr/lib/python2.7/site-packages/getmail* /usr/lib/python2.7/dist-packages/

and now I got:

mr@gdOv:~$ getmail --version
getmail 5.5
mr@gdOv:~$

Hmmmhhh. Do I know that it will work? Not yet... But let me (even with the doubled site-packages/ and dist-packages/ above --because hey, better too much than too little, and I will ask the devs if any non-advanced user would so easily figured out how to fix the scary ImportError:  No module named getmailcore error above... No I won't, let them read about it themselves smile . But let's first save the listing of those files, and save the hashes before I go online to get my mail the way Getmail devs need to check on my report.

# diff FIND_171221_171149  FIND_171221_174159  | grep -v moonchild | grep -v '\/home\/mr\/' | grep -v clamav | grep '> ' | sed 's/> //' > /var/log/no-apt/getmail_5.5.files

And

# cat /var/log/no-apt/getmail_5.5.files
/usr/lib/python2.7/dist-packages/getmail-5.5-py2.7.egg-info
/usr/lib/python2.7/dist-packages/getmailcore
/usr/lib/python2.7/dist-packages/getmailcore/utilities.pyc
/usr/lib/python2.7/dist-packages/getmailcore/_pop3ssl.pyc
/usr/lib/python2.7/dist-packages/getmailcore/compatibility.pyc
/usr/lib/python2.7/dist-packages/getmailcore/__init__.pyc
/usr/lib/python2.7/dist-packages/getmailcore/compatibility.py
/usr/lib/python2.7/dist-packages/getmailcore/_retrieverbases.py
/usr/lib/python2.7/dist-packages/getmailcore/__init__.py
/usr/lib/python2.7/dist-packages/getmailcore/destinations.pyc
/usr/lib/python2.7/dist-packages/getmailcore/filters.py
/usr/lib/python2.7/dist-packages/getmailcore/constants.py
/usr/lib/python2.7/dist-packages/getmailcore/imap_utf7.py
/usr/lib/python2.7/dist-packages/getmailcore/baseclasses.pyc
/usr/lib/python2.7/dist-packages/getmailcore/destinations.py
/usr/lib/python2.7/dist-packages/getmailcore/message.py
/usr/lib/python2.7/dist-packages/getmailcore/logging.py
/usr/lib/python2.7/dist-packages/getmailcore/logging.pyc
/usr/lib/python2.7/dist-packages/getmailcore/exceptions.pyc
/usr/lib/python2.7/dist-packages/getmailcore/message.pyc
/usr/lib/python2.7/dist-packages/getmailcore/retrievers.py
/usr/lib/python2.7/dist-packages/getmailcore/retrievers.pyc
/usr/lib/python2.7/dist-packages/getmailcore/exceptions.py
/usr/lib/python2.7/dist-packages/getmailcore/_pop3ssl.py
/usr/lib/python2.7/dist-packages/getmailcore/utilities.py
/usr/lib/python2.7/dist-packages/getmailcore/filters.pyc
/usr/lib/python2.7/dist-packages/getmailcore/constants.pyc
/usr/lib/python2.7/dist-packages/getmailcore/imap_utf7.pyc
/usr/lib/python2.7/dist-packages/getmailcore/_retrieverbases.pyc
/usr/lib/python2.7/dist-packages/getmailcore/baseclasses.py
/usr/lib/python2.7/site-packages
/usr/lib/python2.7/site-packages/getmail-5.5-py2.7.egg-info
/usr/lib/python2.7/site-packages/getmailcore
/usr/lib/python2.7/site-packages/getmailcore/utilities.pyc
/usr/lib/python2.7/site-packages/getmailcore/_pop3ssl.pyc
/usr/lib/python2.7/site-packages/getmailcore/compatibility.pyc
/usr/lib/python2.7/site-packages/getmailcore/__init__.pyc
/usr/lib/python2.7/site-packages/getmailcore/compatibility.py
/usr/lib/python2.7/site-packages/getmailcore/_retrieverbases.py
/usr/lib/python2.7/site-packages/getmailcore/__init__.py
/usr/lib/python2.7/site-packages/getmailcore/destinations.pyc
/usr/lib/python2.7/site-packages/getmailcore/filters.py
/usr/lib/python2.7/site-packages/getmailcore/constants.py
/usr/lib/python2.7/site-packages/getmailcore/imap_utf7.py
/usr/lib/python2.7/site-packages/getmailcore/baseclasses.pyc
/usr/lib/python2.7/site-packages/getmailcore/destinations.py
/usr/lib/python2.7/site-packages/getmailcore/message.py
/usr/lib/python2.7/site-packages/getmailcore/logging.py
/usr/lib/python2.7/site-packages/getmailcore/logging.pyc
/usr/lib/python2.7/site-packages/getmailcore/exceptions.pyc
/usr/lib/python2.7/site-packages/getmailcore/message.pyc
/usr/lib/python2.7/site-packages/getmailcore/retrievers.py
/usr/lib/python2.7/site-packages/getmailcore/retrievers.pyc
/usr/lib/python2.7/site-packages/getmailcore/exceptions.py
/usr/lib/python2.7/site-packages/getmailcore/_pop3ssl.py
/usr/lib/python2.7/site-packages/getmailcore/utilities.py
/usr/lib/python2.7/site-packages/getmailcore/filters.pyc
/usr/lib/python2.7/site-packages/getmailcore/constants.pyc
/usr/lib/python2.7/site-packages/getmailcore/imap_utf7.pyc
/usr/lib/python2.7/site-packages/getmailcore/_retrieverbases.pyc
/usr/lib/python2.7/site-packages/getmailcore/baseclasses.py
/usr/share/doc/getmail-5.5
/usr/share/doc/getmail-5.5/TODO
/usr/share/doc/getmail-5.5/troubleshooting.txt
/usr/share/doc/getmail-5.5/documentation.txt
/usr/share/doc/getmail-5.5/faq.txt
/usr/share/doc/getmail-5.5/getmailrc-examples
/usr/share/doc/getmail-5.5/getmail.spec
/usr/share/doc/getmail-5.5/getmaildocs.css
/usr/share/doc/getmail-5.5/README
/usr/share/doc/getmail-5.5/troubleshooting.html
/usr/share/doc/getmail-5.5/COPYING
/usr/share/doc/getmail-5.5/BUGS
/usr/share/doc/getmail-5.5/configuration.txt
/usr/share/doc/getmail-5.5/faq.html
/usr/share/doc/getmail-5.5/CHANGELOG
/usr/share/doc/getmail-5.5/documentation.html
/usr/share/doc/getmail-5.5/configuration.html
/usr/share/doc/getmail-5.5/THANKS
/usr/share/man/man1/getmail_maildir.1
/usr/share/man/man1/getmail_mbox.1
/usr/share/man/man1/getmail.1
/usr/share/man/man1/getmail_fetch.1
/usr/bin/getmail_mbox
/usr/bin/getmail
/usr/bin/getmail_maildir
/usr/bin/getmail_fetch
#

That's listed, but it needs to be hashed now, else how could I verify none of these files has been modified some later time in the future? So:

# for i in $(cat /var/log/no-apt/getmail_5.5.files); do if [ ! -d "$i" ]; then sha256sum $i >> /var/log/no-apt/getmail_5.5.files.sum ; fi ; done

which ran quickly, it's a lightweight package. And I got (just so newbies may figure out more easily):

# cat /var/log/no-apt/getmail_5.5.files.sum
6b728dc21586d609a4ef3e4658166c8d345d1a8070d58992ae6c1103309a1d74  /usr/lib/python2.7/dist-packages/getmail-5.5-py2.7.egg-info
ed7fbfc1c821a7fbe59185f2a5330433b66d3695d2448b41aa0645c7111da72a  /usr/lib/python2.7/dist-packages/getmailcore/utilities.pyc
3f95f910f5f12a1f5274996545878f5c08ea030661b8a6eae06423dd6826aaca  /usr/lib/python2.7/dist-packages/getmailcore/_pop3ssl.pyc
bb1ed345b2e70984a15ba22d6d5981eff2644cb2775e3e89af29b779fa9e863a  /usr/lib/python2.7/dist-packages/getmailcore/compatibility.pyc
773609b22757160fa6359f83fb48c5a6440cb3b1ec2d8b98096c6f96cb9cdab5  /usr/lib/python2.7/dist-packages/getmailcore/__init__.pyc
f88c0b00c05797b46079539ec2ec00f27eb95a0f8997337079de2bafd0c48c91  /usr/lib/python2.7/dist-packages/getmailcore/compatibility.py
eb97d055cdeab22dd39a98b97f6e8c35729890caa0f07c7e573a7aa4c8e86f6d  /usr/lib/python2.7/dist-packages/getmailcore/_retrieverbases.py
0bee689ccfdc53650f792c186bad6b96f8338e8bb6215a8d81aa6b61935ce164  /usr/lib/python2.7/dist-packages/getmailcore/__init__.py
bee756ff99f16a1a98b5116226c3643dd548ecfbf11f92caec45b70e0f05a4f4  /usr/lib/python2.7/dist-packages/getmailcore/destinations.pyc
8d33306063e7c0edcd68a73008d46e4caa4eae3bdf1c56af2de033f96eabd490  /usr/lib/python2.7/dist-packages/getmailcore/filters.py
18458fe891179bc2473f0b815e1836153a98df0c3127ce56ba50da55c117f954  /usr/lib/python2.7/dist-packages/getmailcore/constants.py
1a7102e53fc25e45dc3436c3826fe46fb1e026833aea0cb90f318f111cf54114  /usr/lib/python2.7/dist-packages/getmailcore/imap_utf7.py
55ee9e9cd4b6649f0601afa4790330d7c0837751a0047689d6eef6cc0ef44cef  /usr/lib/python2.7/dist-packages/getmailcore/baseclasses.pyc
b3d4b421e681ffa854f657b2f6496b70b7162bd49df0e3baad88c5aab6adfc76  /usr/lib/python2.7/dist-packages/getmailcore/destinations.py
36e114c74d8a19270e11167e264424a25b3f64fc37783289fb1480a7210f685d  /usr/lib/python2.7/dist-packages/getmailcore/message.py
7eb3a5c0de1c6f004cdb379f49dd83b1927e9c76897603463cd0bb7d7fd5aceb  /usr/lib/python2.7/dist-packages/getmailcore/logging.py
13591983a425fa343e2c94a5b88ecb94d745d02e5d87c6d4aec38833c89c2332  /usr/lib/python2.7/dist-packages/getmailcore/logging.pyc
e0c6b69695163f23ea168add59a5157957302794be1d4658d85f760ebcc17940  /usr/lib/python2.7/dist-packages/getmailcore/exceptions.pyc
25a19e9442d6205f480d08e04cd9d7816dbf7cee078bf492753cac0fce663d72  /usr/lib/python2.7/dist-packages/getmailcore/message.pyc
743fa20982994ec534fc12a4e8c312803d4ff7ecbd230312dd8039792be1bbb1  /usr/lib/python2.7/dist-packages/getmailcore/retrievers.py
d857d799de71e1d79f77ccd3a850f92c3b9f4f07b277b2a9360dc8664bd323fc  /usr/lib/python2.7/dist-packages/getmailcore/retrievers.pyc
00a8ed17817adbaae109d2e701f7fe81ffb5f740671856b3085a521335b5770a  /usr/lib/python2.7/dist-packages/getmailcore/exceptions.py
4a46a4424cc1bd3c2c5869b47d65f20eb910c2f80f4ef019875d6859926fa14c  /usr/lib/python2.7/dist-packages/getmailcore/_pop3ssl.py
8b1946ab7e942b851210ad6c23deb9313ac0f97df307e15db6a2a96be2770bb6  /usr/lib/python2.7/dist-packages/getmailcore/utilities.py
e05482a7df48437b39e58a1276f3ba57ec7b43b73b0cc150de792f58c52e5282  /usr/lib/python2.7/dist-packages/getmailcore/filters.pyc
a7ed48ee5c5bc86ded2b91524f19b0b15e9a592534bc6e7ad3d5334e55a5dda0  /usr/lib/python2.7/dist-packages/getmailcore/constants.pyc
f5551a556622ec38900c9822c9232cd75f72ef06284e64baca44926aeeb347cb  /usr/lib/python2.7/dist-packages/getmailcore/imap_utf7.pyc
e2eeebcd935696219891bcdb8fac77884cd11429dc598c8531c14ce49f622ed9  /usr/lib/python2.7/dist-packages/getmailcore/_retrieverbases.pyc
523307adad71ccec9c90c51c552ab52539498605a9c47a6156421a5de13db8c3  /usr/lib/python2.7/dist-packages/getmailcore/baseclasses.py
6b728dc21586d609a4ef3e4658166c8d345d1a8070d58992ae6c1103309a1d74  /usr/lib/python2.7/site-packages/getmail-5.5-py2.7.egg-info
ed7fbfc1c821a7fbe59185f2a5330433b66d3695d2448b41aa0645c7111da72a  /usr/lib/python2.7/site-packages/getmailcore/utilities.pyc
3f95f910f5f12a1f5274996545878f5c08ea030661b8a6eae06423dd6826aaca  /usr/lib/python2.7/site-packages/getmailcore/_pop3ssl.pyc
bb1ed345b2e70984a15ba22d6d5981eff2644cb2775e3e89af29b779fa9e863a  /usr/lib/python2.7/site-packages/getmailcore/compatibility.pyc
773609b22757160fa6359f83fb48c5a6440cb3b1ec2d8b98096c6f96cb9cdab5  /usr/lib/python2.7/site-packages/getmailcore/__init__.pyc
f88c0b00c05797b46079539ec2ec00f27eb95a0f8997337079de2bafd0c48c91  /usr/lib/python2.7/site-packages/getmailcore/compatibility.py
eb97d055cdeab22dd39a98b97f6e8c35729890caa0f07c7e573a7aa4c8e86f6d  /usr/lib/python2.7/site-packages/getmailcore/_retrieverbases.py
0bee689ccfdc53650f792c186bad6b96f8338e8bb6215a8d81aa6b61935ce164  /usr/lib/python2.7/site-packages/getmailcore/__init__.py
bee756ff99f16a1a98b5116226c3643dd548ecfbf11f92caec45b70e0f05a4f4  /usr/lib/python2.7/site-packages/getmailcore/destinations.pyc
8d33306063e7c0edcd68a73008d46e4caa4eae3bdf1c56af2de033f96eabd490  /usr/lib/python2.7/site-packages/getmailcore/filters.py
18458fe891179bc2473f0b815e1836153a98df0c3127ce56ba50da55c117f954  /usr/lib/python2.7/site-packages/getmailcore/constants.py
1a7102e53fc25e45dc3436c3826fe46fb1e026833aea0cb90f318f111cf54114  /usr/lib/python2.7/site-packages/getmailcore/imap_utf7.py
55ee9e9cd4b6649f0601afa4790330d7c0837751a0047689d6eef6cc0ef44cef  /usr/lib/python2.7/site-packages/getmailcore/baseclasses.pyc
b3d4b421e681ffa854f657b2f6496b70b7162bd49df0e3baad88c5aab6adfc76  /usr/lib/python2.7/site-packages/getmailcore/destinations.py
36e114c74d8a19270e11167e264424a25b3f64fc37783289fb1480a7210f685d  /usr/lib/python2.7/site-packages/getmailcore/message.py
7eb3a5c0de1c6f004cdb379f49dd83b1927e9c76897603463cd0bb7d7fd5aceb  /usr/lib/python2.7/site-packages/getmailcore/logging.py
13591983a425fa343e2c94a5b88ecb94d745d02e5d87c6d4aec38833c89c2332  /usr/lib/python2.7/site-packages/getmailcore/logging.pyc
e0c6b69695163f23ea168add59a5157957302794be1d4658d85f760ebcc17940  /usr/lib/python2.7/site-packages/getmailcore/exceptions.pyc
25a19e9442d6205f480d08e04cd9d7816dbf7cee078bf492753cac0fce663d72  /usr/lib/python2.7/site-packages/getmailcore/message.pyc
743fa20982994ec534fc12a4e8c312803d4ff7ecbd230312dd8039792be1bbb1  /usr/lib/python2.7/site-packages/getmailcore/retrievers.py
d857d799de71e1d79f77ccd3a850f92c3b9f4f07b277b2a9360dc8664bd323fc  /usr/lib/python2.7/site-packages/getmailcore/retrievers.pyc
00a8ed17817adbaae109d2e701f7fe81ffb5f740671856b3085a521335b5770a  /usr/lib/python2.7/site-packages/getmailcore/exceptions.py
4a46a4424cc1bd3c2c5869b47d65f20eb910c2f80f4ef019875d6859926fa14c  /usr/lib/python2.7/site-packages/getmailcore/_pop3ssl.py
8b1946ab7e942b851210ad6c23deb9313ac0f97df307e15db6a2a96be2770bb6  /usr/lib/python2.7/site-packages/getmailcore/utilities.py
e05482a7df48437b39e58a1276f3ba57ec7b43b73b0cc150de792f58c52e5282  /usr/lib/python2.7/site-packages/getmailcore/filters.pyc
a7ed48ee5c5bc86ded2b91524f19b0b15e9a592534bc6e7ad3d5334e55a5dda0  /usr/lib/python2.7/site-packages/getmailcore/constants.pyc
f5551a556622ec38900c9822c9232cd75f72ef06284e64baca44926aeeb347cb  /usr/lib/python2.7/site-packages/getmailcore/imap_utf7.pyc
e2eeebcd935696219891bcdb8fac77884cd11429dc598c8531c14ce49f622ed9  /usr/lib/python2.7/site-packages/getmailcore/_retrieverbases.pyc
523307adad71ccec9c90c51c552ab52539498605a9c47a6156421a5de13db8c3  /usr/lib/python2.7/site-packages/getmailcore/baseclasses.py
f1595f78375b79eac7f6f5d36b2adaa972bf5d3f10d1785ac31b699e6c73b62f  /usr/share/doc/getmail-5.5/TODO
cd1e837c0ad6b038626050c8113007b02240ac4e728754a84f97e2a12bc531e9  /usr/share/doc/getmail-5.5/troubleshooting.txt
618710632ae777b298fdd96c970d76f84747d1e1532b6c7dfc7aa2c3d606b27a  /usr/share/doc/getmail-5.5/documentation.txt
25e4b376d0e3a489363d805ef35367021a4050fd3eaa150a0da40e68e2805d8b  /usr/share/doc/getmail-5.5/faq.txt
953faed07d2fa34807ab1c2558fcf48d4d1c67d4424565c6c103fa7dd57c4062  /usr/share/doc/getmail-5.5/getmailrc-examples
8844130f888a50a900a94fdda9236a83c686890f873922c678677e0c995dd588  /usr/share/doc/getmail-5.5/getmail.spec
13af6c26edd192237802d715393c8adcaf1f4339676237eaccdbcd04cd912b78  /usr/share/doc/getmail-5.5/getmaildocs.css
76a4a6a0305751e5f5be1c63904172e873cb41d53637cdc3336117fda4f0ba39  /usr/share/doc/getmail-5.5/README
4a784d2cd73f1424a76fe1d605d81da25ea9861cf2c0b9391b2b0954957a887e  /usr/share/doc/getmail-5.5/troubleshooting.html
8177f97513213526df2cf6184d8ff986c675afb514d4e68a404010521b880643  /usr/share/doc/getmail-5.5/COPYING
935f5a8907a8480562fc93e5237aefab7c3816463bf8cab3a06a39f143d29291  /usr/share/doc/getmail-5.5/BUGS
53018c17d00509873e835a9bb5c23bf47ff413cc9716613d97d4f353113e8049  /usr/share/doc/getmail-5.5/configuration.txt
c2d22573a3d8fc82c5e2da43d3276cee7b7195739f3987fd001753e9a9cac175  /usr/share/doc/getmail-5.5/faq.html
cca40b8fc5a9c8b4590530c1c471090e043bd728d8ed06709118bcf344111459  /usr/share/doc/getmail-5.5/CHANGELOG
ef1976feba848fca26d97a6a6006dd4b0125adf700c31ca141af561567ebd4da  /usr/share/doc/getmail-5.5/documentation.html
40e2094618b1f58e9e81cf3efc6672fc7c6bf86f4415c980cae642349f3b04c8  /usr/share/doc/getmail-5.5/configuration.html
d0b26fd248b4e8ae6822d6ec2cc44d9dd0584dc49eb2b4325051fd540efc2bf3  /usr/share/doc/getmail-5.5/THANKS
548ca9289d4ce0c979e8e0dde4e85bb5a97e5d298d75556b3a20891112b25411  /usr/share/man/man1/getmail_maildir.1
29da736bad948252537f4520f0624fd90be5cdf9e65807430b70f572a219a827  /usr/share/man/man1/getmail_mbox.1
7ec7bf2c06cd04990261797141e685238d1a43e7ed026c0eaddcda84c8e21e65  /usr/share/man/man1/getmail.1
ebed55848082f53bd2f48d5d204e6c9b54d934a66715b1b78d79cc6ec642ffe6  /usr/share/man/man1/getmail_fetch.1
6b20428151eee3c4661fabb8acdafd615c0dcd7b9c0ff06336aaa4b99799af79  /usr/bin/getmail_mbox
04cfb870dbf73217c71e8746a2c36233c673a68eaa8635056074e1d2bfa0af98  /usr/bin/getmail
977a97233b042c74d7dcae25585d1638616934b0250d6226463ff4ceb5408265  /usr/bin/getmail_maildir
c351e9fc1f6a632c2482ff5dbd44d4a6e4707d5eda1ad9a8995147f23d11cd94  /usr/bin/getmail_fetch

which, again, is pertaining to my install only.

It you count the lines, all should correspond, barring these four dirs:

# for i in $(cat /var/log/no-apt/getmail_5.5.files); do if [ -d "$i" ]; then ls -ld $i  ; fi ; done 
drwxr-xr-x 2 root root 4096 2017-12-21 17:12 /usr/lib/python2.7/dist-packages/getmailcore
drwxr-xr-x 3 root root 4096 2017-12-21 17:12 /usr/lib/python2.7/site-packages
drwxr-xr-x 2 root root 4096 2017-12-21 17:12 /usr/lib/python2.7/site-packages/getmailcore
drwxr-xr-x 2 root root 4096 2017-12-21 17:12 /usr/share/doc/getmail-5.5
#

the rest are files. So the  /var/log/no-apt/getmail_5.5.files should have 4 lines more than /var/log/no-apt/getmail_5.5.files.sum. Is that so:

# wc -l /var/log/no-apt/getmail_5.5.files*
   87 /var/log/no-apt/getmail_5.5.files
   83 /var/log/no-apt/getmail_5.5.files.sum
  170 total
#

Yes it is... And more, but the point has been done.

And only now I can try and use getmail... In the next post I'll report, or just give the link to my email to Getmail ML.

#16 Re: Installation » Keeping track of no-apt installs (installing out-of Devuan PM) » 2017-12-21 16:23:59

Getmail now. Ah, I wrote wrong, in this post is first the apt-get remove'al of the install (old-version) Getmail.

First the uninstall. Of course, get the find's listing first. Unlike what I gave in the previous posts, seconds are better be there in the date timestamp. So run:

# find / -xdev -name '*' > FIND_$(date +%y%m%d_%H%M%S)

previous first. Then run:

# apt-get remove getmail4 |& tee /some/log/apt-get_remove_getmail4_$(date +%y%m%d_%H%M%S)
#

then run the

# find / -xdev -name '*' > FIND_$(date +%y%m%d_%H%M%S)

again. This diff of the two find's run:

# diff FIND_171221_155140  FIND_171221_155232
11548a11549
> /home/mr/LOG_/apt-get_remove_getmail4_171221_155156_gdOv
11676a11678
> /home/mr/FIND_171221_1552
90974d90975
< /usr/lib/python2.7/dist-packages/getmail-4.54.0.egg-info
92211,92239d92211
< /usr/lib/python2.7/dist-packages/getmailcore
< /usr/lib/python2.7/dist-packages/getmailcore/utilities.pyc
< /usr/lib/python2.7/dist-packages/getmailcore/_pop3ssl.pyc
< /usr/lib/python2.7/dist-packages/getmailcore/compatibility.pyc
< /usr/lib/python2.7/dist-packages/getmailcore/__init__.pyc
< /usr/lib/python2.7/dist-packages/getmailcore/compatibility.py
< /usr/lib/python2.7/dist-packages/getmailcore/_retrieverbases.py
< /usr/lib/python2.7/dist-packages/getmailcore/__init__.py
< /usr/lib/python2.7/dist-packages/getmailcore/destinations.pyc
< /usr/lib/python2.7/dist-packages/getmailcore/filters.py
< /usr/lib/python2.7/dist-packages/getmailcore/constants.py
< /usr/lib/python2.7/dist-packages/getmailcore/imap_utf7.py
< /usr/lib/python2.7/dist-packages/getmailcore/baseclasses.pyc
< /usr/lib/python2.7/dist-packages/getmailcore/destinations.py
< /usr/lib/python2.7/dist-packages/getmailcore/message.py
< /usr/lib/python2.7/dist-packages/getmailcore/logging.py
< /usr/lib/python2.7/dist-packages/getmailcore/logging.pyc
< /usr/lib/python2.7/dist-packages/getmailcore/exceptions.pyc
< /usr/lib/python2.7/dist-packages/getmailcore/message.pyc
< /usr/lib/python2.7/dist-packages/getmailcore/retrievers.py
< /usr/lib/python2.7/dist-packages/getmailcore/retrievers.pyc
< /usr/lib/python2.7/dist-packages/getmailcore/exceptions.py
< /usr/lib/python2.7/dist-packages/getmailcore/_pop3ssl.py
< /usr/lib/python2.7/dist-packages/getmailcore/utilities.py
< /usr/lib/python2.7/dist-packages/getmailcore/filters.pyc
< /usr/lib/python2.7/dist-packages/getmailcore/constants.pyc
< /usr/lib/python2.7/dist-packages/getmailcore/imap_utf7.pyc
< /usr/lib/python2.7/dist-packages/getmailcore/_retrieverbases.pyc
< /usr/lib/python2.7/dist-packages/getmailcore/baseclasses.py
147762,147780d147733
< /usr/share/doc/getmail4
< /usr/share/doc/getmail4/TODO
< /usr/share/doc/getmail4/getmaildocs.css
< /usr/share/doc/getmail4/README
< /usr/share/doc/getmail4/troubleshooting.html
< /usr/share/doc/getmail4/BUGS
< /usr/share/doc/getmail4/faq.html
< /usr/share/doc/getmail4/copyright
< /usr/share/doc/getmail4/configuration.txt.gz
< /usr/share/doc/getmail4/documentation.html
< /usr/share/doc/getmail4/getmailrc-examples.gz
< /usr/share/doc/getmail4/README.Debian
< /usr/share/doc/getmail4/configuration.html
< /usr/share/doc/getmail4/documentation.txt.gz
< /usr/share/doc/getmail4/THANKS
< /usr/share/doc/getmail4/changelog.gz
< /usr/share/doc/getmail4/faq.txt.gz
< /usr/share/doc/getmail4/changelog.Debian.gz
< /usr/share/doc/getmail4/troubleshooting.txt.gz
163682d163634
< /usr/share/man/man1/getmail_fetch.1.gz
163998d163949
< /usr/share/man/man1/getmail_mbox.1.gz
164768d164718
< /usr/share/man/man1/getmails.1.gz
165490d165439
< /usr/share/man/man1/getmail.1.gz
165567d165515
< /usr/share/man/man1/getmail_maildir.1.gz
171842d171789
< /usr/share/doc-base/getmail4
189200d189146
< /usr/bin/getmail_mbox
189230d189175
< /usr/bin/getmail
189528d189472
< /usr/bin/getmail_maildir
189792d189735
< /usr/bin/getmails
189875d189817
< /usr/bin/getmail_fetch
203573d203514
< /var/lib/dpkg/info/getmail4.list
205146d205086
< /var/lib/dpkg/info/getmail4.prerm
206826d206765
< /var/lib/dpkg/info/getmail4.postinst
208414d208352
< /var/lib/dpkg/info/getmail4.md5sums
#

has all the changes, but I'll stow it in:

# diff FIND_171221_155140  FIND_171221_155232  | grep '< ' | sed 's/< //' >> /var/log/no-apt/getmail_4.53.0-2_REMOVED.files
#

without those line numbers and without < of the previous listing of now noexistent files of the old getmail in the system.

I've stowed that listing in that /var/log/no-apt (that I had previously created when I had installed gradm):

# cat /var/log/no-apt/getmail_4.53.0-2_REMOVED.files
/usr/lib/python2.7/dist-packages/getmail-4.54.0.egg-info
/usr/lib/python2.7/dist-packages/getmailcore
/usr/lib/python2.7/dist-packages/getmailcore/utilities.pyc
/usr/lib/python2.7/dist-packages/getmailcore/_pop3ssl.pyc
/usr/lib/python2.7/dist-packages/getmailcore/compatibility.pyc
/usr/lib/python2.7/dist-packages/getmailcore/__init__.pyc
/usr/lib/python2.7/dist-packages/getmailcore/compatibility.py
/usr/lib/python2.7/dist-packages/getmailcore/_retrieverbases.py
/usr/lib/python2.7/dist-packages/getmailcore/__init__.py
/usr/lib/python2.7/dist-packages/getmailcore/destinations.pyc
/usr/lib/python2.7/dist-packages/getmailcore/filters.py
/usr/lib/python2.7/dist-packages/getmailcore/constants.py
/usr/lib/python2.7/dist-packages/getmailcore/imap_utf7.py
/usr/lib/python2.7/dist-packages/getmailcore/baseclasses.pyc
/usr/lib/python2.7/dist-packages/getmailcore/destinations.py
/usr/lib/python2.7/dist-packages/getmailcore/message.py
/usr/lib/python2.7/dist-packages/getmailcore/logging.py
/usr/lib/python2.7/dist-packages/getmailcore/logging.pyc
/usr/lib/python2.7/dist-packages/getmailcore/exceptions.pyc
/usr/lib/python2.7/dist-packages/getmailcore/message.pyc
/usr/lib/python2.7/dist-packages/getmailcore/retrievers.py
/usr/lib/python2.7/dist-packages/getmailcore/retrievers.pyc
/usr/lib/python2.7/dist-packages/getmailcore/exceptions.py
/usr/lib/python2.7/dist-packages/getmailcore/_pop3ssl.py
/usr/lib/python2.7/dist-packages/getmailcore/utilities.py
/usr/lib/python2.7/dist-packages/getmailcore/filters.pyc
/usr/lib/python2.7/dist-packages/getmailcore/constants.pyc
/usr/lib/python2.7/dist-packages/getmailcore/imap_utf7.pyc
/usr/lib/python2.7/dist-packages/getmailcore/_retrieverbases.pyc
/usr/lib/python2.7/dist-packages/getmailcore/baseclasses.py
/usr/share/doc/getmail4
/usr/share/doc/getmail4/TODO
/usr/share/doc/getmail4/getmaildocs.css
/usr/share/doc/getmail4/README
/usr/share/doc/getmail4/troubleshooting.html
/usr/share/doc/getmail4/BUGS
/usr/share/doc/getmail4/faq.html
/usr/share/doc/getmail4/copyright
/usr/share/doc/getmail4/configuration.txt.gz
/usr/share/doc/getmail4/documentation.html
/usr/share/doc/getmail4/getmailrc-examples.gz
/usr/share/doc/getmail4/README.Debian
/usr/share/doc/getmail4/configuration.html
/usr/share/doc/getmail4/documentation.txt.gz
/usr/share/doc/getmail4/THANKS
/usr/share/doc/getmail4/changelog.gz
/usr/share/doc/getmail4/faq.txt.gz
/usr/share/doc/getmail4/changelog.Debian.gz
/usr/share/doc/getmail4/troubleshooting.txt.gz
/usr/share/man/man1/getmail_fetch.1.gz
/usr/share/man/man1/getmail_mbox.1.gz
/usr/share/man/man1/getmails.1.gz
/usr/share/man/man1/getmail.1.gz
/usr/share/man/man1/getmail_maildir.1.gz
/usr/share/doc-base/getmail4
/usr/bin/getmail_mbox
/usr/bin/getmail
/usr/bin/getmail_maildir
/usr/bin/getmails
/usr/bin/getmail_fetch
/var/lib/dpkg/info/getmail4.list
/var/lib/dpkg/info/getmail4.prerm
/var/lib/dpkg/info/getmail4.postinst
/var/lib/dpkg/info/getmail4.md5sums
#

to have it for troubleshooting in case something would still go wrong. Which I don't expect, but don't know.

We'll see, in the next post, when I install the latest Getmail.

#17 Re: Installation » Keeping track of no-apt installs (installing out-of Devuan PM) » 2017-12-21 15:41:53

As I promised (or warned you; mind my verbosity... but I believe you can view it as being systematic, if you wink an eye wink ) a quick example of a deployed no-apt install.

I installed (it's still the latest at this time):  gradm-e9045c0.tar.gz which I got from https://cvsweb.grsecurity.net/ (which btw way, can be git clone'd, read "Git Checkout" at: https://grsecurity.net/cvs.php, and I installed it, basically, following the README:

$ cat gradm-e9045c0/README 
To install gradm with PAM support for special roles:

make
make install

To install gradm without PAM support:

make nopam
make install
$

Basically, because if I ran those make, make install commands, I would have to engage my future knowledge of forensic which I don't yet possess (joking: I may never reach such competence) to know exactly which files have been installed where after I ran the (if I ran it just so quickly) ill-fated make install.

With all due respect to the quick and easy make and make install (and their friends such as ./configure and others, depending on the package), I want to know where those install, and I want to be able to check their state. I'm not that advanced to check their state as well as Tripwire can check it, but a simple SHA256 sum of each file will do.

And so I had, previous to running the (following this method, it will not anymore be ill-fated) make install, I ran:

# find / -xdev -name '*' > FIND_$(date +%y%m%d_%H%M%S)

that gets you a huge listing of all files under / excluding, thanks to the -xdev flag, anything that's mounted on /, even /proc and /sys, and /run and likely more are excluded, as they should be.

Then I ran (now not to be ill-fated, and you're soon to see why) make install, and then, after having run it, I run the:

# find / -xdev -name '*' > FIND_$(date +%y%m%d_%H%M%S)

And simply diffing the FIND_xxx previous to make install with the FIND_xxx after it, I know exactly which files got installed. Details will follow, but for the latest Getmail package.

There's one caveat. If there existed a file with the same path and same name as the file that your make install installed, that file won't be in the diff...

Meaning, now that I have to (kind of) test this method with installing the latest Getmail, I'd say I am advised, and strongly, by the fact that some files would out of doubt end up not being in the diff, if I do not uninstall my currently installed instance of Getmail.

But before I start with Getmail, here's what I got with the diffing those for Gradm:

# cat /var/log/no-apt/gradm_171122_01.files
/sbin/gradm_pam
/sbin/grlearn
/sbin/gradm
/etc/udev/rules.d/80-grsec.rules
/etc/grsec/pw
/etc/grsec/learn_config
/etc/grsec/policy
/usr/share/man/man8/gradm.8
#

(DIGRESSION START because Gradm is a marvellous package done by a programmer of matchless skills... There's hardly anybody who understands Linux kernel, often so much better than Linus himself, than spender, esp. with regard to security... It's such sad news that we lost spender and PaX Team for FOSS, because of Goog the Schmoogle's ripoff of their code... Read and understand the link that's in all of my Debian Forum's posts --it was the same, or similar signature in every Gentoo Forums posts after the date that I applied it, but alas some people behave fascistically and had erased it... only my NGO's link is still there now... Read and understand the old Not-Invented-Here Linus' behavior when spender long time ago offered to help fix the kernel at: http://www.crmbuyer.com/story/39565.html ... And find more by following the links in my signiture here on Dev1Galaxy for more. DIGRESSION END)

And I also took:

# cat /var/log/no-apt/gradm_171122_01.files.sum 
618c6cf706b32eeda088e21285711e4826a0ee23f11dee9a371adc599c73ed58  /sbin/gradm_pam
988211e1505f9c1a021671dffa4eec4fcd46d74910b8c8048f902949284a03bd  /sbin/grlearn
8c541940aade2c2e454a2b1e542d8091d03d8fc208ff82b1694ab2cd5fde9d38  /sbin/gradm
a165ebda31ec3eca32aa8b06ab435df72be6ebaa2fc760ca89c83050ce9bcf37  /etc/udev/rules.d/80-grsec.rules
695fea6e88d577dd885fcb5a2c0a9c565b45d438716c7ff58b58b11ee67f31d3  /etc/grsec/pw
7cb517f3286078f1ed4ad8585b2a7222c79fe86230876990f554e48e66644959  /etc/grsec/learn_config
154924d3cb9c0e16821e45f77d02b2e7d26998ba76208903476534a639886c3b  /etc/grsec/policy
29e98a09b3de3eb36d57b1d9aa02c0645c453400d4867e54df85031ccd2bd3c4  /usr/share/man/man8/gradm.8
#

(which are unique to my system, just if some newbie is following here)
And these verify correctly:

# sha256sum -c /var/log/no-apt/gradm_171122_01.files.sum 
/sbin/gradm_pam: OK
/sbin/grlearn: OK
/sbin/gradm: OK
/etc/udev/rules.d/80-grsec.rules: OK
/etc/grsec/pw: OK
/etc/grsec/learn_config: OK
/etc/grsec/policy: FAILED
/usr/share/man/man8/gradm.8: OK
sha256sum: WARNING: 1 computed checksum did NOT match
#

The /etc/grsec/policy is something you build as you use it. This means all that is not supposed to have changed is as when I installed that package.

In the next post, the no-apt installation of Getmail.

#18 Installation » Keeping track of no-apt installs (installing out-of Devuan PM) » 2017-12-21 14:32:21

miroR
Replies: 5

title (currently): Keeping track of no-apt installs (installing out-of Devuan package management)
---
PREEMPTIVE: Before jumping to give me advice how only modifying packages in the Devuan/Debian way is the sole way to go, pls. read at least the lines in the very bottom of this post.

From:

Debian Reference
                             Osamu Aoki

Copyright © 2013 Osamu Aoki

the file in your Devuan machine (of course in Debian and other derivatives of Debian as well), being:
/usr/share/debian-reference/debian-reference.en.txt.gz, if you have:

# apt-file list debian-reference-en
debian-reference-en: /usr/share/debian-reference/apa.en.html
debian-reference-en: /usr/share/debian-reference/ch01.en.html
debian-reference-en: /usr/share/debian-reference/ch02.en.html
debian-reference-en: /usr/share/debian-reference/ch03.en.html
debian-reference-en: /usr/share/debian-reference/ch04.en.html
debian-reference-en: /usr/share/debian-reference/ch05.en.html
debian-reference-en: /usr/share/debian-reference/ch06.en.html
debian-reference-en: /usr/share/debian-reference/ch07.en.html
debian-reference-en: /usr/share/debian-reference/ch08.en.html
debian-reference-en: /usr/share/debian-reference/ch09.en.html
debian-reference-en: /usr/share/debian-reference/ch10.en.html
debian-reference-en: /usr/share/debian-reference/ch11.en.html
debian-reference-en: /usr/share/debian-reference/ch12.en.html
debian-reference-en: /usr/share/debian-reference/debian-reference.en.epub
debian-reference-en: /usr/share/debian-reference/debian-reference.en.pdf
debian-reference-en: /usr/share/debian-reference/debian-reference.en.txt.gz
debian-reference-en: /usr/share/debian-reference/index.en.html
debian-reference-en: /usr/share/debian-reference/pr01.en.html
debian-reference-en: /usr/share/doc-base/debian-reference-en
debian-reference-en: /usr/share/doc/debian-reference-en/README
debian-reference-en: /usr/share/doc/debian-reference-en/changelog.gz
debian-reference-en: /usr/share/doc/debian-reference-en/copyright
debian-reference-en: /usr/share/doc/debian-reference-en/docs
#

... if you have debian-reference-en installed (probably installs with apt-get install debian-reference).

    This Debian Reference (v2) (2017-09-18 15:42:22 UTC) is intended
    to provide a broad overview of the Debian system as a
...

It's in my Ceres Devuan system, to which it perfectly applies. Devuan is still just
a corrected version of Debian (systemDestruction free smile, I just have to express
my joy for my init-freedom, if any of the Debianers/Ubuntuers are reading. I
couldn't live with that ugly beheemoth like you do, and here we've been given
our Unix back. And added to that, as a perfect shiny cherry on top, cherry colored nicely almost like the
Devuan themes, I can have a fully functioning sans-dbus system. I followed:
https://git.devuan.org/dev1fanboy/Upgra … tall-guide
https://git.devuan.org/dev1fanboy/Upgra … minimalism
https://git.devuan.org/dev1fanboy/Upgra … thout-dbus
,
and I gave the (kind of) my system history of how I did it at:

sans-dbus, Questions, Tips and Tricks on its Implementation
https://dev1galaxy.org/viewtopic.php?id=761
(where find, esp. in today's post of mine:
https://dev1galaxy.org/viewtopic.php?id=761#p6831 what (currently) might be missing from dev1fanboy's wiki (and I've just notified him of it by a PM having found him on this Forum).

which I'm afraid is not available easily in any other GNU/Linux distro. Very
satisfying. Best, to my taste!

But let's cite some more from Osamu Aoki's book.

2. Debian package management

...

2.1. Debian package management prerequisites

...

2.1.2. Basic precautions

    Warning

Read this:

    Do not install packages from random mixture of suites. It
    probably breaks the package consistency which requires deep
    system management knowledge, such as compiler ABI, library
    version, interpreter features, etc.

Oops! Scary, ain't it... things that breakbpackage consistency and which require deep system management knowledge. That means knowledge about how dpkg and apt-get work.

I always like better command line tools, but you may like better aptitude or real GUI tools, not me.

I can claim I've figured those enough to (kind of) develop for me (and if anybody else wants to follow) the Air-Gap installing method for Devuan (sure would work for other Debian derivatives) that has, actually, recently saved my butt big time! Look up all the crashes in:

https://github.com/minipli/linux-unoffi … sec/issues
starting from
#13, and than all the way to #17, #18, #19, #20, #21.

Those crashes were a very bad nuissance, but thanks to my Air-Gap building and cloning the system for online use:
(
Air-Gapped Devuan Install, Tentative
https://dev1galaxy.org/viewtopic.php?id=746
)
, every time my system in the cloned-for-online machine was freshly cloned, the very bad nuissance would be vanishing, and peace and calm from the Air-Gapped was back!

I'm not saying the attack --because I'm sure that's what it is, nothing else explains it but that, and indications are galore to that-- can't be back, but unless the attacker would terribly apply, in the pretty costly manner: probably too expensive for even bigger subjects --and I hope those really big who could easily bear the expenditure, bringing that here because since we are speaking of intrusional control of people's machines I want to paint an integral picture, [I hope] they do not have me in their sights--, [but unless the attacker --given that he not be of the rare and really huge ones who could do it more easily-- but unless the attacker would terribly apply], the system won't get b0rked, not my Air-Gapped system, and consequently I'll always be able to clone it...

Ah, btw my systems are full disk encrypted:
Installing to existing partitions/mount? Full disk encrypt? Feedback.
https://dev1galaxy.org/viewtopic.php?id=559
.

Back to Osamu Aoki's book. So, not to break the package consistency of your system, you need to possess (if you want to do some kind of testing/experimenting/debugging with your system by installing programs from unstable/other/what-not sources):

    system management knowledge, such as compiler ABI, library
    version, interpreter features, etc.

Library version is what I usually figure out still only intuitively, because our developers put enought information where needed so users like me find the info upon installing the software they provided for us. Interpreter features, that's Bash/Dash/Zsh, Perl, Python and stuff... Applies same: intuitively I can manage those correctly thanks to devs having provided info where due.

I'm making a complete introduction, so I'll leave this:

    The newbie Debian system administrator should stay with the 
    stable release of Debian while applying only security updates. I
    mean that some of the following valid actions are better avoided,
    as a precaution, until you understand the Debian system very
    well. Here are some reminders.

for any occasionly hard learning and fast apprehending newbies if they are visiting here.

Oops! Scary, ain't it:

      * Do not include testing or unstable in "/etc/apt/
        sources.list".

      * Do not mix standard Debian with other non-Debian archives
        such as Ubuntu in "/etc/apt/sources.list".

Of course, we, Devuaners translate this to do not mix standard Devuan with other non-Devuan archives. My /etc/apt/sources.list is, of course, all set up for Devuan Ceres, by the way...

      * Do not create "/etc/apt/preferences".

Nope! Of course I did create one. Similar like suggested by dev1fanboy in his guide (already linked above)
https://git.devuan.org/dev1fanboy/Upgra … tall-guide
(and other links from there) to get me a well-functioning sans-dbus system.

      * Do not change default behavior of package management tools
        through configuration files without knowing their full
        impacts.

And this:   

      * Do not install random packages by "dpkg -i <random_package>".

of course I do! And occasionally get others to do it smile :

Grsecurity/Pax installation on Devuan GNU/Linux
https://dev1galaxy.org/viewtopic.php?id=596
(where find the links to grsecunoff deb packages that I often provide).

But I haven't yet had any situation so bad that I needed to do either of the following:

      * Do not ever install random packages by "dpkg --force-all -i
        <random_package>".

      * Do not erase or alter files in "/var/lib/dpkg/".

Not yet, and it's good that I haven't.

Bu I'm providing all this introduction to make another research. I have done other researches as much less advanced user that I am now (mostly in Gentoo, in the past years).

And my years old request to get a sans-dbus option for Devuan users was met with (eventually) very kind and helpful response from Devuan leaders, to whom I have to thank again here for that option: that option continues to be fully viable in Devuan!

This is another (advanced-user level, but newbie-friendy) research, which I actually follow on my own footsteps in Gentoo (WARNING: the title is misleading as far as my contribution there, it's about installing outside Package Management System):
Need help creating ebuild for "lurker"
https://forums.gentoo.org/viewtopic-t-228582.html

So, finally, here's what the (the first few of the) next posts will be (mostly) about:

Re: Getmail and Maildrop tricked into delivering truncated emails
https://marc.info/?l=getmail&m=151328826313606&w=2

where find:

Charles Cazabon wrote:

Installing getmail from source is *very* easy.  It's not like building
LibreOffice or vlc or something wink

Mostly, because I'll also look back at another instance of out-of-devuan-pms, or no-apt (for short) install already in full swing in my system, first.

Well, yes, it is. It is easy... However, bearing in mind what cleverer people than me wrote about how to keep your system consistent... it is also not so very easy. I don't want my system to get files that it does not know about (meaning which DPKG and APT don't know about) without some sort of manual keeping track of those files, and of their consistent state...

I don't have two or three days to get familiar with the Package Management from zero onwards, which would be the best path to follow. If I were at that level, I'd be helping out maintaining a package here and there, but I'm not...

And, having been sick and unable to work which created a delay of some two days, I also can't keep the devs at Getmail waiting, who have been kind to start investigating my problem (although I'm pretty confident by the indications that I posted to the list that it was an attack; just go back from the link I gave you and aquaint yourself with my reasoning and my arguments on the case; and that it was an attack that is unlikely to repeat in any predictable fashion)...

Now, if anybody would have like to say: No! Go the Package Management way, the only way... Would be true only if whoever says so is quick enough to give me the tips how to do it in as little time (excluding this lengthy introduction) as I can do it in the (not yet written) next posts? Those devs are waiting for my reply...

#19 Re: Installation » sans-dbus, Questions, Tips and Tricks on its Implementation » 2017-12-21 13:41:48

I'll give here, as I promised in my EDIT of today in the first post, what I believe is necessary (a query too about it will follow afterwards).

Some of these are needed, and I wasn't able to find /etc/apt/preferences.d/avoid-systemd in dev1fanboy's wiki, even though I had, months ago now, picked it from there, to my best recollection:

# ls -ABRgo /etc/apt/preferences*
-rw-r--r-- 1  262 2017-12-01 14:30 /etc/apt/preferences

/etc/apt/preferences.d:
total 4
-rw-r--r-- 1 62 2015-04-20 22:25 avoid-systemd

So:

# cat /etc/apt/preferences
Package: *dbus*
Pin: origin ""
Pin-Priority: -1

Package: *consolekit*
Pin: origin ""
Pin-Priority: -1

Package: *policykit*
Pin: origin ""
Pin-Priority: -1

Package: *pulse*
Pin: origin ""
Pin-Priority: -1

Package: *pulseaudio*
Pin: origin ""
Pin-Priority: -1
#

and:

# cat /etc/apt/preferences.d/avoid-systemd 
Package: systemd-sysv
Pin: release o=Debian
Pin-Priority: -1
#

Now the query. Is it better I stick:

# cat > /etc/apt/preferences.d/avoid-systemd
Package: systemd
Pin: release o=Debian
Pin-Priority: -1 

Package: systemd
Pin: release *
Pin-Priority: -1
#

or should what I already have in place be fine? Anybody, what's your take?

That we call it no-systemd or avoid-systemd is irrelevant, just whether:

Package: systemd-sysv

gets the same effect on the system as:

Package: systemd

in the two included variants fro the new script?

BTW, I don't have issues. My Ceres is not plagued by either systemd or dbus.

(Nor pulseaudio either. And my audio is functioning well, in PaleMoon, FFmpeg, MPlayer, Mencoder, Mpv, Vlc...)

Regards!

#21 Re: Documentation » Grsecurity/Pax installation on Devuan GNU/Linux » 2017-12-10 01:56:04

I've decided to offer packages that, according to the latest realization --but that may change, therefore the warning in the download page--:

NULL pointer deref in do_blockdev_direct_IO()
https://github.com/minipli/linux-unoffi … -350482590

protect my system, while the vanilla kernel does not.

Pls. feel free to test:

https://croatiafidelis.hr/gnu/deb/linux … 171209-20/

#22 Re: Installation » OpenRC and eudev installation in Devuan ceres » 2017-12-02 09:06:33

Also great to read from golinux!

fog wrote:

To answer your question:
Since I am using Devuan in VM, I can't use grsec (only exception is VirtualBox for grsec customized by Alpine Linux). I gave up on grsec because of ended updates.

There's
kernel tried to execute NX-protected page - exploit attempt?
https://github.com/minipli/linux-unoffi … -348678535
Aahh..., I gave a particular subpage... But, never mind, read how good grsec-unoff is, all visitors! And it's all linked from there.

My kernels are small ~3.7MB vmlinuz and I don't use initrd.
If you are asking about compiling deb kernels this is listed in debian handbook.

No, that's not what I asked, you can, if you don't take me wrong, pls. don't do, reread what I asked.
See also...

But I have to post this temporarily, incomplete, else I might lose it... attacked too often lately...

Continuing. Pls read those traces linked from above that alomost undeniably indicate attemped intrusions and forgive my stuttered posting smile

My config file is really for VM. This in fact is the reason why libre kernel is working on the laptop:
libre disables all firmware including my intel wireless, but in VM I set guest with virtual eth0 which is NATed to whatever connection host is making.

I did install eudev without exiting X.

That note was for other future users of eudev

This is probably advantage of VM using most common virtual hardware that do not cause problems with installed OS.

If you are looking for good secure VM try Qubes, but to take full advantage of Qubes, you will have to have specific hardware. This is on the other hand quite risky considering latest revelations about bugs in intel me.

The problem is Qubes, IIRC, can't be used without dbus, and I don't have dbus, and don't want to use it, don't trust it.... My Devuan is  sans-dbus.
Else, I read about Qubes, I have their paxrat installed in my box.

I have found one way to completely remove ME (BIOS free space will go up from 1MB to 5MB), but I did not try it yet.

On my AMD64 it's PSP, not ME.
Regards!

#23 Re: Installation » OpenRC and eudev installation in Devuan ceres » 2017-12-01 22:54:39

Similar setup in my machines (I use Air-Gap cloning, so it's kind of same system on master and clones, only built in Air-Gapped)

fog wrote:

I intentionally selected the subject similar to this one:
https://dev1galaxy.org/viewtopic.php?id=1128
that is I did exactly the same as described in the topic above.
in detail:
1) updated Devuan Jesse
https://talk.devuan.org/t/upgrading-dev … -ascii/363
2) installed openrc
https://dev1galaxy.org/viewtopic.php?id=1128
and removed services I don't need

I was late on this one:

I mean, I've deployed it on two of my system only today (and a third system will be getting it via cloning).
But I have a question about this one:

fog wrote:

4) installed libre linux kernel from sources
http://linux-libre.fsfla.org/pub/linux-libre/releases/

And the question is (no time to research on my own right now): can grsec-unoff be patched onto libre linux kernel... Umhh, no! I don't think... It gets patched on the LTS 4.9.x series from kernel.org... so, at least not directly, not without modifications...

fog wrote:

compiled deb kernel streamlined for my hardware/virtualbox

I would have liked if I knew how to do that when I was trying to, months ago... But no time to research now. (But if you have quick links, I could return (at some unspecified time) later knowing where to start my research from.)

fog wrote:

When I was trying ceres a month ago system was freezing often. Now, after few hours ceres still behaves. To me this means that developers are working hard to get new Devuan ready.

Yep! smile

One usuful note about eudev: exit Xorg before you install eudev. On two of my machines (with same system, though, but one never sees online: the Air-Gapped master), upon installing eudev, Xorg froze. Nothing broke in the least, and the installation continued, just I wouldn't see it but in the logs later (having grsec's exec_logging and audit_chdirenabled, I was able to know upon reboot, that it all went fine).

#24 Re: Other Issues » Fighting persistent intrusionals in Devuan (Devuan wins!) » 2017-11-25 14:53:05

I apologize to have to prolong the story I announced in this topic.

Other attacks (unconfirmed by experts following there, so pls. wait for replies in the below):

https://github.com/minipli/linux-unoffi … /issues/19
https://github.com/minipli/linux-unoffi … /issues/18
https://github.com/minipli/linux-unoffi … /issues/17
https://github.com/minipli/linux-unoffi … /issues/13

have happened in the meantime, and those, and other in links from below, took huge time for me to analyze:

https://www.croatiafidelis.hr/foss/cap/ … -RAP-Oops/

Regards!

#25 Re: Documentation » Grsecurity/Pax installation on Devuan GNU/Linux » 2017-11-16 21:22:27

There's corsac's grsecurity packages (with the new grsecunoff patches, and all the necessary recommends in Ceres.

So updating to Ceres, one can install them, probably something like:

# apt-get install linux-image-4.9.0-4-grsec-amd64

Updating to Ceres is first I'll do, and then report about it.
The news I was told on Debian Forums in the llink I gave two or so posts above.

Regards!

Board footer

Forum Software