Hello:

I am in the process of building a (light as possible) Beowulf installation on a separate disk in my box.

root@devuan3:~# uname -a
Linux devuan3 4.19.0-18-amd64 #1 SMP Debian 4.19.208-1 (2021-09-29) x86_64 GNU/Linux
root@devuan3:~# 

One of the things I do not want running is AppArmor.

I added the bit security=none to the kernel command line and purged it but I still get this in dmesg:

root@devuan3:~# dmesg | grep -i apparmor
[    0.328030] AppArmor: AppArmor initialized
[    0.569017] AppArmor: AppArmor Filesystem Enabled
[    1.257404] AppArmor: AppArmor sha1 policy hashing enabled
root@devuan3:~#

So I looked to see what was going on:

root@devuan3:~# apt list | grep -i installed | grep -i apparmor
--- snip ---
libapparmor1/oldstable,now 2.13.2-10 amd64 [installed,automatic]
root@devuan3:~# 

AppArmor is not installed but it left behind its crap, which seems difficult to get rid of:

root@devuan3:~# apt purge libapparmor1
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 dconf-service : Depends: default-dbus-session-bus but it is not installable or
                          dbus-session-bus
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
root@devuan3:~#

So what is causing this?

root@devuan3:~# aptitude why libapparmor1
i   dbus Depends libapparmor1 (>= 2.8.94)
root@devuan3:~# 

dbus is installed and up to date:

root@devuan3:~# apt install dbus
Reading package lists... Done
Building dependency tree       
Reading state information... Done
dbus is already the newest version (1.12.20-0+deb10u1+devuan1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@devuan3:~# 

And dbus-session-bus can't be installed:

root@devuan3:~# apt install dbus-session-bus
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'dbus-x11' instead of 'dbus-session-bus'
dbus-x11 is already the newest version (1.12.20-0+deb10u1+devuan1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@devuan3:~# 

I have a faint memory of having come across this before but I cannot find it in the forum.

Any ideas?

Thanks in advance,

A.

Hello:

Although I have yet to master it, jED is my favourite editor.
Must be my many years under the shadow of MS editors.  8^/

One issue I solved long ago was the line numbering which (for some strange reason) is not set up by default.
Or an option to be quickly configured in a drop down menu.

You just generate a .jedrc file in your /home/user folder with this content:

LINENUMBERS = 2;

public define global_mode_hook (hook_name)
{
   
       set_line_number_mode (1);
}

See:  https://travelingfrontiers.wordpress.co … ed-editor/

The problem with this is that it is set up on a user basis and I'd like for this to be the default system-wide setting.

This came up while needing jED with line numbers while working on a VM without sudo.
I had to su or su - and line numbers were not available.

Any idea on how to get that done?

Thanks in advance,

A.

Hello:

The time to move to Devuan Chimaera is slowly getting nearer.

Whatever happened to ...

If I can avoid it, I'd really want to continue using both WiCD and SLiM.
I see the SLiM 1.3.6-5.2+devuan1 package is in the /merged  chimaera/main amd64

I run a netbook which is i386 (Asus 1000HE), is SLiM available for devuan_chimaera_4.0.0_i386?

I also see the WiCD 1.7.4+tb2-6+devuan2 package is in /merged  chimaera-proposed-updates/main amd64

Anyone using it reliably?

Thanks in advance.

A.

Hello:

Just got this in my mailbox, good to see things are working as they should:

---

X.Org Security Advisory: December 14, 2021

Multiple input validation failures in X server extensions
=========================================================

All of the following issues can lead to local privileges elevation on
systems where the X server is running privileged and remote code
execution for ssh X forwarding sessions.

* CVE-2021-4008/ZDI-CAN-14192 SProcRenderCompositeGlyphs out-of-bounds
access

The handler for the CompositeGlyphs request of the Render extension does
not properly validate the request length leading to out of bounds memory
write.

* CVE-2021-4009/ZDI-CAN 14950 SProcXFixesCreatePointerBarrier
out-of-bounds access

The handler for the CreatePointerBarrier request of the XFixes extension
does not properly validate the request length leading to out of bounds
memory write.

* CVE-2021-4010/ZDI-CAN-14951 SProcScreenSaverSuspend out-of-bounds access

The handler for the Suspend request of the Screen Saver extension does
not properly validate the request length leading to out of bounds memory
write.

* CVE-2021-4011/ZDI-CAN-14952 SwapCreateRegister out-of-bounds access

The handlers for the RecordCreateContext and RecordRegisterClients
requests of the Record extension do not properly validate the request
length leading to out of bounds memory write.

Patches
-------

Patches for this issues have been commited to the xorg server git
repository (https://gitlab.freedesktop.org/xorg/xserver). xorg-server
21.1.2 will be released shortly and will include these patches.

commit ebce7e2d80e7c80e1dda60f2f0bc886f1106ba60

    render: Fix out of bounds access in SProcRenderCompositeGlyphs()

    ZDI-CAN-14192, CVE-2021-4008

    This vulnerability was discovered and the fix was suggested by:
    Jan-Niklas Sohn working with Trend Micro Zero Day Initiative

commit b5196750099ae6ae582e1f46bd0a6dad29550e02

    xfixes: Fix out of bounds access in *ProcXFixesCreatePointerBarrier()

    ZDI-CAN-14950, CVE-2021-4009

    This vulnerability was discovered and the fix was suggested by:
    Jan-Niklas Sohn working with Trend Micro Zero Day Initiative

commit 6c4c53010772e3cb4cb8acd54950c8eec9c00d21

    Xext: Fix out of bounds access in SProcScreenSaverSuspend()

    ZDI-CAN-14951, CVE-2021-4010

    This vulnerability was discovered and the fix was suggested by:
    Jan-Niklas Sohn working with Trend Micro Zero Day Initiative

commit e56f61c79fc3cee26d83cda0f84ae56d5979f768

    record: Fix out of bounds access in SwapCreateRegister()

    ZDI-CAN-14952, CVE-2021-4011

    This vulnerability was discovered and the fix was suggested by:
    Jan-Niklas Sohn working with Trend Micro Zero Day Initiative

Thanks
======

This vulnerability was discovered by Jan-Niklas Sohn working with
Trend Micro Zero Day Initiative.

--
Povilas Kanapickas

---

Best,

A.