Age | Commit message (Collapse) | Author |
|
svn path=/branches/tk705/; revision=6195
|
|
results from the original rcynic, still some loose ends and unfinished
bits, and no support for RRDP yet (which was sort of the ultimate
point of the exercise), but approaching the point of being usable, and
about an order of magnitude shorter than the C original.
svn path=/branches/tk705/; revision=6194
|
|
latin1 to work around MySQL 5.6 insanity. Fixes #782 (again).
svn path=/trunk/; revision=6193
|
|
svn path=/trunk/; revision=6192
|
|
svn path=/branches/tk705/; revision=6191
|
|
MySQL 5.5, so try the kludge, whine if it fails, then blunder ahead.
Fixes #781.
svn path=/trunk/; revision=6190
|
|
5.6 Latin1 kludge.
svn path=/trunk/; revision=6189
|
|
character set is UTF8 (fine so far), which causes MySQL to reject
ASN.1 DER stored in BLOBs (or, more likely, any operations against
such columns) on the grounds that ASN.1 DER is not well-formed UTF8.
svn path=/trunk/; revision=6188
|
|
summary from rcynic-text.
svn path=/branches/tk705/; revision=6187
|
|
svn path=/branches/tk705/; revision=6186
|
|
svn path=/branches/tk705/; revision=6185
|
|
Get full rsync code working, history cache and all.
svn path=/branches/tk705/; revision=6184
|
|
issuer. Not sure we really need the complex issuer-finding code at
all anymore, but dumping core is not an appropriate form of social
criticism.
svn path=/branches/tk705/; revision=6183
|
|
svn path=/branches/tk705/; revision=6182
|
|
OpenSSL certificate verification errors.
svn path=/branches/tk705/; revision=6181
|
|
makes the C code considerably simpler.
svn path=/branches/tk705/; revision=6180
|
|
left to do, still need to add in stuff that we pushed out to Python
rather than trying to do in C (eg, a lot of the URI tests), but basics
seem to work. Checkpointing before attempting a major simplification
of the StatusCode mechanism.
svn path=/branches/tk705/; revision=6179
|
|
svn path=/branches/tk705/; revision=6178
|
|
svn path=/branches/tk705/; revision=6177
|
|
X509Store.verify() to X509.verify(). Result seems to run properly
with trivial modification to existing Python BPKI code.
RPKI extended validation via this interface (the real point of this
exercise) still not tested.
svn path=/branches/tk705/; revision=6176
|
|
POW.c, still totally untested. X.509 certificate validation is in a
transitional state, currently spiced with awful kludges so that we're
still doing the right thing cryptographically, albeit in a completely
disgusting way as far as the API is concerned. Serious cleanup
needed, but wanted to get a post-merge version with CMS and X.509
working again after the merge into the repository for backup.
svn path=/branches/tk705/; revision=6175
|
|
rcynic.c. New functionality not yet tested, but doesn't seem to have
broken break anything in the CA software.
(Previous commit accidently included POW.c, oops, but no harm done.)
svn path=/branches/tk705/; revision=6174
|
|
svn path=/branches/tk705/; revision=6173
|
|
Regenerate EE certificates along with everything else when activating
a new CADetail (ie, when rolling a CA key).
svn path=/branches/tk705/; revision=6172
|
|
hacks: in practice, we always bypassed it (except when we forgot...).
Make sure we revoke and withdraw the old certs and objects for ROAs
and Ghostbusters rather than the new ones during forced reissue.
svn path=/branches/tk705/; revision=6171
|
|
.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
|
|
svn path=/branches/tk705/; revision=6168
|
|
svn path=/branches/tk705/; revision=6167
|
|
svn path=/branches/tk705/; revision=6166
|
|
svn path=/branches/tk705/; revision=6165
|
|
rpkid_task code. Combine and simplify CRL and manifest generation.
svn path=/branches/tk705/; revision=6164
|
|
svn path=/branches/tk705/; revision=6163
|
|
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
|
|
svn path=/branches/tk705/; revision=6160
|
|
through to X509 verification callback handler so it can record status
properly.
svn path=/branches/tk705/; revision=6159
|
|
RPKI validation in POW.c. So far this is mostly notes and the support
for the status code mechanism.
svn path=/branches/tk705/; revision=6158
|
|
svn path=/branches/tk705/; revision=6157
|
|
svn path=/branches/tk705/; revision=6156
|
|
for portability. With this change, the GUI appears to work with SQLite3.
svn path=/branches/tk705/; revision=6155
|
|
under yamltest. No obvious way to tell Django's CSRF protection to
allow this, not entirely sure we'd want to do so even if we could.
svn path=/branches/tk705/; revision=6154
|
|
running with new code base. Now working with
$ yamltest.py --sql mysql --gui smoketest.1.yaml
svn path=/branches/tk705/; revision=6153
|
|
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
|
|
postgresql sort of works with the core daemons and rpkic, well enough
to generate RPKI objects if one hand configures it, but one can't even
run migrations for the GUI, due to a few non-portable SQL data types,
and migrations from earlier version of the IRDB have similar problems.
svn path=/branches/tk705/; revision=6151
|
|
operations, so simplify code and schema by removing gratuitous
transformations to and from binary format.
svn path=/branches/tk705/; revision=6150
|
|
backend. Switch yamltest's default database configuration to sqlite3.
MySQL still has character set issues, which are almost certainly to do
with the communication channel rather than the database tables. It's
possible that one of the newer DB API drivers for MySQL fixes this,
might be worth trying one of them at some point (see the "MySQL notes"
discussion of MySQL DB API drivers in the Django documentation).
svn path=/branches/tk705/; revision=6149
|
|
database, so the garbage collector can clean it up automatically.
svn path=/branches/tk705/; revision=6148
|
|
else.
svn path=/branches/tk705/; revision=6147
|
|
incorrectly coded UTF-8 in BLOB fields holding ASN.1 DER data. This
is wrong in so many ways that I don't even know where to start, but,
bottom line, forcing Latin1 here is just making MySQL 5.6+ revert to
the behavior in MySQL 5.5.
This is just a workaround. The real solution is probably to switch to
an SQL engine that's not quite such a kludge tower.
svn path=/branches/tk705/; revision=6146
|