similar to: smbpasswd truncates password to 8 chars on Solaris sparc?

The current mitigation for CVE-2018-14634 is a systemtap script mentioned here: https://access.redhat.com/security/cve/cve-2018-14634 It also mentions that one can build a kernel module to distribute to other machines, but in any case one needs the corresponding debuginfo packages to do either. After enabling CentOS-Debug.repo, what I get is:

Two identical machines, both running CentOS 4.3 plus all the errata. First one: yum update went for a while and hung. At the bottom of the yum.log file was this: Aug 31 06:58:01 Updated: control-center.i386 1:2.8.0-12.rhel4.5 Aug 31 06:58:09 Updated: iiimf-le-unit.i386 1:12.1-13.EL.5 Aug The python process was in the process list, but it was consuming no CPU time. I let it go for a couple

Never had much trouble building on the Mac until this round. Trying to build 7.4p1 with openssl 1.0.2j on a MacOSX 10.12.2/3 machine. gcc --version returns clang-800.0.42.1. This is the latest Xcode. Builds fine. Upon running sshd, it seg faults with this in the logs: assertion failed 16C67: libsystem_trace.dynlib+76912 [5BD4ECD4-75CA-38EA-AF5C-B481C15955F8]: 0x0 If I run the tests, it

On Sun, Oct 28, 2018 at 03:54:06PM -0600, Zube wrote: > > Le 28/10/2018 ? 22:10, Albert McCann a ?crit?: > > > > Red Hat would stay as a distinct entity inside IBM. IBM has also > > contributed to Free software, and especially Linux kernel. > > I don't know how bad it is and the implications for CentOS... > > That old war wound started aching again. >

On Sat Oct 22 08:20:24 PM, Valeri Galtsev wrote: > I should have said CentOS 7. Older ones (CentOS 6 and 5) are not vulnerable. https://bugzilla.redhat.com/show_bug.cgi?id=1384344 Comment #35 points to a link that doesn't depend on /proc/self/mem and claims to work on CentOS 6 and 5. I'm not quite sure what I should be looking for when I run the program, though. I do hope Redhat

Twitter user stintel, in this thread: https://twitter.com/stintel/status/948499157282623488 mentions a possible problem with the new patches and the nvidia driver: "As if the @Intel bug isn't bad enough, #KPTI renders @nvidia driver incompatible due to GPL-only symbol 'cpu_tlbstate'. #epicfail" Also: https://twitter.com/tomasz_gwozdz/status/948590364679655429

Sorry for the bother, but is there any way to poke or prod or query dovecot so that it will reveal what version of SSL it is currently using? dovecot --build-options tells me that openssl is there, but not the version. ldd on any of the binaries in libexec comes up empty. I can get the version and what directory it is looking at by: strings ssl-params | grep -i ssl but that is kludgy.

On Tue Feb 16 03:35:06 PM, John R Pierce wrote: Thanks to both you and Mark Roth for chiming in and thank you for the lsi-raidinfo script. > On 2/16/2016 3:23 PM, Zube wrote: > >Does anyone know what program can be used to query the RAID status > >from the OS for an on-board LSI SAS 2308-4i? > > the 2308 isn't actually a megaraid, Right, that is in agreement with both

Good day. Thanks in advance for any help. I have a Tyan S2895 (Thunder K8WE) with 2 275 Opterons and the latest (1.02) bios. It appears to have an nVidia nForce SATA chipset which connects to a 250gb WD Caviar SATA drive. Using the CentOS 4 update 2 x86_64 DVD, the install is peachy until half-way through the "performing post install configuration" bit. Then it hangs forever. I

yum update was killed at an inopportune time, leaving ipa\* and xorg\* in an inconsistent state. yum-complete-transaction looks like it it's going to erase the entire system and then fails. >From the transaction files, the following are in: install 0:ipa-python-2.2.0-17.el6_3.1.x86_64 install 0:ipa-client-2.2.0-17.el6_3.1.x86_64 install

On 10/28/18 17:54, Zube wrote: > On Sun Oct 28 10:20:31 PM, Alain p?an wrote: > >> Le 28/10/2018 ? 22:10, Albert McCann a ?crit?: >>> Damn, this is bad enough to make one weep. >> >> Red Hat would stay as a distinct entity inside IBM. IBM has also >> contributed to Free software, and especially Linux kernel. >> I don't know how bad it is and the

On Wed Jan 03 07:43:04 PM, Phil Perry wrote: > > On CentOS 7 I'm running into an issue with the latest nvidia driver > > from elrepo: kmod-nvidia-384.98-1.el7_4.elrepo.x86_64 > > This driver version seem to introduce issue in detecting video modes > > when a monitor is connected using DVI. As soon as the machine attempts > > to start X, nothing happens and the

Back in January/March of 2017, it was the case that building openssh with the latest openssl on MacOS 10.12.x (Sierra) was a bit of a bother. I could build everything with Xcode, but the resulting sshd segfaulted upon invocation (see the archives). So I built gcc 6.3 and used that to build openssh 7.x on Sierra. As long as machines stayed on 10.12.x, all was fine. Under High Sierra, the Xcode

Downloaded 6.8 DVD1.iso, dd to stick. Went through same selections I have gone through since 6.2, only this time it got to the end and stated it couldn't find rear, which is under "backup client". OK, try it again without rear. This time it's yum-plugin-ovl from base (?). Then chrony, also in base (?). Then flightrecorder, libreswan, at least 2 of openmpi & co. and

Failure on Solaris 9 sparc: Undefined first referenced symbol in file seed_rng openbsd-compat//libopenbsd-compat.a(bsd-arc4random.o) ld: fatal: Symbol referencing errors. No output written to ssh-pkcs11-helper collect2: ld returned 1 exit status gmake: *** [ssh-pkcs11-helper] Error 1

All tests ok on SNAP-20080707, Solaris 9 sparc, gcc 3.4.6. Zube

After the patch recently posted, Solaris 9 sparc, gcc 3.4.6: "all tests passed" Thank you for the quick patch. Zube

On Thu, Jan 4, 2018 at 5:22 AM, Phil Perry <pperry at elrepo.org> wrote: > On 03/01/18 20:14, Zube wrote: >> >> I can confirm that this happens with the driver downloaded from NVIDIA. >> I had to fall back to the .90 driver to get it to work for all my >> NVS 315s (with dual DVI) running on 7.4 / 6.9. Thanks. For reference, I did the same test. With the driver

Does anyone know what program can be used to query the RAID status from the OS for an on-board LSI SAS 2308-4i? On this page: http://docs.avagotech.com/docs/12351997 there is a curious note on the left that reads: "Integrated MegaRAID support available upon request" After one mostly fruitless round of chatting with LSI/Avago/Broadcom and one completely fruitless round of chatting

On Thu, Jan 4, 2018 at 9:40 PM, Phil Perry <pperry at elrepo.org> wrote: > Normally elrepo only releases the long term branch for Enterprise Linux, on > the assumption EL users will welcome the implied stability over more > frequent and potentially buggy releases. > In this case I had built the current short lived release as a user requested > it for compatibility with the