| Age | Commit message (Collapse) | Author |
|---|
|
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
|
|
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
|
|
or commenting conventions should be shot. If it so happens that it is
inconvenient to shoot him, then he is to be politely requested to recode
his program in adherence to the above standard."
-- Michael Spier, Digital Equipment Corporation
svn path=/branches/tk705/; revision=6152
|
|
incomprehensible advance depreciation warnings for Django 1.9.
svn path=/branches/tk705/; revision=6100
|
|
This needs rewriting, but doing it properly requires a minor database
schema change, and I'm trying to get a test case running by tomorrow
morning.
svn path=/branches/tk705/; revision=6015
|
|
svn path=/branches/tk705/; revision=5956
|
|
svn path=/branches/tk713/; revision=5952
|
|
svn path=/branches/tk713/; revision=5951
|
|
indeed masking the new migration stuff. yamltest now runs migrations
as part of setting up test CAs; still need to decide whether running
migrations in production is something that should be handled
explicitly via rpki-manage or should be bundled into rpki-sql-setup.
Old settings.configure() code still present as a trail of breadcrumbs
to follow when backing out the rest of the tortuous startup sequence
required by the old way of doing things.
svn path=/branches/tk713/; revision=5950
|
|
svn path=/branches/tk713/; revision=5948
|
|
svn path=/branches/tk705/; revision=5913
|
|
svn path=/trunk/; revision=5902
|
|
svn path=/trunk/; revision=5856
|
|
logging handlers up front to the argparse stage, thereby also giving
the application more control over the default logging configuration.
svn path=/trunk/; revision=5851
|
|
svn path=/trunk/; revision=5845
|
|
subclass the stock one. Replace all uses of rpki.log.traceback() with
logging package .exception() calls. Use LoggingAdapter for all the
whacky per-stream logging code in rpki.http. Fix default logging
priority for non-daemon programs like rpkic.
svn path=/trunk/; revision=5843
|
|
svn path=/trunk/; revision=5842
|
|
svn path=/trunk/; revision=5836
|
|
svn path=/branches/tk685/; revision=5757
|
