On 2/12/19 10:55 PM, Alice Wonder wrote:
DNSSEC keys do not expire. Signatures do expire. How long a signature
is good for depends upon the software generating the signature, some
lets you specify. ldns I believe defaults to 60 days but I am not sure.
The keys are in DNSSKEY records that
On 2/12/19 7:26 PM, Paul R. Ganci wrote:
Last weekend I had my DNSSEC keys expire. I discovered that they had
expired the hard way... namely randomly websites could not be found and
email did not get delivered. It seems that the keys were only valid for
what I estimate was about 30 days. It is
Last weekend I had my DNSSEC keys expire. I discovered that they had
expired the hard way... namely randomly websites could not be found and
email did not get delivered. It seems that the keys were only valid for
what I estimate was about 30 days. It is a real PITA to have update the
keys,
On Tue, Feb 12, 2019 at 9:39 PM Rob Kampen
wrote:
> On 13/02/19 2:05 PM, Sean Son wrote:
> > Hello all
> >
> > First off, I am running Oracle Linux 7.6 on a Hyper-V 2016 VM for a
> > customer. I know this is not an Oracle Linux mailling list, but because
> > Oracle Linux and CentOS are so
On 13/02/19 2:05 PM, Sean Son wrote:
Hello all
First off, I am running Oracle Linux 7.6 on a Hyper-V 2016 VM for a
customer. I know this is not an Oracle Linux mailling list, but because
Oracle Linux and CentOS are so similar, to an extent, I figured why not ask
on here because someone MIGHT
Hello all
First off, I am running Oracle Linux 7.6 on a Hyper-V 2016 VM for a
customer. I know this is not an Oracle Linux mailling list, but because
Oracle Linux and CentOS are so similar, to an extent, I figured why not ask
on here because someone MIGHT know the answer.. Here is the issue. I
Hey all,
In this week's Open Source Highlights I read:
"Check ink level: If you have an Epson, Canon, HP, or Sony printer, you
can see its ink level with a simple application. Look for the "ink"
package in your distribution repositories."
I checked my package manager but I didn't find any
On Tue, Feb 12, 2019 at 01:47:43PM -0800, Paul Heinlein wrote:
> That asterick where 040 (and its contents) should be is worrisome
> to me. To my eye, something is amiss.
In the 'hexdump' and 'od' utilities, the '*' means a duplicate line
was suppressed. From od(1):
-v,
On Tue, 12 Feb 2019, Brian Reichert wrote:
First off, I have to admit that I'm uncertain if this is the
appropriate forum; I'd be happy for suggestions about where else
to look.
I'm doing this work on a stock install of CentOS-7-x86_64-Minimal-1810.iso,
with no updates.
I'm trying to create
Good evening,
my final solution:
SUBSYSTEM=="scsi_generic", SUBSYSTEMS=="scsi", ATTRS{type}=="8",
ATTRS{model}=="MAGNUM 224 ", IMPORT{program}="scsi_id
--sg-version=3 --export --whitelisted -d $devnode", \
SYMLINK+="changer0"
SUBSYSTEM=="scsi_generic", SUBSYSTEMS=="scsi",
First off, I have to admit that I'm uncertain if this is the
appropriate forum; I'd be happy for suggestions about where else
to look.
I'm doing this work on a stock install of CentOS-7-x86_64-Minimal-1810.iso,
with no updates.
I'm trying to create an RPM database from a custom set of RPMs.
One
Hi,
builds fixing CVE-2019-5736 in runc and docker are in cbs:
https://cbs.centos.org/koji/buildinfo?buildID=25142
https://cbs.centos.org/koji/buildinfo?buildID=25136
The security flaw is quite severe. Please, what should be done? I am not
very well versed in the processes and do not want to
On 2/12/19 4:57 AM, Leon Fauster via CentOS wrote:
I have some cron.d entries that execute scripts in minute intervals and I'm
wondering how could an
"official" way look like, to have a condition to not run cron.d entries when
cron.daily scripts are
running. Sure, I can hack something around
Well, this is anything but elegant, but if your daily occurs at an exact hour
and minute you could write two series of per minute cron jobs (a "before' and
an "after") avoiding that minute.
Leroy Tennison
Network Information/Cyber Security Specialist
E: le...@datavoiceint.com
2220 Bush Dr
EL6 context:
cronie-1.4.4-16.el6_8.2.x86_64
cronie-anacron-1.4.4-16.el6_8.2.x86_64
crontabs-1.10-33.el6.noarch
I have some cron.d entries that execute scripts in minute intervals and I'm
wondering how could an
"official" way look like, to have a condition to not run cron.d entries when
> On Mon, Feb 11, 2019 at 04:16:38PM +0100, Simon Matter via CentOS wrote:
>> > Hi all!
>> >
>> > I'm a "nervous nellie", I have not yet updated my 7.5 desktop to 7.6
>> > because (1) it has an Nvidia card, and (2) I've heard of problems
>> > upgrading on top of software RAID (using RAID1 with 2
16 matches
Mail list logo
