Age | Commit message (Collapse) | Author |
|
svn path=/branches/tk705/; revision=6417
|
|
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
|
|
into an expanded rpki.irdb.models.Parent, as the two are more alike
than I expected them to be, but archive this version first.
svn path=/branches/tk705/; revision=6375
|
|
svn path=/branches/tk705/; revision=6157
|
|
helped the MySQL UTF-8 whining. Same Python code running with MySQL
5.5 doesn't do this, so it's some kind of upgrade trainwreck.
BinaryField uses BLOBs too, just as one would expect, so in theory
this can't be happening. So it's an undocumented feature. Yum.
But we wanted to move to BinaryField anyway, and doing so doesn't seem
to have made the problem worse, so committing the changes.
svn path=/branches/tk705/; revision=6145
|
|
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
|
|
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
|
|
configuration protocol instead of the crufty ancient "myrpki" version.
Semantics largely unchanged, differences are primarily syntax and
cleanup of historical baggage, but only the new protocol includes RRDP
support, which we're gonna need.
At some point we should write XSL transforms that map between the
useful portions of the old protocol and the modern equivalent.
svn path=/branches/tk705/; revision=6119
|
|
incomprehensible advance depreciation warnings for Django 1.9.
svn path=/branches/tk705/; revision=6100
|
|
but it sails blithely along, suggesting that I've forgotten some bit
of startup voodoo that it's doing. Regardless, the migration should
be harmless, and now we know that South thinks it can read the IRDB
models, which is progress.
The current requirement to have a valid rpki.conf before one can run
rpki-manage schemamigration etc is a bit of a pain, may need to do
something about that.
svn path=/branches/tk713/; revision=5949
|