sks-devel
[Top][All Lists]
Advanced

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

Re: [Sks-devel] exchange of ideas


From: Steffen Kaiser
Subject: Re: [Sks-devel] exchange of ideas
Date: Fri, 12 Apr 2019 08:59:54 +0200 (CEST)
User-agent: Alpine 2.11 (DEB 23 2013-08-11)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, 23 Mar 2019, fuat wrote:

A text file, html file, and .asc file are not dangerous to the server.

The attacker cannot harm the server with the text file. can only read.
but sks database is very often corrupted. If there is an error in
writing a file, only that file is corrupted.

if a single file gets corrupted, you won't notice. If the DB is corrupted, you'll notice soon. A single file is more easily compromised.

The content of a text file from the internet is quick to reach.

Yes, if you have a straight forward access mechanism, e.g. getting by hash or an exact match lookup. You can surf many many static files easily - semiparallel. But what about (fuzzy) search? You'll need some sort of search index to answer in a reasonable time. The same key can be addressed by different lookup queries, too.

The database occupies only 20 percent less disk space and the search is
slightly faster than 20 percent.

I'll doubt that non-exact search is only 20% faster than handling plain text files.

however, instead of remaining dependent on a single system for such a
difference, it would be more flexible and diverse to work with
different programs that achieve the same results and do the same.

Yes. In fact, you could do so now by using SKS for reconcil only, dump the keys in any fashion and use yet another search and delivery program.

If you increase logging, you'll get Adding Del'ing lines. I assume these include update events, too.

- -- Steffen Kaiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBXLA3aiOjcd6avHZPAQKjLAgAhKb/b4L1qojsV79UP2EW+g3J2JV/Ce1y
Rv/0AFo9qeX8JGAiErh10G+OVI09/3GMaKLCJrFKbpXcqC+XU7ZyPxGidfAsYtuf
TT93S2pCyelsZo7QLMNqquSXoSCGeEQ2M5yVONKWJliQnOq4T1i8yrSQDFepU1K5
G7nW+A3DcmONl2BjFaQHFUqTQlg/EmOFdUVHzzoKe264Wm0ycYXUS+SUwoT8b1wa
7F5gAAHMToh6+jA9TpmbUckcRWhZyHVGjCvV4lwnV81dpduoI7b+PjkiSt7Aa7rK
o2+WiirXYzHYAcPTRXTxsHj+bS3//F8VPu3RhGZUZ44ZzLx3UPQunA==
=JHkw
-----END PGP SIGNATURE-----



reply via email to

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