Age | Commit message (Collapse) | Author |
|
svn path=/branches/tk705/; revision=6445
|
|
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
|
|
reporting AIA extension of a root certificate. See #809.
svn path=/branches/tk705/; revision=6412
|
|
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
|
|
startup error messages logged properly if at all possible. See #806.
svn path=/branches/tk705/; revision=6387
|
|
svn path=/branches/tk705/; revision=6379
|
|
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
|
|
Parents do, because Roots will be uniquely named by reference to their
associated Parent. So move the handle back to Parent.
svn path=/branches/tk705/; revision=6370
|
|
svn path=/branches/tk705/; revision=6369
|
|
svn path=/branches/tk705/; revision=6346
|
|
using a single bulk IRDB query for all the child data that
UpdateChildrenTask needs is a better solution.
svn path=/branches/tk705/; revision=6295
|
|
svn path=/branches/tk705/; revision=6293
|
|
svn path=/branches/tk705/; revision=6289
|
|
svn path=/branches/tk705/; revision=6276
|
|
svn path=/branches/tk705/; revision=6275
|
|
svn path=/branches/tk705/; revision=6273
|
|
than one would use in an interactive program.
svn path=/branches/tk705/; revision=6272
|
|
.publish_world_now() to something a little less whacky. Consolidate
fix for singleton URIs in SIA fields.
svn path=/branches/tk705/; revision=6170
|
|
Tweak publication callback mechanism to use uri instead of tag.
svn path=/branches/tk705/; revision=6169
|
|
understands Django's exotic metaclasses, which in turn allows us to
re-enable a number of pylint checks we had disabled. While we were at
this, stripped out a bunch of old pylint pragmas, then added back the
subset that were really needed. As usual with pylint, this turned up
a few real bugs along with an awful lot of noise.
svn path=/branches/tk705/; revision=6162
|
|
sequence trace code to rpki.rpkidb.models to assist in simplifying
some of the gratuitously complicated method call chains. Various
trivial PyLint cleanups.
svn path=/branches/tk705/; revision=6161
|
|
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
|
|
database, so the garbage collector can clean it up automatically.
svn path=/branches/tk705/; revision=6148
|
|
up-down protocol specification and, more importantly, avoid spurious
CMS Replay errors.
svn path=/branches/tk705/; revision=6144
|
|
UTF-8 whining on what are supposed to be binary fields that's probably
the result of a MySQL upgrade, and CMS Replay exceptions due to the
pseudo-random order in which HTTP client connections run in Tornado.
The UTF-8 mess is probably a good reason to change over to Django's
native binary field type, which we were going to want to do anyway.
The CMS Replay problem is not Tornado's fault: we probably would have
seen it in the old code were it not for an accidental side effect of a
long-since-abandoned attempt to use persistent HTTP connections. The
fix is probably to serialize requests to a particular host using use a
tornaodo.queue.Queue() object, or something like that.
svn path=/branches/tk705/; revision=6143
|
|
svn path=/branches/tk705/; revision=6140
|
|
quite working perfectly yet (cron is a bit wonky) but manages to
produce an initial set of ROAs without thowing any exceptions, and
code is already much cleaner than the old callback-based horror.
svn path=/branches/tk705/; revision=6139
|
|
bad choice for something implemented in Python, holdover from an older
specification, but Django ORM's troubles with "self" as a keyword
argument were the last straw. Enough already. Backwards
compatability should be a straightforward data migration.
svn path=/branches/tk705/; revision=6134
|
|
Django ORM. Duct tape and bailing wire everywhere, much clean-up left
to do, but basic "make yamltest" suite runs. Much of the clean-up
isn't worth doing until after revamping the I/O system, as it'll all
change again at that point anyway.
svn path=/branches/tk705/; revision=6127
|
|
svn path=/branches/tk705/; revision=6123
|
|
svn path=/branches/tk705/; revision=6122
|
|
left-right protocol and irdb and rpkidb models.
Not fully working yet, RRDP URI isn't yet showing up everywhere it
should, but this is probably more an indication that the previous hack
was incomplete than that the replacement broke something.
svn path=/branches/tk705/; revision=6120
|
|
svn path=/branches/tk705/; revision=6115
|
|
svn path=/branches/tk705/; revision=6114
|
|
svn path=/branches/tk705/; revision=6113
|
|
svn path=/branches/tk705/; revision=6112
|
|
rpki.left_right and start pruning the result down to figure out how
much really needs to be ported over to the new models.
svn path=/branches/tk705/; revision=6108
|
|
At this point, all the classes remaining in rpki.left_right pertain
are the pre-Django equivalents of models, and they're the only things
left still using rpki.xml_utils.
Some old test code remains broken (not yet converted). GUI code that
I know about has been converted but not tested (not all that much to
convert there, mostly the GUI just invokes the Zookeeper.
svn path=/branches/tk705/; revision=6107
|
|
rpki.left_right classes.
svn path=/branches/tk705/; revision=6106
|
|
clean up some of the corresponding mess.
svn path=/branches/tk705/; revision=6105
|
|
to parse them and generate migrations for them. Not actually using
them for anything yet, but code still runs with this present so
haven't broken anything yet....
svn path=/branches/tk705/; revision=6103
|
|
and didn't notice.
svn path=/branches/tk705/; revision=6097
|
|
development branch, so committing the merge before testing shouldn't
break anything.
svn path=/branches/tk705/; revision=6084
|
|
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=6014
|
|
svn path=/branches/tk705/; revision=5981
|
|
svn path=/branches/tk705/; revision=5970
|
|
SAX.
svn path=/branches/tk705/; revision=5969
|
|
svn path=/branches/tk705/; revision=5960
|