sks-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sks-devel] SKS database structure


From: Kristian Fiskerstrand
Subject: Re: [Sks-devel] SKS database structure
Date: Thu, 15 Aug 2013 23:47:29 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 08/15/2013 09:28 AM, Parke wrote:
> Hi SKS-devel,
> 
> Is there documentation of the database structure?
> 
> I'd like to know how feasible it is to read/query the database 
> directly from Python, rather than via HPK.  I don't need to edit
> the database, just query it.

To the extent it is helpful for your project we added sksclient[0] in
1.1.4. I've been playing around with it a bit myself wrt sks2wot /
pks2wot. It has its own make target to get the binary.

[0] http://lists.nongnu.org/archive/html/sks-devel/2012-05/msg00127.html

- -- 
- ----------------------------
Kristian Fiskerstrand
Twitter: @krifisk
- ----------------------------
Public PGP key 0xE3EDFAE3 at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
- ----------------------------
Adde parvum parvo magnus acervus erit
Add little to little and there will be a big pile
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.1.0-beta220 (GNU/Linux)

iQIcBAEBCAAGBQJSDUxlAAoJEJjgB+fVz3pups4P/i224CFrwjIKueY77Y/4vRr6
GRDPij+hjGhfv+8CeEEdeb+RmoTSTNJTscC+GlW2d35gCRjkYpMCIdjAGhc+rUsa
/jfDP/ZTDqLcrnuKcB/mB17ZpdlnTBfyt8bES9Dmazg7yFzh/uZ3GcFPG+cj5veP
ilSvQqx+iTFzyxTWDG2zNm8dbK+OWoFI8TM7oI5Z176dWCVZRDRO70CRohmMM95C
+BY0Jwkj3qY/EwaVsda+A4PXfLuy+WbWxNiadeodb/zsusaHm61iFqdkm7C/WHwr
NJf4QPG5G4n+ZhXBIiWMGcAnKNhr/YXGeiFXxiTnV4h0KGi+umDpMfn6hXX2kWNx
Jhz+nEm1dM01yssobm68ALz6bmwZOxZA/9kAh3rQ/H3O7GDJ0rY+ZLlPhDD9+A90
zPEJTQlNqofPZAUf1OaeAgviycNiXEdQcgzwrUOksl6VJcqFshS6anR8c0iIN5V8
aJh7CT439idMp393z8F+eEWC0mfA/aqx1kCxeiK/INlqcmrAwzXYvkliProwy9W7
bItD1yNdiqiWnBM/0RbmVxebvzi3f3zeoQUJFD6xRY96w1fv706/IFwyY1eJJwwb
YGmF7YiY0fVUiZMlY8RDz6KDruB4Q4ZFo/6dGEHCy0obk+H3Zl0G2LfjGr7eiJTj
hfrHq5byfMzisS/jKgRY
=k31A
-----END PGP SIGNATURE-----



reply via email to

[Prev in Thread] Current Thread [Next in Thread]