Randy Bush via Opendnssec-user writes:
> /etc/syslog.conf
>
> !opendnssec
> local2.* /var/log/signer
>
Actyally, one needs something like:
!*
:programname, regex, "^ods.*"
local2.*/var/log/signer
jaap
PS. I too hate syslog.conf
___
Randy Bush via Opendnssec-user writes:
> > no binary package yet. jaap! puhleeze! making from source drags in
> > massively
>
> and pulls softhsm2; and i had a massive mess last time i tried to
> upgrade from v1
>
When building port, pulling in softhsm is optional (and default it
is off
Randy Bush via Opendnssec-user writes:
> >> # uname -a
> >> FreeBSD rip.psg.com 12.2-RELEASE-p6 FreeBSD 12.2-RELEASE-p6 GENERIC
> >> amd64
>
> > OpenDNSSEC 2.1.9 is out, which solves this issue I think.
>
> no binary package yet. jaap! puhleeze! making from source drags in
> massively
Roman Serbski via Opendnssec-user writes:
Among others things:
>
> I see that the new 2.1.8 has been released yesterday which mentions a
> fix to keys not being purged from the HSM, although I'm not sure it's
> our case.
To prevent possible confusion, let me clarify. A release candidate
(2.1
Roman Serbski via Opendnssec-user writes:
> Hello,
>
> It's probably more FreeBSD related, but any hints would be greatly
> appreciated.
Yeah, you cab kind of blame FreeBSD.
The port uses an old version of botan, and apparently not a lot of
people uses softhsm2 with botan. I actually don't
Ondřej Surý writes:
> networks, mounts are ok, but how you are going to make sure that a
> remote MySQL server is available from within a local init system?
>
> > Is it unreasonable for OpenDNSSEC to require certain resources to be
> > available before starting?
>
> With remote MySQL you
"Fred.Zwarts" writes:
> Thanks for your response. So, I was at the right track, but the version of
> SoftHSM2 that is currently released, does not yoet support a migration from
> SoftHSM v1. I will wait for a new release of SoftHSM that will support the
> migration. Any idea when we can ex
Jakob Schlyter writes:
> On 30 mar 2015, at 13:13, Jaap Akkerhuis wrote: >
> > Are there any plans to have support for a LibreSSL backend? That >
> probably will mean sacrificing support for gost but apparently some >
> people want that.
>
> Does the curre
Are there any plans to have support for a LibreSSL backend? That
probably will mean sacrificing support for gost but apparently some
people want that.
jaap
___
Opendnssec-user mailing list
Opendnssec-user@lists.opendnssec.org
https://lists.opendn
Paul Wouters writes:
> On Fri, 20 Feb 2015, Patrik Wallström wrote:
>
> >> I'm not sure what caused this. The disk was not full and still has 1Gb
> >> of free space.
> >
> > You didn’t have a backup?
>
> I do, but sadly it does not contain all the current ZSKs. Not the end of
> the wor
I can ask Fedora maintainer for a new Fedora build but I would like to know
what should we can expect. Does it work? :-)
I haven't done any extensive testing, I'm probably not the right person
to answer this.
jaap
___
Opendnssec
I quickly went through tickets on
https://issues.opendnssec.org/browse/SOFTHSM
but I'm not sure if I got the overall picture right.
If I say that performance is not very interesting for me, how
reliable is i t? When it crashes, how likely is database
corruption? (I
Jerry,
Should be no problem. We have been running 1.10 for testing on several
platforms a long while now. See
https://wiki.opendnssec.org/pages/viewpage.action?pageId=3D2064460 .
Good to know, thanks. There is an idea to retired the olde botan 1.8.5 and
use 1.10.x. The port b
Evening,
Inquiring minds want to know, is there positive experience in using
botan version 1.10 with softhsm?
Thanks in advance,
jaap
___
Opendnssec-user mailing list
Opendnssec-user@lists.opendnssec.org
https://lists.opendnssec.org/mailman/lis
Also If I add
ods-signer sign me.ne.mm
only in crontab it does not work either
This smells to a crontab issue, not opendnssec.
The default PATH in crontab is limited (/bin:/usr/bin normally)
Use an abslute path to where ods-signer lives or add
PATH=$PATH:/path-to
Yes, that is in the time plan. But first we need to get the
fundamental PKCS#11 support in place for SoftHSM v2. Then we have the
issue: https://issues.opendnssec.org/browse/SOFTHSM-9
It is my personal preference to keep the documentation up to date,
eve during development. I've s
I have now increased the required version to 1.10.0. Because the 1.9.*
was the development release for 1.10.
You probably want that to be documented in the README as well.
jaap
___
Opendnssec-user mailing list
Opendnssec-user@li
Is sqlite3 version 3.3.9 required for OpenDNSSEC 1.3? On Redhat
5. I have sqlite version 3.3.6, will that work too?
Check the release notes but I think you want 3.4.2 or higher.
jaap
___
Opendnssec-user mailing list
Opendnssec-user
For those that care, this version just made in to the BSD ports.
jaap
___
Opendnssec-user mailing list
Opendnssec-user@lists.opendnssec.org
https://lists.opendnssec.org/mailman/listinfo/opendnssec-user
Being brought up with the nostrum that no *nix tools exist unless
there are manual pages, it is great to see manual pages for opendnssec
tools. Thanks!
There is another small whish I have. te menual pages have absolute path
name in them as in:
(defaults to /etc/opendnssec/conf.xml)
Would
20 matches
Mail list logo
