Login: GUEST @ JH4XSY.14.JNET1.JPN.AS [Tsuchiura]
home | newest check | boards | help index | log | ps | userlogin | send sysop | slog | status forward | bcm news | users | version | remove cookie
LU9DCE > ARCH 16.02.25 17:33l 236 Lines 10433 Bytes #21 (0) @ WW
BID : 5945_LU9DCE
Read: GUEST
Subj: ARCHLINUX NEWS 16-FEB25
Path: JH4XSY<JE7YGF<LU4ECL<LU9DCE
Sent: 250216/0831Z 5945@LU9DCE.TOR.BA.ARG.SOAM LinBPQ6.0.24
__ _ _ ___ ____ ___ ____ ____ ____ ____
( ) / )( \/ _ \( \ / __)( __) ( _ \( _ \/ ___)
/ (_/\) \/ (\__ )) D (( (__ ) _) ) _ ( ) _ (\___ \
\____/\____/(___/(____/ \___)(____) (____/(____/(____/
PACKET RADIO STATION - BUENOS AIRES (GF05OM)
PHP SCHEDULED NEWSLETTERS (PSN)
COPYRIGHT 2025 - EDUARDO A. CASTILLO
SESSION - 05E9490351ED5441879F64AAD986F3A16DDA2EDD4C40392E1484F4428A72D9DA6D
+----------------------------------------------------------------------------+
GLIBC 2.41 CORRUPTING DISCORD INSTALLATION
WE PLAN TO MOVE GLIBC AND ITS FRIENDS TO STABLE LATER TODAY, FEB 3. AFTER
INSTALLING THE UPDATE, THE DISCORD CLIENT WILL SHOW A RED WARNING THAT THE
INSTALLATION IS CORRUPT.
THIS ISSUE HAS BEEN FIXED IN THE DISCORD CANARY BUILD. IF YOU RELY ON AUDIO
CONNECTIVITY, PLEASE USE THE CANARY BUILD, LOGIN VIA BROWSER OR THE FLATPAK
VERSION UNTIL THE FIX HITS THE STABLE DISCORD RELEASE.
THERE HAVE BEEN NO REPORTS THAT (WRITTEN) CHAT CONNECTIVITY IS AFFECTED.
UPDATE: THE ISSUE HAS BEEN FIXED IN DISCORD 0.0.84-1.
=#=#=#=#=#=#=#=#=
CRITICAL RSYNC SECURITY RELEASE 3.4.0
WE'D LIKE TO RAISE AWARENESS ABOUT THE RSYNC SECURITY RELEASE VERSION 3.4.0-1
AS DESCRIBED IN OUR ADVISORY ASA-202501-1.
AN ATTACKER ONLY REQUIRES ANONYMOUS READ ACCESS TO A VULNERABLE RSYNC SERVER,
SUCH AS A PUBLIC MIRROR, TO EXECUTE ARBITRARY CODE ON THE MACHINE THE SERVER
IS RUNNING ON.
ADDITIONALLY, ATTACKERS CAN TAKE CONTROL OF AN AFFECTED SERVER AND READ/WRITE
ARBITRARY FILES OF ANY CONNECTED CLIENT.
SENSITIVE DATA CAN BE EXTRACTED, SUCH AS OPENPGP AND SSH KEYS, AND MALICIOUS
CODE CAN BE EXECUTED BY OVERWRITING FILES SUCH AS ~/.BASHRC OR ~/.POPT.
WE HIGHLY ADVISE ANYONE WHO RUNS AN RSYNC DAEMON OR CLIENT PRIOR TO VERSION
3.4.0-1 TO UPGRADE AND REBOOT THEIR SYSTEMS IMMEDIATELY.
AS ARCH LINUX MIRRORS ARE MOSTLY SYNCHRONIZED USING RSYNC, WE HIGHLY ADVISE
ANY MIRROR ADMINISTRATOR TO ACT IMMEDIATELY, EVEN THOUGH THE HOSTED PACKAGE
FILES THEMSELVES ARE CRYPTOGRAPHICALLY SIGNED.
ALL INFRASTRUCTURE SERVERS AND MIRRORS MAINTAINED BY ARCH LINUX HAVE ALREADY
BEEN UPDATED.
=#=#=#=#=#=#=#=#=
PROVIDING A LICENSE FOR PACKAGE SOURCES
ARCH LINUX HASN'T HAD A LICENSE FOR ANY PACKAGE SOURCES (SUCH AS PKGBUILD
FILES) IN THE PAST, WHICH IS POTENTIALLY PROBLEMATIC. PROVIDING A LICENSE WILL
PREEMPT THAT UNCERTAINTY.
IN RFC 40 WE AGREED TO CHANGE ALL PACKAGE SOURCES TO BE LICENSED UNDER THE
VERY LIBERAL 0BSD LICENSE. THIS CHANGE WILL NOT LIMIT WHAT YOU CAN DO WITH
PACKAGE SOURCES. CHECK OUT THE RFC FOR MORE ON THE RATIONALE AND PRIOR
DISCUSSION.
BEFORE WE MAKE THIS CHANGE, WE WILL PROVIDE CONTRIBUTORS WITH A WAY TO VOICE
ANY OBJECTIONS THEY MIGHT HAVE. STARTING ON 2024-11-19, OVER THE COURSE OF A
WEEK, CONTRIBUTORS WILL RECEIVE A SINGLE NOTIFICATION EMAIL LISTING ALL THEIR
CONTRIBUTIONS.
IF YOU RECEIVE AN EMAIL AND AGREE TO THIS CHANGE, THERE IS NO ACTION REQUIRED
FROM YOUR SIDE.
IF YOU DO NOT AGREE, PLEASE REPLY TO THE EMAIL AND WE'LL FIND A SOLUTION
TOGETHER.
IF YOU CONTRIBUTED TO ARCH LINUX PACKAGES BEFORE BUT DIDN'T RECEIVE AN EMAIL,
PLEASE CONTACT US AT PACKAGE-SOURCES-LICENSING@ARCHLINUX.ORG.
=#=#=#=#=#=#=#=#=
MANUAL INTERVENTION FOR PACMAN 7.0.0 AND LOCAL REPOSITORIES REQUIRED
WITH THE RELEASE OF VERSION 7.0.0 PACMAN HAS ADDED SUPPORT FOR
DOWNLOADING PACKAGES AS A SEPARATE USER WITH DROPPED PRIVILEGES.
FOR USERS WITH LOCAL REPOS HOWEVER THIS MIGHT IMPLY THAT THE DOWNLOAD
USER DOES NOT HAVE ACCESS TO THE FILES IN QUESTION, WHICH CAN BE FIXED
BY ASSIGNING THE FILES AND FOLDER TO THE ALPM GROUP AND ENSURING THE
EXECUTABLE BIT (+X) IS SET ON THE FOLDERS IN QUESTION.
$ CHOWN :ALPM -R /PATH/TO/LOCAL/REPO
REMEMBER TO MERGE THE .PACNEW FILES TO APPLY THE NEW DEFAULT.
PACMAN ALSO INTRODUCED A CHANGE TO IMPROVE CHECKSUM STABILITY FOR
GIT REPOS THAT UTILIZE .GITATTRIBUTES FILES. THIS MIGHT REQUIRE A
ONE-TIME CHECKSUM CHANGE FOR PKGBUILDS THAT USE GIT SOURCES.
=#=#=#=#=#=#=#=#=
THE SSHD SERVICE NEEDS TO BE RESTARTED AFTER UPGRADING TO OPENSSH-9.8P1
AFTER UPGRADING TO OPENSSH-9.8P1, THE EXISTING SSH DAEMON WILL BE UNABLE TO
ACCEPT NEW CONNECTIONS (SEE
HTTPS://GITLAB.ARCHLINUX.ORG/ARCHLINUX/PACKAGING/PACKAGES/OPENSSH/-/ISSUES/5).
WHEN UPGRADING REMOTE HOSTS, PLEASE MAKE SURE TO RESTART THE SSHD SERVICE
USING SYSTEMCTL TRY-RESTART SSHD RIGHT AFTER UPGRADING.
WE ARE EVALUATING THE POSSIBILITY TO AUTOMATICALLY APPLY A RESTART OF THE SSHD
SERVICE ON UPGRADE IN A FUTURE RELEASE OF THE OPENSSH-9.8P1 PACKAGE.
=#=#=#=#=#=#=#=#=
ARCH LINUX 2024 LEADER ELECTION RESULTS
RECENTLY WE HELD OUR LEADER ELECTION, AND THE PREVIOUS PROJECT LEADER LEVENTE
"ANTHRAXX" POLYAK RAN AGAIN WHILE NO OTHER PEOPLE WERE NOMINATED FOR THE ROLE.
AS PER OUR ELECTION RULES HE IS RE-ELECTED FOR A NEW TERM.
THE ROLE OF OF THE PROJECT LEAD WITHIN ARCH LINUX IS CONNECTED TO A FEW
RESPONSIBILITIES REGARDING DECISION MAKING (WHEN NO CONSENSUS CAN BE REACHED),
HANDLING
FINANCIAL MATTERS WITH SPI AND OVERALL PROJECT MANAGEMENT TASKS.
CONGRATULATIONS TO LEVENTE AND ALL THE BEST WISHES FOR ANOTHER SUCCESSFUL
TERM! ･ｳ
=#=#=#=#=#=#=#=#=
INCREASING THE DEFAULT VM.MAX_MAP_COUNT VALUE
THE VM.MAX_MAP_COUNT PARAMETER WILL BE INCREASED FROM THE DEFAULT 65530 VALUE
TO 1048576.
THIS CHANGE SHOULD HELP ADDRESS PERFORMANCE, CRASH OR START-UP ISSUES FOR A
NUMBER OF MEMORY INTENSIVE APPLICATIONS, PARTICULARLY FOR (BUT NOT LIMITED TO)
SOME WINDOWS GAMES PLAYED THROUGH WINE/STEAM PROTON. OVERALL, END USERS SHOULD
HAVE A SMOOTHER EXPERIENCE OUT OF THE BOX WITH NO EXPRESSED CONCERNS ABOUT
POTENTIAL DOWNSIDES IN THE RELATED PROPOSAL ON ARCH-DEV-PUBLIC MAILING LIST.
THIS VM.MAX_MAP_COUNT INCREASE IS INTRODUCED IN THE 2024.04.07-1 RELEASE OF
THE FILESYSTEM PACKAGE AND WILL BE EFFECTIVE RIGHT AFTER THE UPGRADE.
BEFORE UPGRADING, IN CASE YOU ARE ALREADY SETTING YOUR OWN VALUE FOR THAT
PARAMETER IN A SYSCTL.D CONFIGURATION FILE, EITHER REMOVE IT (TO SWITCH TO THE
NEW DEFAULT VALUE) OR MAKE SURE YOUR CONFIGURATION FILE WILL BE READ WITH A
HIGHER PRIORITY THAN THE /USR/LIB/SYSCTL.D/10-ARCH.CONF FILE (TO SUPERSEDE THE
NEW DEFAULT VALUE).
=#=#=#=#=#=#=#=#=
THE XZ PACKAGE HAS BEEN BACKDOORED
UPDATE: TO OUR KNOWLEDGE THE MALICIOUS CODE WHICH WAS DISTRIBUTED VIA
THE RELEASE TARBALL NEVER MADE IT INTO THE ARCH LINUX PROVIDED BINARIES,
AS THE BUILD SCRIPT WAS CONFIGURED TO ONLY INJECT THE BAD CODE IN
DEBIAN/FEDORA BASED PACKAGE BUILD ENVIRONMENTS. THE NEWS ITEM BELOW CAN
THEREFORE MOSTLY BE IGNORED.
WE ARE CLOSELY MONITORING THE SITUATION AND WILL UPDATE THE PACKAGE AND
NEWS AS NECCESARY.
TL;DR: UPGRADE YOUR SYSTEMS AND CONTAINER IMAGES NOW!
AS MANY OF YOU MAY HAVE ALREADY READ (ONE), THE UPSTREAM RELEASE TARBALLS FOR
XZ IN VERSION 5.6.0 AND 5.6.1 CONTAIN MALICIOUS CODE WHICH ADDS A BACKDOOR.
THIS VULNERABILITY IS TRACKED IN THE ARCH LINUX SECURITY TRACKER (TWO).
THE XZ PACKAGES PRIOR TO VERSION 5.6.1-2 (SPECIFICALLY 5.6.0-1 AND 5.6.1-1)
CONTAIN THIS BACKDOOR.
THE FOLLOWING RELEASE ARTIFACTS CONTAIN THE COMPROMISED XZ:
INSTALLATION MEDIUM 2024.03.01
VIRTUAL MACHINE IMAGES 20240301.218094 AND 20240315.221711
CONTAINER IMAGES CREATED BETWEEN AND INCLUDING 2024-02-24 AND 2024-03-28
THE AFFECTED RELEASE ARTIFACTS HAVE BEEN REMOVED FROM OUR MIRRORS.
WE STRONGLY ADVISE AGAINST USING AFFECTED RELEASE ARTIFACTS AND INSTEAD
DOWNLOADING WHAT IS CURRENTLY AVAILABLE AS LATEST VERSION!
UPGRADING THE SYSTEM
IT IS STRONGLY ADVISED TO DO A FULL SYSTEM UPGRADE RIGHT AWAY IF YOUR SYSTEM
CURRENTLY HAS XZ VERSION 5.6.0-1 OR 5.6.1-1 INSTALLED:
PACMAN -SYU
UPGRADING CONTAINER IMAGES
TO FIGURE OUT IF YOU ARE USING AN AFFECTED CONTAINER IMAGE, USE EITHER
PODMAN IMAGE HISTORY ARCHLINUX/ARCHLINUX
OR
DOCKER IMAGE HISTORY ARCHLINUX/ARCHLINUX
DEPENDING ON WHETHER YOU USE PODMAN OR DOCKER.
ANY ARCH LINUX CONTAINER IMAGE OLDER THAN 2024-03-29 AND YOUNGER THAN
2024-02-24 IS AFFECTED.
RUN EITHER
PODMAN IMAGE PULL ARCHLINUX/ARCHLINUX
OR
DOCKER IMAGE PULL ARCHLINUX/ARCHLINUX
TO UPGRADE AFFECTED CONTAINER IMAGES TO THE MOST RECENT VERSION.
AFTERWARDS MAKE SURE TO REBUILD ANY CONTAINER IMAGES BASED ON THE AFFECTED
VERSIONS AND ALSO INSPECT ANY RUNNING CONTAINERS!
REGARDING SSHD AUTHENTICATION BYPASS/CODE EXECUTION
FROM THE UPSTREAM REPORT (ONE):
OPENSSH DOES NOT DIRECTLY USE LIBLZMA. HOWEVER DEBIAN AND SEVERAL OTHER
DISTRIBUTIONS PATCH OPENSSH TO SUPPORT SYSTEMD NOTIFICATION, AND LIBSYSTEMD
DOES DEPEND ON LZMA.
ARCH DOES NOT DIRECTLY LINK OPENSSH TO LIBLZMA, AND THUS THIS ATTACK VECTOR IS
NOT POSSIBLE. YOU CAN CONFIRM THIS BY ISSUING THE FOLLOWING COMMAND:
LDD "$(COMMAND -V SSHD)"
HOWEVER, OUT OF AN ABUNDANCE OF CAUTION, WE ADVISE USERS TO REMOVE THE
MALICIOUS CODE FROM THEIR SYSTEM BY UPGRADING EITHER WAY. THIS IS BECAUSE
OTHER YET-TO-BE DISCOVERED METHODS TO EXPLOIT THE BACKDOOR COULD EXIST.
=#=#=#=#=#=#=#=#=
MKINITCPIO HOOK MIGRATION AND EARLY MICROCODE
WITH THE RELEASE OF MKINITCPIO V38, SEVERAL HOOKS PREVIOUSLY PROVIDED BY ARCH
PACKAGES HAVE BEEN
MOVED TO THE MKINITCPIO UPSTREAM PROJECT. THE HOOKS ARE: SYSTEMD, UDEV,
ENCRYPT,
SD-ENCRYPT, LVM2 AND MDADM_UDEV.
TO ENSURE NO BREAKAGE OF USERS' SETUP OCCURS, TEMPORARY
CONFLICTS HAVE BEEN INTRODUCED INTO THE RESPECTIVE PACKAGES TO PREVENT
INSTALLING PACKAGES
THAT ARE NO LONGER COMPATIBLE.
THE FOLLOWING PACKAGES NEEDS TO BE UPGRADED TOGETHER:
MKINITCPIO 38-3
SYSTEMD 255.4-2
LVM2 2.03.23-3
MDADM 4.3-2
CRYPTSETUP 2.7.0-3
PLEASE NOTE THAT THE MKINITCPIO FLAG --MICROCODE, AND THE MICROCODE OPTION IN
THE PRESET FILES, HAS BEEN DEPRECATED IN FAVOUR OF
A NEW MICROCODE HOOK. THIS ALSO ALLOWS YOU TO DROP THE MICROCODE INITRD
LINES FROM YOUR BOOT CONFIGURATION AS THEY ARE NOW PACKED TOGETHER WITH THE
MAIN INITRAMFS IMAGE.
=#=#=#=#=#=#=#=#=
MAKING DBUS-BROKER OUR DEFAULT D-BUS DAEMON
WE ARE MAKING DBUS-BROKER OUR DEFAULT IMPLEMENTATION OF D-BUS, FOR
IMPROVED PERFORMANCE, RELIABILITY AND INTEGRATION WITH SYSTEMD.
FOR THE FORESEEABLE FUTURE WE WILL STILL SUPPORT THE USE OF DBUS-DAEMON,
THE PREVIOUS IMPLEMENTATION. PACMAN WILL ASK YOU WHETHER TO INSTALL
DBUS-BROKER-UNITS OR DBUS-DAEMON-UNITS. WE RECOMMEND PICKING THE
DEFAULT.
FOR A MORE DETAILED RATIONALE, PLEASE SEE OUR RFC 25.
=#=#=#=#=#=#=#=#=
+----------------------------------------------------------------------------+
ARGEN-X BBS FIDONET - TELNET ARGENX.KOZOW.COM PORT 23000
HYPERTEXT PREPROCESSOR - DEVELOPED BY LU9DCE - VERSION 3
前のメール | 次のメール