January 2024 - Roundtable

MUUG Meeting, Tuesday, Feb 6, 7:30pm (Date Change, In-person/Hybrid Meeting) -- Firejail
by Gilbert Detillieux 31 Jan '24

31 Jan '24

The Manitoba UNIX User Group (MUUG) will be holding its next monthly meeting IN PERSON, on Tuesday, February 6th, at 7:30pm. Yes, that's a week early, i.e. the FIRST Tuesday of the month... Firejail Want to add an extra layer of protection when using complex or untrusted programs, like browsers or Steam? Short on time and fed up with overbearing whole-system solutions like SELinux or resource-hogging virtualization? Well, protect yourself the easy and painless way with Firejail! In this month's presentation, Trevor Cordes will outline why you want to use Linux Firejail, how you use it, and why it may be better for your use case than other protection solutions. Cool demos may ensue. Where to find the Meeting: Fortress Software Inc., 350 Keewatin St -- Unit #2 We have a new in-person meeting location now! Brad Vokey has graciously let us use his work office for our next in-person meeting. The meeting room will be open by 7:00 pm, with the actual meeting starting at 7:30 pm. If driving, enter the lot using the most north east entrance and drive around to the south west corner of the building (see route in map detail on poster linked below). You can use any of the free, ample, and safe parking spots that say "reserved" in front of units #1 through #4 before entering unit #2. Bus stops #30814 and #30880 (route 77) are only 150 meters away. The last bus leaves for Polo Park at 10:15 pm and for Garden City at 10:31 pm. Logan Ave. bus routes #19, #26, and #27 are a 600 meter (8 minute) walk to the south. For those unable or preferring not to attend in person, the meeting will also be available online, using BBB as usual. Stay tuned to our muug.ca home page for the official URL, which will be made available about a half hour before the meeting starts. (Reload the page if you don't see the link, or if there are issues with connecting.) *Date Change* Please note the change in meeting date for this month, and for the rest of the current year: We are now meeting on the first Tuesday of each month. The group now holds its meetings at 7:30pm on the *first* Tuesday of every month from September to June. (There are no meetings in July and August.) Meetings are open to the general public; you don't have to be a MUUG member to attend. For more information about MUUG, and its monthly meetings, check out their web server: https://muug.ca/ Help us promote this month's meeting, by putting this poster up on your workplace bulletin board or other suitable public message board, or linking to it on social media: https://muug.ca/meetings/MUUGmeeting.pdf -- Gilbert E. Detillieux E-mail: <gedetil(a)muug.ca> Manitoba UNIX User Group Web: http://muug.ca/

1 0

[SECURITY] Fedora 38 Update: ncurses-6.4-7.20230520.fc38
by Trevor Cordes 31 Jan '24

31 Jan '24

Wow, this bug must have been in ncurses for decades. Yikes. However, I'm at a loss to think of any setuid ncurses program?? Seems to have warranted a 7.8 severity though. https://nvd.nist.gov/vuln/detail/CVE-2023-29491 ncurses before 6.4 20230408, when used by a setuid application, allows local users to trigger security-relevant memory corruption via malformed data in a terminfo database file that is found in $HOME/.terminfo or reached via the TERMINFO or TERM environment variable. Begin forwarded message: Date: Wed, 31 Jan 2024 01:42:30 +0000 (UTC) From: updates(a)fedoraproject.org To: package-announce(a)lists.fedoraproject.org Subject: [SECURITY] Fedora 38 Update: ncurses-6.4-7.20230520.fc38 -------------------------------------------------------------------------------- Fedora Update Notification FEDORA-2024-96090dafaf 2024-01-31 01:41:22.934193 -------------------------------------------------------------------------------- Name : ncurses -------------------------------------------------------------------------------- Update Information: Update to newer ncurses version, which fixes CVE-2023-29491 and CVE-2023-50495. -------------------------------------------------------------------------------- ChangeLog: * Tue Aug 22 2023 Miroslav Lichvar <mlichvar(a)redhat.com> 6.4-7.20230520 - ignore TERMINFO and HOME only if setuid/setgid/capability * Thu Jul 20 2023 Fedora Release Engineering <releng(a)fedoraproject.org> - 6.4-6.20230520 - Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild * Tue Jun 27 2023 Debarshi Ray <rishi(a)fedoraproject.org> 6.4-5.20230520 - move foot entries to -base (#2217982) * Mon May 22 2023 Miroslav Lichvar <mlichvar(a)redhat.com> 6.4-4.20230520 - update to 6.4-20230520 - build with options disabling root file access and environment -------------------------------------------------------------------------------- References: [ 1 ] Bug #2191704 - CVE-2023-29491 ncurses: Local users can trigger security-relevant memory corruption via malformed data https://bugzilla.redhat.com/show_bug.cgi?id=2191704 [ 2 ] Bug #2254244 - CVE-2023-50495 ncurses: segmentation fault via _nc_wrap_entry() https://bugzilla.redhat.com/show_bug.cgi?id=2254244

