Re: [DNG] It's far from being over. Sigh!
Round 2! spectre V4! https://www.cnet.com/news/intel-microsoft-reveal-new-variant-on-spectre-meltdown-chip-security-flaws/ Of course zero real info for us lowly peons, like before only microsoft and the criminals have the info we get nothing - even congress is mad about it. https://www.zdnet.com/article/meltdown-spectre-why-were-flaws-kept-secret-from-industry-demand-lawmakers/ Now there is of course a SMM exploit too, good for me that I use a coreboot port with SMM gone :D 0xDF372A17.asc Description: application/pgp-keys ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] LibreOffice removed with autoremove
>> >> Try removing packages.devuan.org: it shouldn't be necessary when you have >> pkgmaster.devuan.org active. My output is: >> >> libpython3.5-stdlib: >> Installed: 3.5.3-1 >> Candidate: 3.5.3-1 >> Version table: >> *** 3.5.3-1 500 >>500 https://pkgmaster.devuan.org/merged ascii/main amd64 Packages >>100 /var/lib/dpkg/status >> >> >>> I have never used backports before. I will have to search the >>> archives or the forum for how to do it. >>> >>> Vernon >> >> You can add the file /etc/apt/sources.list.d/devuan-ascii-backports.list >> with the following lines: >> >> deb https://pkgmaster.devuan.org/merged/ ascii-backports main >> deb-src http://backports.devuan.org/merged/ ascii-backports main >> >> and then you run the command: >> >> apt-get -t ascii-backports --just-print install libreoffice >> >> and you get the list of the (many) packages you'd update or install to their >> backports version to install libreoffice-1:6.0.4~rc1-4~bpo9+2 (they're 43 in >> my system). >> >> >> Alessandro >> >> On Mon, 21 May 2018 at 23:43:34 +0200 >> Alessandro Selli wrote: >> >>> You can add the file /etc/apt/sources.list.d/devuan-ascii-backports.list >>> with the following lines: >>> >>> deb https://pkgmaster.devuan.org/merged/ ascii-backports main >>> deb-src http://backports.devuan.org/merged/ ascii-backports main >> >> Sorry, the second line should read: >> >> deb-src http://pkgmaster.devuan.org/merged/ ascii-backports main >> >> I didn't notice the error before because it's commented in my system. >> >> >> Alessandro >> > > Thank you Alessandro I will try that. > > Also to all, sorry for changing the Subject line in the last post. > > Vernon After removing the packages.devuan.org you will want to downgrade your package version to the one from the pkgmaster.devuan.org repository. apt-get install libpython3.5-stdlib=3.5.3-1 apt-mark auto libpython3.5-stdlib The second command will just set the package back to automatically installed status within apt configuration. After this you shouldn’t have any issues installing libreoffice 6 from backports using Allesandro’s instructions. —Tom ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] LibreOffice removed with autoremove
> > Message: 6 > Date: Mon, 21 May 2018 23:43:34 +0200 > From: Alessandro Selli > To: dng@lists.dyne.org > Subject: Re: [DNG] LibreOffice removed with autoremove > Message-ID: <20180521234334.1c0a4f7e@ayu.localdomain> > Content-Type: text/plain; charset=UTF-8 > > On Sun, 20 May 2018 at 20:35:17 -0700 > Vernon Geiszler wrote: > >> On Sun, May 20, 2018 at 5:44 PM, wrote: >>> On 21 May 2018, at 10:08, wirelessd...@gmail.com wrote: > > [...] > I can only see 3.5.3-1 in the archive. Do you have other third-party repos enabled? What’s the output of “apt-cache policy libpython3.5-stdlib”? —Tom >>> >>> I should also note that I have had no problems installing libreoffice >>> 6.0.4~rc1-4~bpo9+2 from ascii-backports. >> >> This is the output from apt-cache policy: >> >> libpython3.5-stdlib: >> Installed: 3.5.3-3 >> Candidate: 3.5.3-3 >> Version table: >> *** 3.5.3-3 100 >> 100 /var/lib/dpkg/status >> 3.5.3-1 500 >> 500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages >> 500 http://packages.devuan.org/merged ascii/main amd64 Packages > > Try removing packages.devuan.org: it shouldn't be necessary when you have > pkgmaster.devuan.org active. My output is: > > libpython3.5-stdlib: > Installed: 3.5.3-1 > Candidate: 3.5.3-1 > Version table: > *** 3.5.3-1 500 > 500 https://pkgmaster.devuan.org/merged ascii/main amd64 Packages > 100 /var/lib/dpkg/status > > >> I have never used backports before. I will have to search the >> archives or the forum for how to do it. >> >> Vernon > > You can add the file /etc/apt/sources.list.d/devuan-ascii-backports.list > with the following lines: > > deb https://pkgmaster.devuan.org/merged/ ascii-backports main > deb-src http://backports.devuan.org/merged/ ascii-backports main > > and then you run the command: > > apt-get -t ascii-backports --just-print install libreoffice > > and you get the list of the (many) packages you'd update or install to their > backports version to install libreoffice-1:6.0.4~rc1-4~bpo9+2 (they're 43 in > my system). > > > Alessandro > > > > -- > > Message: 7 > Date: Tue, 22 May 2018 01:16:04 +0200 > From: Alessandro Selli > To: dng@lists.dyne.org > Subject: Re: [DNG] LibreOffice removed with autoremove > Message-ID: <20180522011604.6b0a32a6@ayu.localdomain> > Content-Type: text/plain; charset=US-ASCII > > On Mon, 21 May 2018 at 23:43:34 +0200 > Alessandro Selli wrote: > >> You can add the file /etc/apt/sources.list.d/devuan-ascii-backports.list >> with the following lines: >> >> deb https://pkgmaster.devuan.org/merged/ ascii-backports main >> deb-src http://backports.devuan.org/merged/ ascii-backports main > > Sorry, the second line should read: > > deb-src http://pkgmaster.devuan.org/merged/ ascii-backports main > > I didn't notice the error before because it's commented in my system. > > > Alessandro > > > -- > > Message: 8 > Date: Mon, 21 May 2018 18:41:40 -0700 > From: Vernon Geiszler > To: dng@lists.dyne.org > Subject: Re: [DNG] Dng Digest, Vol 44, Issue 36 > Message-ID: > > Content-Type: text/plain; charset="UTF-8" > >> >> Message: 1 >> Date: Mon, 21 May 2018 15:13:46 +1000 >> From: wirelessd...@gmail.com >> To: dng@lists.dyne.org >> Subject: Re: [DNG] LibreOffice removed with autoremove >> Message-ID: >> Content-Type: text/plain; charset=utf-8 >> >> >>> On 21 May 2018, at 13:35, Vernon Geiszler wrote: >>> >>> This is the output from apt-cache policy: >>> >>> libpython3.5-stdlib: >>> Installed: 3.5.3-3 >>> Candidate: 3.5.3-3 >>> Version table: >>> *** 3.5.3-3 100 >>>100 /var/lib/dpkg/status >>> 3.5.3-1 500 >>>500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages >>>500 http://packages.devuan.org/merged ascii/main amd64 Packages >>> >>> I have never used backports before. I will have to search the >>> archives or the forum for how to do it. >>> >>> Vernon >> >> I can’t see that specific package version in the repository. Did you have >> any other non-devuan apt sources enabled at any point previously? Is there >> any relevant information in the output of “aptitude why libpython3.5-stdlib”? >> >> -- > > This is my full apt sources. > > # deb cdrom:[Debian GNU/Linux 1.0 _Jessie_ - Official Release > Candidate amd64 NETINST Binary-1 20170420-22:04]/ jessie contrib main > non-free > > #deb cdrom:[Debian GNU/Linux 1.0 _Jessie_ - Official Release Candidate > amd64 NETINST Binary-1 20170420-22:04]/ jessie contrib main non-free > > deb http://pkgmaster.devuan.org/merged/ ascii main > deb-src http://pkgmaster.devuan.org/merged/ ascii main > > # jessie-security, previously known as 'volatile' > deb http://pkgmaster.devuan.org/merged/ ascii-security main contrib non-free > deb-src http://pkgmaster.devuan.org/merged/ ascii-security main contrib > non-free > > # jessie-updates, previously known as 'volat
Re: [DNG] Dng Digest, Vol 44, Issue 36
> > Message: 1 > Date: Mon, 21 May 2018 15:13:46 +1000 > From: wirelessd...@gmail.com > To: dng@lists.dyne.org > Subject: Re: [DNG] LibreOffice removed with autoremove > Message-ID: > Content-Type: text/plain; charset=utf-8 > > >> On 21 May 2018, at 13:35, Vernon Geiszler wrote: >> >> This is the output from apt-cache policy: >> >> libpython3.5-stdlib: >> Installed: 3.5.3-3 >> Candidate: 3.5.3-3 >> Version table: >> *** 3.5.3-3 100 >>100 /var/lib/dpkg/status >> 3.5.3-1 500 >>500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages >>500 http://packages.devuan.org/merged ascii/main amd64 Packages >> >> I have never used backports before. I will have to search the >> archives or the forum for how to do it. >> >> Vernon > > I can’t see that specific package version in the repository. Did you have any > other non-devuan apt sources enabled at any point previously? Is there any > relevant information in the output of “aptitude why libpython3.5-stdlib”? > > -- This is my full apt sources. # deb cdrom:[Debian GNU/Linux 1.0 _Jessie_ - Official Release Candidate amd64 NETINST Binary-1 20170420-22:04]/ jessie contrib main non-free #deb cdrom:[Debian GNU/Linux 1.0 _Jessie_ - Official Release Candidate amd64 NETINST Binary-1 20170420-22:04]/ jessie contrib main non-free deb http://pkgmaster.devuan.org/merged/ ascii main deb-src http://pkgmaster.devuan.org/merged/ ascii main # jessie-security, previously known as 'volatile' deb http://pkgmaster.devuan.org/merged/ ascii-security main contrib non-free deb-src http://pkgmaster.devuan.org/merged/ ascii-security main contrib non-free # jessie-updates, previously known as 'volatile' deb http://pkgmaster.devuan.org/merged/ ascii-updates main contrib non-free deb-src http://pkgmaster.devuan.org/merged/ ascii-updates main contrib non-free # Devuan repositories deb http://packages.devuan.org/merged ascii main contrib non-free deb-src http://packages.devuan.org/merged ascii main contrib non-free # libdvdcss deb http://download.videolan.org/pub/debian/stable/ / deb-src http://download.videolan.org/pub/debian/stable/ / Vernon ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] LibreOffice removed with autoremove
On Mon, 21 May 2018 at 23:43:34 +0200 Alessandro Selli wrote: > You can add the file /etc/apt/sources.list.d/devuan-ascii-backports.list > with the following lines: > > deb https://pkgmaster.devuan.org/merged/ ascii-backports main > deb-src http://backports.devuan.org/merged/ ascii-backports main Sorry, the second line should read: deb-src http://pkgmaster.devuan.org/merged/ ascii-backports main I didn't notice the error before because it's commented in my system. Alessandro ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] LibreOffice removed with autoremove
On Sun, 20 May 2018 at 20:35:17 -0700 Vernon Geiszler wrote: > On Sun, May 20, 2018 at 5:44 PM, wrote: >> >>> On 21 May 2018, at 10:08, wirelessd...@gmail.com wrote: [...] >>> I can only see 3.5.3-1 in the archive. Do you have other third-party >>> repos enabled? >>> >>> What’s the output of “apt-cache policy libpython3.5-stdlib”? >>> >>> —Tom >> >> I should also note that I have had no problems installing libreoffice >> 6.0.4~rc1-4~bpo9+2 from ascii-backports. > > This is the output from apt-cache policy: > > libpython3.5-stdlib: > Installed: 3.5.3-3 > Candidate: 3.5.3-3 > Version table: > *** 3.5.3-3 100 > 100 /var/lib/dpkg/status > 3.5.3-1 500 > 500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages > 500 http://packages.devuan.org/merged ascii/main amd64 Packages Try removing packages.devuan.org: it shouldn't be necessary when you have pkgmaster.devuan.org active. My output is: libpython3.5-stdlib: Installed: 3.5.3-1 Candidate: 3.5.3-1 Version table: *** 3.5.3-1 500 500 https://pkgmaster.devuan.org/merged ascii/main amd64 Packages 100 /var/lib/dpkg/status > I have never used backports before. I will have to search the > archives or the forum for how to do it. > > Vernon You can add the file /etc/apt/sources.list.d/devuan-ascii-backports.list with the following lines: deb https://pkgmaster.devuan.org/merged/ ascii-backports main deb-src http://backports.devuan.org/merged/ ascii-backports main and then you run the command: apt-get -t ascii-backports --just-print install libreoffice and you get the list of the (many) packages you'd update or install to their backports version to install libreoffice-1:6.0.4~rc1-4~bpo9+2 (they're 43 in my system). Alessandro ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Switching to OpenRC
On Mon, 21 May 2018 at 14:01:42 +0200 Adam Borowski wrote: > On Mon, May 21, 2018 at 05:53:56PM +1000, wirelessd...@gmail.com wrote: > >> Originally, I really had no idea what I was referring to specifically. >> After some more poking around, I think you’re right. I said sysv-rc >> because I noticed that installing the openrc package would only >> uninstall/conflict with the sysv-rc package and not the rest of >> sysvinit. > > The important part is: sane init systems are _modular_. Various fields have > various integration-to-modularity tradeoffs, and init+rc+supervisor schemes > are at such an extreme that I say it would take a deranged mind to argue > that an unextendable blob is fit for this job. I fully agree. What you wrote is to me the best rationale against systemd, beyond the fine technical details. Alessandro ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Switching to OpenRC
On Mon, 21 May 2018 14:01:42 +0200 Adam Borowski wrote: > ... none of the contenders is adequate for every single > use case, thus you need to allow the sysadmin to replace pieces with > something that he/she wants. Quoted for truth in perpetuity. Well said! > Don't fear change, fear inability to change. Even more quoted for truth in perpetuity! I'll be using these points often. Thanks! SteveT Steve Litt June 2018 featured book: Twenty Eight Tales of Troubleshooting http://www.troubleshooters.com/28 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Switching to OpenRC, including respawn
On Mon, 21 May 2018 19:05:37 +1000 wirelessd...@gmail.com wrote: > > On 14 May 2018, at 18:51, Steve Litt > > wrote: > > > > One property of OpenRC is it has no facility to respawn a daemon > > when the old daemon crashes. Some folks like it this way, some > > don't, but it's a fact of OpenRC. Except... > > > > There are two ways to have OpenRC respawn. Way 1 is to run the > > daemon from /etc/inittab, with the "respawn" flag. Remember, OpenRC > > doesn't have its own PID1, and traditionally uses sysvinit's PID1. > > > > Way 2 is to have OpenRC run either runit or s6 from /etc/inittab > > with "respawn", and then to put all respawnable daemons in runit or > > s6. Running either runit or s6 *as a supervisor rather than an > > init* is dead-bang easy. Since about 2010 I've been doing something > > similar: I ran daemontools on top of sysvinit, and it always worked > > out great for me. > > > > SteveT > > I had a closer look at OpenRC docs and noticed they now include a > built-in “supervise-daemon”[1] supervisor that can be used instead of > the default start-stop-daemon. It will restart a daemon if it > terminates unexpectedly. Dang that's big news, and changes things profoundly. From reading it, did it look like you could use the start-stop on some things, and the "supervise daemon" on others? That would be ideal. > > The only issue with it for my use case is that I couldn’t find any > way to send an arbitrary signal to the supervised daemon without > signalling it to stop. The problem being that the pidfile created > exists for the individual supervisor process and not the supervised > daemon process. I'll tell you about signals in runit, in the hope that you can find something similar in OpenRC. Runit has the sv command, which can be used to start the process being supervised, send signals to the process, or get info about the process: sv down sshd sends TERM then CONT to sshd Without going into syntax, sv can easily send any of the following signals to the daemon (sshd in this example): STOP, CONT, HUP, ALRM, INT, QUIT, USR1, USR2, TERM, or KILL But wait, there's more. If somehow you need to send yet some other signal, the generic way is to find the daemon's PID is the following: [root@mydesk ~]# sv status sshd run: sshd: (pid 739) 56174s [root@mydesk ~]# A little awk-foo, and you have your PID, and from there, you can use the kill command (or equivalent in whatever language you're using) to send absolutely any signal to that PID. I bet OpenRC's supervisor has an equivalent to sv status, because daemontools, runit and s6, all prior art, have that capability. SteveT Steve Litt June 2018 featured book: Twenty Eight Tales of Troubleshooting http://www.troubleshooters.com/28 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Switching to OpenRC
On Mon, May 21, 2018 at 05:53:56PM +1000, wirelessd...@gmail.com wrote: > >> On Tue, 15 May 2018 23:39:24 +1000 > >> Tom wrote: > >> > >>> Thanks as always for your insightful information Steve. Much > >>> appreciated. As someone who knows very little about init systems, > >>> can you explain what this respawning business is all about? > >> > >> Terminology: I call the init system we've used for 30 years "sysvinit". > > > >> I assume here you mean sysvinit when you write sysv-rc. > > > > I think Tom is not referring to the whole init system, rather to just the > > rc scripts: > Originally, I really had no idea what I was referring to specifically. > After some more poking around, I think you’re right. I said sysv-rc > because I noticed that installing the openrc package would only > uninstall/conflict with the sysv-rc package and not the rest of sysvinit. The important part is: sane init systems are _modular_. Various fields have various integration-to-modularity tradeoffs, and init+rc+supervisor schemes are at such an extreme that I say it would take a deranged mind to argue that an unextendable blob is fit for this job. The reason is: none of the contenders is adequate for every single use case, thus you need to allow the sysadmin to replace pieces with something that he/she wants. More importantly, "job security" is antithetical to Free Software: an irreplaceable tangle can't be reasonably improved. A set of small modules, on the other hand, is _made_ for experiments, many of which will take over their predecessors. Don't fear change, fear inability to change. Main parts here are: * init. Pid 1. Its tasks are: 1. spawning the rc system; 2. reaping orphaned processes. That's all. Other functionality might be also implemented in pid 1, but that's up to you -- for example, sysvinit chose to add a rudimentary process supervisor whose main use today is spawning getties -- and a particular contender put pretty much everything there. * rc system. On De??an started by /etc/init.d/rcS; its tasks are starting daemons whenever you boot, shutdown, switch to a different runlevel, install or remove a package, or otherwise manually request. This is sysv-rc or openrc. * daemon supervisor. This is what handles daemons that unexpectedly die. Most daemons are designed to not die, the only case on a regular Unix system is getty -- anything else tends to be a hallmark of an attack; usually mindlessly restarting turns a DoS into giving more and more opportunity of a successful intrusion. For a real supervisor you want something like runit; sysvinit has inittab which is extremely limited. OpenRC has no equivalent -- or rather, had none until the introduction of supervise-daemon which I don't know yet. But hey, it's not like I'm one of uploaders of openrc or anything to be supposed to know such things, am I? .sig related. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ .globl _start↵.data↵rc: .ascii "/etc/init.d/rcS\0"↵.text↵_start ⣾⠁⢰⠒⠀⣿⡁ mov $57,%rax↵syscall↵cmp $0,%rax↵jne child↵parent:↵mov $61,%rax ⢿⡄⠘⠷⠚⠋⠀ mov $-1,%rdi↵xor %rsi,%rsi↵xor %rdx,%rdx↵syscall↵jmp parent↵child: ⠈⠳⣄ mov $59,%rax↵mov $rc,%rdi↵xor %rsi,%rsi↵xor %rdx,%rdx↵syscall ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ..waaay OT: Is Void OK? Was: Keep it alive
On Sun, 20 May 2018 14:51:46 +0200, Alessandro wrote in message <20180520145146.251636eb@ayu.localdomain>: > On Sun, 20 May 2018 at 13:06:45 +0200 > Arnt Karlsen wrote: > > > ..precisely why you want _full_ infrastructure redundancy, without > > any "single point of failure capable of bringing down everything." > > Then you must mean something different from ICT infrastructure. ..yup, true end-to-end communication, like using a local radio station using https://en.wikipedia.org/wiki/FM_broadcasting to mobilize ballot signatories and using https://en.wikipedia.org/wiki/Telephone for coordination etc, as an alternative to such modern amenities as the https://en.wikipedia.org/wiki/Internet . ..to prevent another such heinous scare, the aptly named 'Descendants Of Quisling' (by the Israeli ambassador to Norway Raphael Schutz) has killed off FM radio: ... https://en.wikipedia.org/wiki/Digital_audio_broadcasting#FM_radio_switch-off ...and civil defense amenities such as air raid alarm systems in this wonderful death trap called "Norway." -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Switching to OpenRC, including respawn
> On 14 May 2018, at 18:51, Steve Litt wrote: > > One property of OpenRC is it has no facility to respawn a daemon when > the old daemon crashes. Some folks like it this way, some don't, but > it's a fact of OpenRC. Except... > > There are two ways to have OpenRC respawn. Way 1 is to run the daemon > from /etc/inittab, with the "respawn" flag. Remember, OpenRC doesn't > have its own PID1, and traditionally uses sysvinit's PID1. > > Way 2 is to have OpenRC run either runit or s6 from /etc/inittab with > "respawn", and then to put all respawnable daemons in runit or s6. > Running either runit or s6 *as a supervisor rather than an init* is > dead-bang easy. Since about 2010 I've been doing something similar: I > ran daemontools on top of sysvinit, and it always worked out great for > me. > > SteveT I had a closer look at OpenRC docs and noticed they now include a built-in “supervise-daemon”[1] supervisor that can be used instead of the default start-stop-daemon. It will restart a daemon if it terminates unexpectedly. The only issue with it for my use case is that I couldn’t find any way to send an arbitrary signal to the supervised daemon without signalling it to stop. The problem being that the pidfile created exists for the individual supervisor process and not the supervised daemon process. [1] https://github.com/OpenRC/openrc/blob/master/supervise-daemon-guide.md —Tom___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] DSA Ascii May21
Thu, 17 May 2018 17:24:47 +0200 [SECURITY] [DSA 4203-1] vlc security update Binary: vlc, libvlc-dev, libvlc5, libvlccore-dev, libvlccore9, libvlc-bin, vlc-bin, vlc-data, vlc-l10n, vlc-plugin-base, vlc-plugin-access-extra, vlc-plugin-video-output, vlc-plugin-video-splitter, vlc-plugin-visualization, vlc-plugin-skins2, vlc-plugin-qt, vlc-plugin-fluidsynth, vlc-plugin-jack, vlc-plugin-notify, vlc-plugin-svg, vlc-plugin-samba, vlc-nox, vlc-plugin-zvbi Version: 3.0.2-0+deb9u1 Confirmed: ascii-security, ascii-proposed-updates Wed, 16 May 2018 21:14:47 +0100 [SECURITY] [DSA 4202-1] curl security update Binary: curl, libcurl3, libcurl3-gnutls, libcurl3-nss, libcurl4-openssl-dev, libcurl4-gnutls-dev, libcurl4-nss-dev, libcurl3-dbg, libcurl4-doc Version: 7.52.1-5+deb9u6 Confirmed: ascii-security, ascii-proposed-updates Tue, 15 May 2018 22:03:29 +0200 [SECURITY] [DSA 4201-1] xen security update For the Debian distribution (stretch), these problems have been fixed in version 4.8.3+comet2+shim4.10.0+comet3-1+deb9u6. Note: https://security-tracker.debian.org/tracker/source-package/xen Version 4.8.3+comet2+shim4.10.0+comet3-1+deb9u6 *is not* listed as a version for Debian stretch (Devuan ascii). Version:4.8.3+xsa262+shim4.10.0+comet3-1+deb9u6 *is* listed for Debian stretch (security). Binary: libxen-4.8, libxenstore3.0, libxen-dev, xenstore-utils, xen-utils-common, xen-utils-4.8, xen-hypervisor-4.8-amd64, xen-system-amd64, xen-hypervisor-4.8-arm64, xen-system-arm64, xen-hypervisor-4.8-armhf, xen-system-armhf Note: Devuan repositories contain Version: 4.8.3+comet2+shim4.10.0+comet3-1+deb9u5 Confirmed: ascii, beowulf, ceres Version: 4.8.3+xsa262+shim4.10.0+comet3-1+deb9u6 Confirmed: ascii-security/main Version 4.8.3+comet2+shim4.10.0+comet3-1+deb9u6 requires confirmation as correct package. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] DSA Jessie May21
Fri, 18 May 2018 21:21:25 +0200 [SECURITY] [DSA 4205-1] Advance notification This is an advance notice that regular security support for Devuan "jessie" will be terminated on the 17th of June. As with previous releases additional LTS support will be provided for a reduced set of architectures and packages, a separate announcement will be available in due time. Fri, 18 May 2018 16:59:44 + [SECURITY] [DSA 4204-1] imagemagick security update Binary: imagemagick-common, imagemagick-doc, libmagickcore-6-headers, libmagickwand-6-headers, libmagick++-6-headers, imagemagick, libimage-magick-perl, libmagickcore-6-arch-config, imagemagick-6.q16, libmagickcore-6.q16-2, libmagickcore-6.q16-2-extra, libmagickcore-6.q16-dev, libmagickwand-6.q16-2, libmagickwand-6.q16-dev, libmagick++-6.q16-5, libmagick++-6.q16-dev, imagemagick-dbg, libimage-magick-q16-perl, perlmagick, libmagickcore-dev, libmagickwand-dev, libmagick++-dev Version:8:6.8.9.9-5+deb8u12 Confirmed: jessie-security, jessie-proposed-updates Thu, 17 May 2018 17:24:47 +0200 [SECURITY] [DSA 4203-1] vlc security update VLC in jessie cannot be migrated to version 3 due to incompatible library changes with reverse dependencies and is thus now declared end-of-life for jessie. Recommended: upgrade to ascii or pick a different media player if that's not an option. Wed, 16 May 2018 21:14:47 +0100 [SECURITY] [DSA 4202-1] curl security update Binary: curl, libcurl3, libcurl3-gnutls, libcurl3-nss, libcurl4-openssl-dev, libcurl4-gnutls-dev, libcurl4-nss-dev, libcurl3-dbg, libcurl4-doc Version: 7.38.0-4+deb8u11 Confirmed: jessie-security, jessie-proposed-updates ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Switching to OpenRC
> On 19 May 2018, at 12:36, Alessandro Selli wrote: > > Sorry for breaking the thread, but I no longer have the original post to > reply to. > > Author: Steve Litt > Date: 2018-05-15 16:55 +200 > To: dng > Subject: Re: [DNG] Switching to OpenRC > >> On Tue, 15 May 2018 23:39:24 +1000 >> Tom wrote: >> >>> Thanks as always for your insightful information Steve. Much >>> appreciated. As someone who knows very little about init systems, >>> can you explain what this respawning business is all about? >> >> Terminology: I call the init system we've used for 30 years "sysvinit". > > [...] > >>> I didn’t >>> realise the existing sysv-rc >> >> I assume here you mean sysvinit when you write sysv-rc. > > I think Tom is not referring to the whole init system, rather to just the > rc scripts: > > Pure SysV Devuan Ascii: > > [alessandro@wkstn09 ~ ]$ dpkg-query --search /etc/init.d/rc > sysv-rc: /etc/init.d/rc > [alessandro@wkstn09 ~ ]$ > > SysV+OpenRC Devuan Ascii: > > alessandro@kratom:~$ dpkg-query --search /etc/init.d/rc > openrc: /etc/init.d/rc > alessandro@kratom:~$ Originally, I really had no idea what I was referring to specifically. After some more poking around, I think you’re right. I said sysv-rc because I noticed that installing the openrc package would only uninstall/conflict with the sysv-rc package and not the rest of sysvinit. Hopefully that clears things up a bit. —Tom ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
