mirror of
git://slackware.nl/current.git
synced 2024-11-18 10:08:17 +01:00
6a63f41b3b
Hey folks! PAM has finally landed in /testing. Some here wanted it to go right into the main tree immediately, and in a more normal development cycle I'd have been inclined to agree (it is -current, after all). But it's probably better for it to appear in /testing first, to make sure we didn't miss any bugs and also to serve as a warning shot that we'll be shaking up the tree pretty good over the next few weeks. I'd like to see this merged into the main tree in a day or two, so any testing is greatly appreciated. Switching to the PAM packages (or reverting from them) is as easy as installing all of them with upgradepkg --install-new, and if reverting then remove the three leftover _pam packages. After reverting, a bit of residue will remain in /etc/pam.d/ and /etc/security/ which can either be manually deleted or simply ignored. While there are many more features available in PAM compared with plain shadow, out of the box about the only noticable change is the use of cracklib and libpwquality to check the quality of a user-supplied password. Hopefully having PAM and krb5 will get us on track to having proper Active Directory integration as well as using code paths that are likely better audited these days. The attack surface *might* be bigger, but it's also a lot better scrutinized. Thanks to Robby Workman and Vincent Batts who did most of the initial heavy lifting on the core PAM packages as a side project for many years. Thanks also to Phantom X whose PAM related SlackBuilds were a valuable reference. And thanks as well to ivandi - I learned a lot from the SlackMATE build scripts and was even occasionally thankful for the amusing ways you would kick my ass on LQ. ;-) You're more than welcome to let us know where we've messed up this time. The binutils and glibc packages in /testing were removed and are off the table for now. I'm not seeing much upside to heading down that rabbit hole at the moment. Next we need to be looking at Xfce 4.14 and Plasma 5.18 LTS and some other things that have been held back since KDE4 couldn't use them. Cheers! :-) a/kernel-generic-5.4.19-x86_64-1.txz: Upgraded. a/kernel-huge-5.4.19-x86_64-1.txz: Upgraded. a/kernel-modules-5.4.19-x86_64-1.txz: Upgraded. a/lvm2-2.03.08-x86_64-1.txz: Upgraded. a/shadow-4.8.1-x86_64-2.txz: Rebuilt. Automatically backup /etc/login.defs and install the new version if incompatible PAM options are detected. d/kernel-headers-5.4.19-x86-1.txz: Upgraded. k/kernel-source-5.4.19-noarch-1.txz: Upgraded. VALIDATE_FS_PARSER y -> n xap/mozilla-thunderbird-68.5.0-x86_64-1.txz: Upgraded. This release contains security fixes and improvements. For more information, see: https://www.mozilla.org/en-US/thunderbird/68.5.0/releasenotes/ https://www.mozilla.org/en-US/security/advisories/mfsa2020-07/ https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6793 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6794 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6795 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6797 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6798 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6792 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6800 (* Security fix *) isolinux/initrd.img: Rebuilt. kernels/*: Upgraded. testing/packages/PAM/ConsoleKit2-1.2.1-x86_64-1_pam.txz: Added. testing/packages/PAM/at-3.2.1-x86_64-1_pam.txz: Added. testing/packages/PAM/cifs-utils-6.10-x86_64-2_pam.txz: Added. testing/packages/PAM/cracklib-2.9.7-x86_64-1_pam.txz: Added. testing/packages/PAM/cups-2.3.1-x86_64-1_pam.txz: Added. testing/packages/PAM/cyrus-sasl-2.1.27-x86_64-2_pam.txz: Added. testing/packages/PAM/dovecot-2.3.9.2-x86_64-1_pam.txz: Added. testing/packages/PAM/gnome-keyring-3.34.0-x86_64-1_pam.txz: Added. testing/packages/PAM/hplip-3.19.12-x86_64-2_pam.txz: Added. testing/packages/PAM/kde-workspace-4.11.22-x86_64-6_pam.txz: Added. testing/packages/PAM/libcap-2.31-x86_64-1_pam.txz: Added. testing/packages/PAM/libcgroup-0.41-x86_64-5_pam.txz: Added. testing/packages/PAM/libpwquality-1.4.2-x86_64-1_pam.txz: Added. testing/packages/PAM/mariadb-10.4.12-x86_64-1_pam.txz: Added. testing/packages/PAM/netatalk-3.1.12-x86_64-2_pam.txz: Added. testing/packages/PAM/netkit-rsh-0.17-x86_64-2_pam.txz: Added. testing/packages/PAM/openssh-8.1p1-x86_64-1_pam.txz: Added. testing/packages/PAM/openvpn-2.4.8-x86_64-1_pam.txz: Added. testing/packages/PAM/pam-1.3.1-x86_64-1_pam.txz: Added. testing/packages/PAM/polkit-0.116-x86_64-1_pam.txz: Added. testing/packages/PAM/popa3d-1.0.3-x86_64-3_pam.txz: Added. testing/packages/PAM/ppp-2.4.7-x86_64-3_pam.txz: Added. testing/packages/PAM/proftpd-1.3.6b-x86_64-1_pam.txz: Added. testing/packages/PAM/samba-4.11.6-x86_64-1_pam.txz: Added. testing/packages/PAM/screen-4.8.0-x86_64-1_pam.txz: Added. testing/packages/PAM/shadow-4.8.1-x86_64-2_pam.txz: Added. testing/packages/PAM/sudo-1.8.31-x86_64-1_pam.txz: Added. testing/packages/PAM/system-config-printer-1.5.12-x86_64-2_pam.txz: Added. testing/packages/PAM/util-linux-2.35.1-x86_64-1_pam.txz: Added. testing/packages/PAM/vsftpd-3.0.3-x86_64-5_pam.txz: Added. testing/packages/PAM/xdm-1.1.11-x86_64-9_pam.txz: Added. testing/packages/PAM/xlockmore-5.62-x86_64-1_pam.txz: Added. testing/packages/PAM/xscreensaver-5.43-x86_64-1_pam.txz: Added. testing/packages/binutils-2.34-x86_64-1.txz: Removed. testing/packages/glibc-2.31-x86_64-1.txz: Removed. testing/packages/glibc-i18n-2.31-x86_64-1.txz: Removed. testing/packages/glibc-profile-2.31-x86_64-1.txz: Removed. testing/packages/glibc-solibs-2.31-x86_64-1.txz: Removed. usb-and-pxe-installers/usbboot.img: Rebuilt. |
||
---|---|---|
.. | ||
sbootmgr | ||
f2.txt | ||
iso.sort | ||
isolinux.cfg | ||
message.txt | ||
README.TXT | ||
README_SPLIT.TXT | ||
setpkg |
HOW TO MAKE A BOOTABLE SLACKWARE DVD ISO IMAGE To make a bootable Slackware install DVD, get into the top level Slackware directory (The one with ChangeLog.txt in it) and issue a command like this to build the ISO image in /tmp: xorriso -as mkisofs \ -iso-level 3 \ -full-iso9660-filenames \ -R -J -A "Slackware Install" \ -hide-rr-moved \ -v -d -N \ -eltorito-boot isolinux/isolinux.bin \ -eltorito-catalog isolinux/boot.cat \ -no-emul-boot -boot-load-size 4 -boot-info-table \ -isohybrid-mbr /usr/share/syslinux/isohdpfx.bin \ -eltorito-alt-boot \ -e isolinux/efiboot.img \ -no-emul-boot -isohybrid-gpt-basdat \ -m 'source' \ -volid "SlackDVD" \ -output /tmp/slackware-dvd.iso \ . On my system, here's the command I'd use to burn the resulting DVD ISO: growisofs -speed=2 -dvd-compat -Z /dev/sr0=slackware-dvd.iso If your burner is not /dev/sr0, replace the device with the one your system uses. I find discs burned at 2x are more reliable than ones burned at higher speeds, but you may see completely different results depending on media and burner type. The -dvd-compat option is also used so that a complete lead-out is written to the media for maximum compatibility. To write the ISO image to a USB stick use a command such as this (replace /dev/sdX with the device name for your USB stick): dd if=/tmp/slackware-dvd.iso of=/dev/sdX bs=1M Or, you can burn directly from the Slackware tree to a DVD(-/+)R(W): xorriso -as mkisofs \ -iso-level 3 \ -full-iso9660-filenames \ -R -J -A "Slackware Install" \ -hide-rr-moved \ -v -d -N \ -eltorito-boot isolinux/isolinux.bin \ -eltorito-catalog isolinux/boot.cat \ -no-emul-boot -boot-load-size 4 -boot-info-table \ -isohybrid-mbr /usr/share/syslinux/isohdpfx.bin \ -eltorito-alt-boot \ -e isolinux/efiboot.img \ -no-emul-boot -isohybrid-gpt-basdat \ -m 'source' \ -volid "SlackDVD" \ -output - \ . \ | xorrecord -v dev=/dev/sr0 speed=2 fs=8m blank=as_needed - Note that the source code directory will not be included on these DVD images in order to keep them under the limit for a single-layer disc. If you are using double layer DVD media and want to burn the complete tree to your disc, remove the -m option line from the command. HOW TO MAKE A SET OF BOOTABLE / INSTALLABLE CDROMS This is a little bit more tricky. Step one will be to split the tree into portions that will fit on the media that you plan to burn to. The first disc must contain these directories: /isolinux/ /kernels/ /slackware/ You'll need to make other /slackware/ directories on discs 2, 3, and maybe more, moving some of the disc series from disc 1 to other discs to make things fit. It is also possible to split a series to make more efficient use of the CD media. See the README_SPLIT.TXT example and instructional file in this directory for details about how to set that up. The rest of the splitting up of discs is left as an exercise for the reader. To make the first (bootable) ISO, a command like this is used within the directory where the disc tree is. Let's say the directory is 'd1' and you wish to output the ISO image in /tmp: cd d1 xorriso -as mkisofs \ -iso-level 3 \ -full-iso9660-filenames \ -R -J -A "Slackware Install 1" \ -hide-rr-moved \ -v -d -N \ -eltorito-boot isolinux/isolinux.bin \ -eltorito-catalog isolinux/boot.cat \ -no-emul-boot -boot-load-size 4 -boot-info-table \ -isohybrid-mbr /usr/share/syslinux/isohdpfx.bin \ -eltorito-alt-boot \ -e isolinux/efiboot.img \ -no-emul-boot -isohybrid-gpt-basdat \ -volid "SlackCD1" \ -output /tmp/slackware-install-1.iso \ . Making a non-bootable disc is similar. Just omit a few options: cd d2 xorriso -as mkisofs \ -iso-level 3 \ -full-iso9660-filenames \ -R -J -A "Slackware Install 2" \ -hide-rr-moved \ -v -d -N \ -volid "SlackCD2" \ -output /tmp/slackware-install-2.iso \ . To burn an ISO image to CD-R(W), the cdrecord command is used. For complete instructions, see the man page ('man cdrecord'). On my own machine where the burner is /dev/cdrw, disc one would be burned with the following command: cat /tmp/slackware-install-1.iso | cdrecord -v dev=/dev/cdrw speed=10 fs=8m -tao -eject -data - As before, it's possible to burn from the disc trees without the intermediate step of creating iso images by piping the output directly to cdrecord: cd d1 xorriso -as mkisofs \ -iso-level 3 \ -full-iso9660-filenames \ -R -J -A "Slackware Install 1" \ -hide-rr-moved \ -v -d -N \ -eltorito-boot isolinux/isolinux.bin \ -eltorito-catalog isolinux/boot.cat \ -no-emul-boot -boot-load-size 4 -boot-info-table \ -isohybrid-mbr /usr/share/syslinux/isohdpfx.bin \ -eltorito-alt-boot \ -e isolinux/efiboot.img \ -no-emul-boot -isohybrid-gpt-basdat \ -volid "SlackCD1" \ -output - \ . | cdrecord -v dev=/dev/cdrw speed=10 fs=8m -tao -eject -data - ----- NOTES: The isolinux/isolinux.boot file will be created on the disc; it's not supposed to be in the source tree. I mention this only because so many people report the "missing" isolinux/isolinux.boot file as a bug. The "-boot-load-size 4" is actually not large enough to hold the isolinux boot loader, but many BIOS implementations are broken and will *only* accept "4". Evidently many newer, more correct BIOS implementations expect this and will continue to load the boot loader file until the EOF is reached. Anyway, previous uses of larger values were correct, but led to the Slackware ISO not booting on some machines which contained broken BIOS implementations. It is my hope that by using the incorrect value of 4 sectors that the ISO will boot on most (if not all) machines that are supposed to be able to boot from an ISO image. I don't know how to create a bootable Slackware ISO on operating systems other than Linux, but it should be easy to burn the Linux-created ISO with most CD burning software on any operating system. Enjoy! -P.