Age | Commit message (Collapse) | Author |
|
apache log instead.
Make the GUI log level configurable via rpki.conf
svn path=/branches/tk705/; revision=6444
|
|
specified by DB API, just use it, rather than getting clever with
variable-length argument sequences.
svn path=/branches/tk705/; revision=6442
|
|
svn path=/branches/tk705/; revision=6441
|
|
of rpki.django_settings.gui
Create new rpki.django_settings.gui_script Django settings file with a minimal subset required to use the ORM, to be used in auxillary scripts
Add [rpkigui-import-routes] section to rpki.conf
Change log level of warning about AS value errors in routeviews dumps to DEBUG
svn path=/branches/tk705/; revision=6439
|
|
for XML. Apparently we were carefully changing just the XML files to
use a single "-" to work around this. Enough already, just convert
all copyright year ranges to single "-" and have done with this.
svn path=/branches/tk705/; revision=6427
|
|
svn path=/branches/tk705/; revision=6426
|
|
since copyright holder of record changed.
svn path=/branches/tk705/; revision=6425
|
|
and logging setup. Most programs now use the unified mechanism,
although there are still a few holdouts: the GUI, which is a special
case because it has no command line, and the rpki-rtr program, which,
for historical reasons has its own implementation of the logging setup
infrastructure.
svn path=/branches/tk705/; revision=6390
|
|
svn path=/branches/tk705/; revision=6377
|
|
worker CA and going straight from the root to certifying children,
which is wrong. However...this is far enough along that we can now
remove all the rootd glorp, which is a worthwhile simplification in
its own right, so checkpoint here, remove rootd glorp, then figure out
what's wrong with the internal certificate hierarchy.
rcynic does validate the current output, given a manually constructed
TAL, even if the current output isn't quite what it should be. So we
should also be able to sort out the new TAL generation code now.
Yes, checking in a version that works for the wrong reasons is weird,
but the current sort-of-broken state lets us confirm that the lower
levels of the tree are still correct as we go, which would be much
harder if the poor thing just sat there and whimpered until we had
the new internal CA code completely finished.
svn path=/branches/tk705/; revision=6376
|
|
svn path=/branches/tk705/; revision=6346
|
|
svn path=/branches/tk705/; revision=6319
|
|
svn path=/branches/tk705/; revision=6271
|
|
svn path=/branches/tk705/; revision=6268
|
|
svn path=/branches/tk705/; revision=6267
|
|
svn path=/branches/tk705/; revision=6265
|
|
svn path=/branches/tk705/; revision=6264
|
|
no serious runtime testing yet.
svn path=/branches/tk705/; revision=6262
|
|
svn path=/branches/tk705/; revision=6259
|
|
svn path=/branches/tk705/; revision=6258
|
|
Installation of everything but Debian packages is probably broken, and
Debian packages are too at the moment due to (probably) minor errors
in buildtools/debian-skeleton, but enough has changed that this really
needs a snapshot checked in for backup.
svn path=/branches/tk705/; revision=6257
|