Re: Current examples for creating keys, updating and getting freesites

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--===============0855165539==
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="3lAtjL59Tmlv9Ar91eHWMfEqo6teluirj"

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--3lAtjL59Tmlv9Ar91eHWMfEqo6teluirj
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 11/10/2013 12:45 AM, Michael Pearce wrote:
> Hi Steve.
>=20
> I'm using Ruby and the library for Ruby is... well... a little out of
> date.  There were a couple of quick changes to make (syntax for Ruby
> 1.9 and library changes), but i was having a hard time getting things
> to work with making a blocking request...  Since i really want to do
> just a few simple things, i'll most likely roll my own library and
> publish as a Ruby Gem.

Alright, sounds good.

> I did have another question: How do applications such as a "chat"
> work?  The only way that I could think of is to have multiple clients
> sharing the same SSK private key, publish to a USK to write a new
> message, then read all versions of with the public key to see what
> others have written.  Is this even close?

That could work, but it would be problematic. With this kind of approach
one malicious person can spam messages to that single key so that no one
can reliably send messages.

The problem to solve here is finding other identities to fetch messages
from. My understanding is that FMS and FLIP (examples of forums and chat
respectively) have a shared key for announcing identities, and after
that each identity inserts messages to their own private SSK.
Individuals can then be ignored at will, and all a malicious individual
can do - at least at a key level - is overwhelm the announcement
mechanism. This is often coupled with a trust/scoring system where in
addition to publishing messages, identities publish a trust list, and
give bad scores to spammers or those who abuse their trust list.

If you want to do something like this, you could roll your own identity
announcement, or make use of an established system like Web of Trust
(WoT) or Less Crappy Web of Trust (LCWoT). [0][1] WoT provides identity
creation and announcement. Unlike FMS and FLIP, it does not use a shared
announcement key. Instead it ships with a list of trusted "seed
identities" that already run the software, and add at neutral trust
those who solve CAPTCHAs they publish. LCWoT was written due to
frustration with WoT's performance and stability, and only supports
established identities.

-Steve

[0] https://github.com/freenet/plugin-WoT-staging/
[1] https://github.com/tmarkus/LessCrappyWebOfTrust


--3lAtjL59Tmlv9Ar91eHWMfEqo6teluirj
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBAgAGBQJSgArfAAoJECLJP19KqmFuzl0P/36S7tI7s4BCLo7KHU7u4LPl
By0DnOkvo+zMT47V953j9b1M0qTmaj0EL+gMZkHg22X838vJSMVuiu4EEecKdDZk
bXDoe0C9FXAZpABc8AG0CWpD/nauRF0W8D/N6qbIyh7NaOhgfLRPc24gjMhL8NnF
t2TAN9ijdN0ee+F4suHfrWFNWm1EBviGbD2e90d9VbwDI7W0KpVsV8dod8NeWZnB
TCgzZgSlQQfsOJ8i+292qtPOOzQ/6ymP8WDmpHl/Ar+Sp0F2zovfW7qtScYe75AU
6frlEHvHDta7pEwFMla1SLuguwOw7xI1mo/u9UsRj0bs27AFgDGZ+iy1HHW0ykN7
X4qh6PwYfBa+KcN/2npPU1TV7huh6HSJz9Fil4gc+wUphzpm37UnQrMPjYEEUqLC
4bHouRraPm6wm2p8+svqvObTpQ0ETGisJ0rvDI06f0b08LzXn/aNSOu4kD8zHYlb
C9iZoGm4LOaUlgDPnwFKWPk6mKHOfjeat7MOgCH+cWoxsDmpBruPVuPlCRC+fQTK
C0m+d24spZLVEV2P/e7lbKsmK6rgm6sQSu9Lssoxpe8Hrsl+owrHzr9GsrmfSvoI
7YjLgR27f8t7QaA0UzPAUJggnwQbWfUcpquVlHmoacTnLXiUL9PNr8bCabneEusD
35UHbXdQ32VcRByGVyNq
=7gHA
-----END PGP SIGNATURE-----

--3lAtjL59Tmlv9Ar91eHWMfEqo6teluirj--

--===============0855165539==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Tech mailing list
[email protected]
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/tech
--===============0855165539==--