search for: numachi

...wondering if Fedora maintains local changes to the SYSLINUX project. If it does, that further lends to my interest in tracking down the utilized sources. Does anyone have any insight on these topics, or, at the very least, a better forum to pursue them? -- Brian Reichert <reichert at numachi.com> BSD admin/developer at large

...39;s good to know. I'm curious about satisfying the obligations of redistributing GPL software. I'll try to trace down the details of this buildinstall process, so I can try to track down where the associated source is provided by the CentOS project. -- Brian Reichert <reichert at numachi.com> BSD admin/developer at large

...roduce > the syslinux RPMs, which when installed provide the binary file in question. Cool! That makes perfect sense to me, and satisfies all of my original points/questions. Thanks again; make my research much easier. :) > Thanks, > Johnny Hughes -- Brian Reichert <reichert at numachi.com> BSD admin/developer at large

...rk with the related bits for CentOS 6. Here are some details of my environment; I'm happy to provide more, if anyone has any questions: $ cat /etc/redhat-release CentOS Linux release 7.6.1810 (Core) $ rpm -qf /usr/bin/rpm rpm-4.11.3-35.el7.x86_64 -- Brian Reichert <reichert at numachi.com> BSD admin/developer at large

...n what I can for that, for CentOS 6... > -- > Jonathan Billings <billings at negate.org> > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos -- Brian Reichert <reichert at numachi.com> BSD admin/developer at large

Hello. I once read somewhere that it's possible to limit SSH pubkeys to 'tunnel-only'. I can't seem to find any information about this in any of the usual places. I'm going to be deploying a few servers in a couple of days and I'd like them to log to a central server over an SSH tunnel (using syslog-ng) however I'd like to prevent actual logins (hence

...ils of my environment, if that's helpful: [root at 172-20-245-145 ~]# cat /etc/redhat-release CentOS release 6.5 (Final) [root at 172-20-245-145 ~]# rpm -q yum rpm yum-3.2.29-69.el6.centos.noarch rpm-4.8.0-37.el6.x86_64 Thanks for any advice... -- Brian Reichert <reichert at numachi.com> BSD admin/developer at large

I'm forwarding this to security@, as I'm getting no replies on ipfw@. Hope it's relevant enough for you :( ---Original Message----- From: owner-freebsd-ipfw@freebsd.org [mailto:owner-freebsd-ipfw@freebsd.org] On Behalf Of Erik Paulsen Skålerud Sent: Wednesday, May 28, 2003 1:02 AM To: ipfw@freebsd.org Subject: Question about logging. Sorry for asking this, It's probably been

...gt; > > http://vault.centos.org/6.7/os/Source/SPackages/syslinux-4.04-3.el6.src.rpm Related question; where do these files come from? http://mirror.centos.org/centos/6/os/x86_64/EFI/BOOT/ I think they're grub-related, but can't prove that... -- Brian Reichert <reichert at numachi.com> BSD admin/developer at large

...happen, and there's no dialog to the contrary. I was able to extract that scriptlet, and run it in the chrooted environment successfully. Is there something about anaconda-yum under CentOS 7 that does something counterintuitive WRT %posttrans scriptlets? -- Brian Reichert <reichert at numachi.com> BSD admin/developer at large

I am running the stock OpenLDAP-servers on a CentOS 6 system. Everything is working just fine, but I am trying to debug connections from a Ubuntu (18.04) system and want to turn on logging in slapd, but although I can get slapd to create a log file, it never actually writes anything. I have these two lines in /etc/openldap/slapd.d/cn=config.ldif: olcLogFile: /var/log/slapd/log olcLogLevel:

Back in February, I opened two bugs, that seem to have had no activity: https://bugs.centos.org/view.php?id=15850 https://bugs.centos.org/view.php?id=15846 Is there some step I skipped when creating these? Or am I being impatient? :) -- Brian Reichert <reichert at numachi.com> BSD admin/developer at large

I have asked this before in -questions but due to a odd security requirement, I need the option to auto lock a normal user's account (root and those in the wheel group must be excluded) after let say, 3, login failures. I know this can cause a DoS issue but I HAVE to have the option of doing it in FreeBSD. Any info is appreciated Thanks. Mike C carlson39@llnl.gov

These source addresses are likely spoofed, but am still curious whether other FreeBSD admins saw a preponderance of DNS probes originating from Microsoft corp subnets ahead of the recent ISC bind vulnerability announcement? Roger Marquis Jul 28 16:51:23 PDT named[...]: client 94.245.67.253#10546: query (cache) 'output.txt/A/IN' denied Jul 28 16:51:23 PDT named[...]: client

Hi, I am looking for an offline accounting package recommendation, please. I enjoyed using Xero accounting, but need something that's offline, and where the data remains my property. Having used Quickbooks on Windows in the past, I am looking for something similar. Any recommendations? -- Kind Regards Rudi Ahlers Website: http://www.rudiahlers.co.za

HI all, When CentOS 7 was created things like SSLv2 TLSv1 TLSv1.1 etc... were all OK, but now they have fallen out of favor for various reasons. Updating to CentOS 7.7 does not automatically disable these types of items from apache - is there a script that is available that can be ran to bring a box up to current "accepted" levels ? Or is that an edit by hand, do it yourself on all your

There may be ways to force NIC naming, I've done so but only on Ubuntu so you'll need to do the research if it's important to you. Things to look for based on my experience: 70-persistent-net.rules, net.ifnames=0, biosdevname=0. ________________________________ From: CentOS <centos-bounces at centos.org> on behalf of Nicolas Kovacs <info at microlinux.fr> Sent: Sunday,

Hi, Sometimes, I found one of my Mellanox NIC renamed to rename6, instead of eth1. The right names of NICs in my system should be: eth0 Mellanox NIC eth1 Mellanox NIC eth2 Intel NIC eth3 Intel NIC eth4 Intel NIC eth5 Intel NIC eth0 and eth1 will combined as bond1 with mode 4. However, the current names are: eth0 Mellanox

On 10/13/2015 01:40 PM, Brian Reichert wrote: > On Tue, Oct 13, 2015 at 12:51:07PM -0400, Brian Reichert wrote: >> On Tue, Oct 13, 2015 at 11:42:08AM -0500, Johnny Hughes wrote: >>> The info you are looking at there is for CentOS-7 .. the syslinux for >>> CentOS-6 is here: >>> >>>

Good Day! I think we have a serious problem. One of our old server running FreeBSD 4.9 have been compromised and is now connected to an ircd server.. 195.204.1.132.6667 ESTABLISHED However, we still haven't brought the server down in an attempt to track the intruder down. Right now we are clueless as to what we need to do.. Most of our servers are running legacy operating systems(old