2 2

Ras Pi Help needed.
by Andrew Popowich 11 Jan '24

11 Jan '24

Without going into TOO much detail, We are using 2 Rasp Pi Gen 4 We are trying to run them connected via the internet. 1 is at a barn. To be used when a sensor is triggered, it sends that alarm to the 2nd ras pi, via the internet to a house 10 kms away. ALARM will not stop until someone can press a key on ALARM sending machine in Barn. Alarm does NOT play in barn, just at 10km house. We are at the stage to just see if we can get Terminal to start up automatically when the rasp pi' s turn on, and if it can auto start terminal, run a script to just say Hello world. We have tried many "working google solutions" and all have failed. Is there anything we can try to see if getting terminal to autostart at bootup and to write hello world ? Please any ideas would be appreciated. Andrew

5 4

Problems with setting up off-site backup via Shaw (residential)
by Kevin McGregor 02 Jan '24

02 Jan '24

I've been trying to set up off-site backups from my home (site A) to another person's home (site B). My home internet (i.e. site A) is provided by Shaw. Site B has internet services provided by Telus, which is provided by Altima Telecom... which is provided by Shaw (as near as I can tell). Both sites have a server running TrueNAS. In the past I had this setup working, although the internet providers were different at the time. It involved forwarding a port by the router at site B to the destination server within site B. I haven't been able to get this to work since the change in providers. The destination simply doesn't respond no matter what port-forwarding settings I use. I ran a traceroute from site B to google.ca: Tracing route to www.google.ca [142.251.211.227] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms router.home [192.168.1.1] 2 10 ms 8 ms 8 ms 50.71.160.1 3 * * * Request timed out. 4 10 ms 9 ms 9 ms rc3sc-be2.wp.shawcable.net [24.244.58.169] 5 35 ms 35 ms 36 ms 104.159.27.13 6 37 ms 34 ms 34 ms 10.70.50.1 7 37 ms 37 ms 36 ms van-b1-link.ip.twelve99.net [62.115.145.124] 8 38 ms 38 ms 40 ms sea-b3-link.ip.twelve99.net [62.115.138.40] 9 47 ms 41 ms 42 ms sea-b1-link.ip.twelve99.net [62.115.132.157] 10 40 ms 39 ms 38 ms 74.125.51.236 11 41 ms 43 ms 42 ms 142.251.70.99 12 40 ms 40 ms 40 ms 216.239.43.121 13 43 ms 41 ms 41 ms sea30s13-in-f3.1e100.net [142.251.211.227] Trace complete. >From site A to site B, the traceroute shows: Tracing route to 104.159.x.y over a maximum of 30 hops 1 3 ms 3 ms 2 ms 192.168.1.1 2 7 ms 5 ms 6 ms 10.0.0.1 <site A is double-NATted :-( > 3 15 ms 16 ms 17 ms 50.71.160.1 4 19 ms 14 ms 17 ms rc3sc-be101-1.wp.shawcable.net [64.59.179.233] 5 18 ms 17 ms 17 ms 24.244.61.61 6 20 ms 18 ms 21 ms 24.244.58.173 7 18 ms 17 ms 22 ms rc3sc-be2.wp.shawcable.net [24.244.58.169] 8 34 ms 30 ms 28 ms rc3so-be110-1.cg.shawcable.net [66.163.76.61] 9 41 ms 42 ms 45 ms rc1bb-be6-1.vc.shawcable.net [66.163.78.38] 10 * 42 ms 41 ms rd3bb-tge0-3-0-14.vc.shawcable.net [66.163.69.42] 11 49 ms 49 ms 47 ms altimatelecom-ic-369545.ip.twelve99-cust.net [62.115.145.125] 12 50 ms 46 ms 47 ms <WAN IP of site B (104.159.x.y)> 13 79 ms 78 ms 98 ms <WAN IP of site B, again> 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 Can anyone explain what I'm seeing here? E.g. Why does the site B IP address appear twice? Why all the following request timeouts? I've used the WAN IP address of site B as the destination and set up port forwarding from that router to my remote NAS box, but as I said there is never any response. Does anyone have any suggestions as to what to try next?

4 3

Reminder: MUUG Meeting, Tonight, Jan 2, 7:30pm (Date Change, In-person/Hybrid Meeting) -- LibreNMS limitations
by Gilbert Detillieux 02 Jan '24

02 Jan '24

A reminder that the MUUG meeting will be this evening, both in person and online... The Manitoba UNIX User Group (MUUG) will be holding its next monthly meeting IN PERSON, on Tuesday, January 2nd, at 7:30pm. Yes, that's a week early, i.e. the FIRST Tuesday of the month... Working around LibreNMS dashboard limitations using Nagios, APIs, and ImageMagick We've looked at LibreNMS and its features in a past meeting. In this presentation, Chris Audet digs a bit deeper, and shows ways to overcome limitations in LibreNMS, using its API and other open source tools. Where to find the Meeting: Fortress Software Inc., 350 Keewatin St -- Unit #2 We have a new in-person meeting location now! Brad Vokey has graciously let us use his work office for our next in-person meeting. The meeting room will be open by 7:00 pm, with the actual meeting starting at 7:30 pm. If driving, enter the lot using the most north east entrance and drive around to the south west corner of the building (see route in map detail on poster linked below). You can use any of the free, ample, and safe parking spots that say "reserved" in front of units #1 through #4 before entering unit #2. Bus stops #30814 and #30880 (route 77) are only 150 meters away. The last bus leaves for Polo Park at 10:15 pm and for Garden City at 10:31 pm. Logan Ave. bus routes #19, #26, and #27 are a 600 meter (8 minute) walk to the south. For those unable or preferring not to attend in person, the meeting will also be available online, using BBB as usual. Stay tuned to our muug.ca home page for the official URL, which will be made available about a half hour before the meeting starts. (Reload the page if you don't see the link, or if there are issues with connecting.) *Date Change* Please note the change in meeting date for this month, and for the rest of the current year: We are now meeting on the first Tuesday of each month. The group now holds its meetings at 7:30pm on the *first* Tuesday of every month from September to June. (There are no meetings in July and August.) Meetings are open to the general public; you don't have to be a MUUG member to attend. For more information about MUUG, and its monthly meetings, check out their web server: https://muug.ca/ Help us promote this month's meeting, by putting this poster up on your workplace bulletin board or other suitable public message board, or linking to it on social media: https://muug.ca/meetings/MUUGmeeting.pdf -- Gilbert E. Detillieux E-mail: <gedetil(a)muug.ca> Manitoba UNIX User Group Web: http://muug.ca/

1 0