net-snmp packages version 5.8-1 just got uploaded. The previous upstream version 5.7.2 has been around for 4 years so this has been a long time coming.

5.8 packages also drop support of python modules, use pysnmp instead as its better in most ways.

Debian packages now should be source only, otherwise they won't make it to bullseye ( the next release).

So the wiki has the flags to add to build source only, so that's all you need to do?

Nope.

debsign and debrelease need to be told too. ( Both with -S)

So the toolchain will create a package that is guaranteed to be rejected using the default setup. The only way to fix it is to use two different sets of options.

After a lot of mucking around I got the laptop looking ok. The conky config says its but it's really .

Installing on a laptop that needs non-free firmware for the wifi to work, is there anything more frustrating?

It's pretty bad if a Debian user of over 20 years still struggles with this process, find the firmware its right there dammit.

Uploaded the mastodon module into the repository tonight. This gets it inline with the pypi version 1.4.6

It now conditionally links http_ece, so no more Debian patches :drake_like:

The program can use but there is no package inside Debian yet.

I have now use the system package for libjs-underscore rather than the one shipped with . For once, the Debian version is newer but linking it didn't seem to give any errors on a browser console. It also meant I had to update my profile for wordpress.

WordPress version 5.2.3 is now out which is a security release. It fixes a bunch of XSS problems and some sanitization problems. Debian packages soon.

wordpress.org/news/2019/09/wor

So I started to work on the new snmp packages that use net-snmp 5.8

The snmpd daemon fails to start and initial debugging shows it attempting to bind to UDP port 161 *twice* ; which is why it bugs out.

So next part of the puzzle is why twice?

-make the Debian package that makes other Debian packages got it's first update for the year.

Not terribly exciting changes, just a bump of the Debian standards and debhelper versions mostly.

I thought I should use something a bit more robust than my pile of shell scripts for firewalling my server so tried out

At first it was a total disaster and would not add rules to the nftables no matter what I did. Digging around, there is a bug with iptables-nft especially around iptables-restore. Updating iptables package fixed things up nicely.

Tonight's plan is to look at the net-snmp packages to see if I should drop the 2 module. I'm pretty sure they don't support python3 and are bad in many ways so they are likely to go.

5.2.2 packages now uploaded to the FTP servers.

Not really sure what they changed between 5.2.1 and 5.2.2 just some tweaks by the look of things.

Also 5.3 should be out soon.

wordpress.org/news/2019/06/wor

The postfix profiles in the package don't work with the Debian postfix.

At least it's only complain mode but it still kills processes if you try to switch context.

packages of the library written by @halcy uploaded to the Debian FTP servers just now. This is a bump from 1.3.1 to 1.4.2 because I have been slack.

5.2.1 packages just got built and I'm uploading them in a few minutes.

Doesn't seem to be any major security updates despite the third digit. The WordPress website is saying 5.2.2 will be out soon too; now *that* one sounds like a security thing.

I was looking at the net-snmp code trying to work out the differences between the PID file generating code for snmpd and snmptrapd.

πŸ”Ή snmpd uses open() with permissions of 0600
πŸ”Ή snmptrapd uses fopen() with permissions of 0644

Given there on my system there is only one other PID file with 0600 I patched snmpd to use 0644.

If you are running stable on the security update has made it to the repositories. The deb9u5 version is the backport of the 5.0.1 fixes.

That should mean you're ok for most current WordPress security bugs except for CVE-2019-8943 which is a path traversal bug. I think it's fixed for WordPress proper but many modules are still vulnerable.

The backports for the security fixes (based on the bugs in wordpress 5.0.1) are going to be a bit different from now.

Instead of trying to pry apart all the changesets, there is now just a consolidated changeset between 4.7.11 and 4.7.12

4.7.12 is the 4.7 branch of fixes backported from 5.0.1. Just using the entire changeset makes it easier and helps with things like database updates.

I've been triaging a bunch of net-snmp bugs on the bug tracker tonight. There are a lot of old ones for versions of net-snmp long gone.

Strangely there are old bugs that are still there, like why are the permissions for snmp and snmptrapd pid files different?

Clearing out the old ones means I can concentrate on what is left.

I've updated the git repository for -snmp to the latest which is 5.8

The Debian specific patches are now applying cleanly so the next steps are
* to make sure it compiles
* Fix it when it surely won't
* Look at the Debian bugs and fix/close those
* Release!

It's a pretty big codebase that takes forever to compile so it won't be a fast process.

Show more
Mastodon on Dropbear

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!