| Age | Commit message (Collapse) | Author |
|---|
|
specification of a handle for the new root entity instead of the
default of using a randomly-generated UUID as the name.
svn path=/branches/tk705/; revision=6432
|
|
as including it ends very badly when the root certificate serial is a
randomly-generated 64-bit value. See #814.
svn path=/branches/tk705/; revision=6430
|
|
compatability hack which allows irdbd's server host and port to be
expressed as a URL. No big deal, except that I wonder how many other
relics we're going to find in The Config File That Time Forgot.
See #813.
svn path=/branches/tk705/; revision=6428
|
|
since copyright holder of record changed.
svn path=/branches/tk705/; revision=6425
|
|
We were building the correct management object structure in rpkidb,
but not in irdb, so the irdb kept breaking things when it tried to
bring them into alignment. What we get for trying to perform an
upgrade which requires pushing on a rope.
Anyway, result now appears to work. Committing, but letting it run
for a while before handing off to the usual alpha testers.
svn path=/branches/tk705/; revision=6422
|
|
svn path=/branches/tk705/; revision=6421
|
|
No longer throwing nasty errors, but resources still not propegating
correctly down from constructed root (yet).
svn path=/branches/tk705/; revision=6420
|
|
rsync URIs in too many places, we had been inconsistent about updating
them to match the new environment.
In theory, the URI updating code now knows to touch only URIs that
refer back to this same set of servers, while leaving URIs referencing
external services alone, but this has not (yet) been tested.
svn path=/branches/tk705/; revision=6419
|
|
svn path=/branches/tk705/; revision=6418
|
|
isn't working quite right yet (can't extract root certificate/TAL, so
not useful yet), but most of the up-down/left-right/publication
protocol now looks to be working with the translated data.
svn path=/branches/tk705/; revision=6416
|
|
engine to reset SQL SEQUENCEs after we've been fiddling with primary
keys directly. OK, I can understand why we ahve to do something, but
why does the official API for this expect us to cut and paste (with
color control escape sequences, no less)?
svn path=/branches/tk705/; revision=6415
|
|
SIA URI twiddling still needs doing.
svn path=/branches/tk705/; revision=6414
|
|
there yet, but general approach is starting to become clear.
svn path=/branches/tk705/; revision=6411
|
|
svn path=/branches/tk705/; revision=6410
|
|
smoketest.1.yaml. Not yet tested in a live server. Rootd transition
not yet written, so far just some diagnostics showing some of the data
we'll need to use to move the root CA state we must keep into the new
internal root object (keys, serial numbers, etc).
svn path=/branches/tk705/; revision=6409
|
|
svn path=/branches/tk705/; revision=6408
|
|
svn path=/branches/tk705/; revision=6407
|
|
Still have irdb and pubd to do.
svn path=/branches/tk705/; revision=6406
|
|
that anybody is likely to care.
svn path=/branches/tk705/; revision=6405
|
|
svn path=/branches/tk705/; revision=6404
|
|
results, of course, but Django behavior so far suggests that this
approach will probably work.
svn path=/branches/tk705/; revision=6403
|
|
svn path=/branches/tk705/; revision=6398
|
|
encapsulate all (well, we hope) relevant configuration and state from
a trunk/ CA in a form we can easily load on another machine, or on the
same machine after a software upgrade, or ....
Transfer format is an ad hoc Python dictionary, encoded in Python's
native "Pickle" format, compressed by "xz" with SHA-256 integrity
checking enabled. See #807.
svn path=/trunk/; revision=6395
|
