Now I finally got the sqlite database initialized.
sqlite> .schema
CREATE TABLE Version (number REAL);
CREATE TABLE Principal (id INTEGER PRIMARY KEY, principal TEXT UNIQUE NOT
NULL, canonical INTEGER, entry INTEGER);
CREATE TABLE Entry (id INTEGER PRIMARY KEY, data BLOB);
CREATE TRIG
The more I look at how the database backends are compiled in and
tested, the more puzzled I get.
1. Question:
When compiling with:
$ ../heimdal-7.1.0/configure --with-libintl
--with-libintl-include=/usr/local/include --with-libintl-lib=/usr/local/lib
--prefix=/usr/heimdal-7.1.0-lmdb --disable
> So, in /etc/krb5.conf you should have this:
>
> [hdb]
> db-dir = /var/heimdal
>
> (or wherever you put your HDB)
Sure, and then it gets more and more confusing. I now start the
kdc and the kadmin with -c /etc/krb5.conf and have a symlink
in /var/heimdal/kdc.conf pointing to /etc/krb5.conf
>> For good measure I'll be running tests in a tree built with ./configure
>> --with-db-preference=sqlite, which should have the effect of using a
>> SQLite3 HDB in tests/kdc/check-kadmin.
>
> I had to modify tests/kdc/krb5.conf.in to make real sure it used the
> sqlite backend, but other than th
Fine by me. Only value I see is being able to use a client krb5.conf on a kdc,
which IMO doesn't justify the extra complexity.
Personal email. hbh...@oxy.edu
> On Dec 23, 2016, at 1:18 PM, Nico Williams wrote:
>
> Can we also not just also deprecate kdc.conf?
On Thu, Dec 22, 2016 at 03:18:28PM -0800, Henry B (Hank) Hotz, CISSP wrote:
> > On Dec 22, 2016, at 8:53 AM, Jeffrey Hutzelman wrote:
> [. . .]
>
> > kadmin -l is not a kdc and probably does not read kdc.conf. I've not
> > looked at the current code to see how much of this was resolved, but we
> On Dec 22, 2016, at 8:53 AM, Jeffrey Hutzelman wrote:
[. . .]
> kadmin -l is not a kdc and probably does not read kdc.conf. I've not looked
> at the current code to see how much of this was resolved, but we used to have
> to patch a bunch of places to get kadmin -l and a bunch of the serve
For good measure I'll be running tests in a tree built with ./configure
--with-db-preference=sqlite, which should have the effect of using a
SQLite3 HDB in tests/kdc/check-kadmin.
On Thu, Dec 22, 2016 at 04:21:59PM -0600, Nico Williams wrote:
> For good measure I'll be running tests in a tree built with ./configure
> --with-db-preference=sqlite, which should have the effect of using a
> SQLite3 HDB in tests/kdc/check-kadmin.
I had to modify tests/kdc/krb5.conf.in to make re
On Thu, Dec 22, 2016 at 09:32:16PM +0100, Harald Barth wrote:
> > kadmin -l is not a kdc and probably does not read kdc.conf. I've not
> > looked at the current code to see how much of this was resolved, but
> > we used to have to patch a bunch of places to get kadmin -l and a
> > bunch of the serv
> kadmin -l is not a kdc and probably does not read kdc.conf. I've not
> looked at the current code to see how much of this was resolved, but
> we used to have to patch a bunch of places to get kadmin -l and a
> bunch of the servers to read kdc.conf.
That's why I copied it to /etc/krb5.conf but I
On Thu, 22 Dec 2016, Harald Barth wrote:
>
> > kadmin -l is not a kdc and probably does not read kdc.conf. I've not
> > looked at the current code to see how much of this was resolved, but
> > we used to have to patch a bunch of places to get kadmin -l and a
> > bunch of the servers to read kdc.c
On December 22, 2016 8:25:08 AM EST, Harald Barth wrote:
>
>I have "limited" (read "so far no") success in running heimdal with
>the sqlite db backend.
>
>I'm trying to get the sqlite backend to work lik this in
>/etc/krb5.conf and /var/heimdal/kdc.conf:
>
>[kadmin]
> database = {
>dbname = sq
> Or what alternate backend do think is solid and stable and why? ;-)
> I am not planning to use ldap =;-)
With Heimdal 7.1, you can use LMDB as the backend, the same backend behind
OpenLDAP's back-mdb database storage.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packa
I have "limited" (read "so far no") success in running heimdal with
the sqlite db backend.
I'm trying to get the sqlite backend to work lik this in
/etc/krb5.conf and /var/heimdal/kdc.conf:
[kadmin]
database = {
dbname = sqlite:/var/heimdal/heimdal.sqlite
realm = TEST
}
require_preaut
15 matches
Mail list logo
