Send Freenet-dev mailing list submissions to
freenet-dev at lists.sourceforge.net
To subscribe or unsubscribe via the web, visit
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
or, via email, send a message with subject or body 'help' to
freenet-dev-request at lists.sourceforge.net
You can reach the person managing the list at
freenet-dev-admin at lists.sourceforge.net
When replying, please edit your Subject line so it is more specific than
"Re: Contents of Freenet-dev digest..."
Today's Topics:
1. Re: Meaningless hits on metadata (Scott G. Miller)
2. JRE availability (Scott G. Miller)
3. Re: Meaningless hits on metadata (Henry Hemming)
4. Re: Meaningless hits on metadata (Scott G. Miller)
5. Re: JRE availability (Oskar Sandberg)
6. Re: Meaningless hits on metadata (Oskar Sandberg)
7. Re: Meaningless hits on metadata (Alex Barnell)
8. Re: JRE availability (Scott G. Miller)
--__--__--
Message: 1
Date: Sun, 25 Jun 2000 10:34:28 -0500
To: freenet-dev at lists.sourceforge.net
Subject: Re: [Freenet-dev] Meaningless hits on metadata
protocol="application/pgp-signature"; boundary="xo44VMWPx7vlQ2+2"
From: "Scott G. Miller" <[email protected]>
Reply-To: freenet-dev at lists.sourceforge.net
--xo44VMWPx7vlQ2+2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
>=20
> I don't see how. Nodes need the plain-text of values to perform fuzzy
> matching (and fuzzy routing). Nodes need the plain-text of fields to allow
> matches to be performed in the case where the request includes just fields
> A and B, but the node has something matching in its store with fields A, B
> and C. If the fields were encrypted, there would be no way of knowing it
> was a match.
I thought we agreed that situations where the cardinality was different
(eg A,B search against A,B,C fields) wouldn't work? And this is only true
if the node does the matching, which it might not have to do, if all the
matching terms are returned and the client filters them.
--xo44VMWPx7vlQ2+2
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE5ViaEpXyM95IyRhURAuvXAKCzl02qeJtoB1QFXja2vNivCAeWOQCeNB4N
6Uder46N+nCsbK7x0sLw36U=
=Cr11
-----END PGP SIGNATURE-----
--xo44VMWPx7vlQ2+2--
--__--__--
Message: 2
Date: Sun, 25 Jun 2000 10:42:36 -0500
To: freenet-dev at lists.sourceforge.net
protocol="application/pgp-signature"; boundary="mP3DRpeJDSE+ciuQ"
From: "Scott G. Miller" <[email protected]>
Subject: [Freenet-dev] JRE availability
Reply-To: freenet-dev at lists.sourceforge.net
--mP3DRpeJDSE+ciuQ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
We can write a Freenet for Dummies, that includes the URLs of the JRE
packages (which are self-installing executables):
Windows:
http://java.sun.com/j2se/1.3/jre/download-windows.html
Linux:
http://java.sun.com/products/jdk/1.2/jre/download-linux.html
Solaris:
http://java.sun.com/products/jdk/1.2/jre/download-solaris.html
Macintosh:
http://asu.info.apple.com/swupdates.nsf/artnum/n11572
OS/2:
http://www.ibm.com/java/jdk/JREsite.html
That should cover the bases.
--mP3DRpeJDSE+ciuQ
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE5VihspXyM95IyRhURAupWAJ9uD/0zZG5T79J4D5Xe3hyaDHuMDQCghkI1
S5FrBrP7nEL08WwvkIAWAO0=
=L3Hp
-----END PGP SIGNATURE-----
--mP3DRpeJDSE+ciuQ--
--__--__--
Message: 3
From: "Henry Hemming" <[email protected]>
To: freenet-dev at lists.sourceforge.net
Subject: Re: [Freenet-dev] Meaningless hits on metadata
Date: Sun, 25 Jun 2000 17:44:51 CEST
Reply-To: freenet-dev at lists.sourceforge.net
If the metadata keywords would be one way hashed, each separately, this
would ofcourse not provide full fuzzy logic, but would still be better than
nothing, and would hide the information from the node containing the
meta-data. Another one is to do a weak enough hash that partial match can be
detected, I'm not sure if this is possible but I can imagine it being
possible.
Other options are to random xor the meta data and give the result to one
party, and the random key to another, when one of the parties gets a meta
data query he xors it with his own key, and sends the xored value to someone
who has the other part of the key, and he performs comparison on the keys.
Ofcourse this would require a bit more trafic but the meta data would be 99%
hidden, and full fuzzy logic could be exploited in the meta data search.
--typo
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
--__--__--
Message: 4
Date: Sun, 25 Jun 2000 11:00:04 -0500
To: freenet-dev at lists.sourceforge.net
Subject: Re: [Freenet-dev] Meaningless hits on metadata
protocol="application/pgp-signature"; boundary="FCuugMFkClbJLl1L"
From: "Scott G. Miller" <[email protected]>
Reply-To: freenet-dev at lists.sourceforge.net
--FCuugMFkClbJLl1L
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
> Other options are to random xor the meta data and give the result to one=
=20
> party, and the random key to another, when one of the parties gets a meta=
=20
> data query he xors it with his own key, and sends the xored value to some=
one=20
> who has the other part of the key, and he performs comparison on the keys=
.=20
> Ofcourse this would require a bit more trafic but the meta data would be =
99%=20
> hidden, and full fuzzy logic could be exploited in the meta data search.
It wouldn't be hidden at all. If the server knows how to find the other
half of the key, then this system is useless, because the node operator
knows (or can find) the other half as well. This provides no additional
security.
Likewise, any weak hash that can allow the server to perform fuzzy
matching isn't strong enough to warrant its use, since its not going to
provide any measure of deniability.
--FCuugMFkClbJLl1L
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE5ViyEpXyM95IyRhURAt8lAJ9maTuzFjELkklR7UfAzHa1/2d4fQCgzd+N
Yx/U/jtaHicJz9PuBHsLAm0=
=ks8h
-----END PGP SIGNATURE-----
--FCuugMFkClbJLl1L--
--__--__--
Message: 5
Date: Sun, 25 Jun 2000 19:31:09 +0200 (MET DST)
From: Oskar Sandberg <[email protected]>
To: freenet-dev at lists.sourceforge.net
Subject: Re: [Freenet-dev] JRE availability
Reply-To: freenet-dev at lists.sourceforge.net
You realise that IDG books are going to sue whoever keeps the
archives of the mailing list now?
Oskar Sandberg
md98-osa at nada.kth.se
On Sun, 25 Jun 2000, Scott G. Miller wrote:
> We can write a Freenet for Dummies, that includes the URLs of the JRE
> packages (which are self-installing executables):
>
> Windows:
> http://java.sun.com/j2se/1.3/jre/download-windows.html
>
> Linux:
> http://java.sun.com/products/jdk/1.2/jre/download-linux.html
>
> Solaris:
> http://java.sun.com/products/jdk/1.2/jre/download-solaris.html
>
> Macintosh:
> http://asu.info.apple.com/swupdates.nsf/artnum/n11572
>
> OS/2:
> http://www.ibm.com/java/jdk/JREsite.html
>
> That should cover the bases.
>
--__--__--
Message: 6
Date: Sun, 25 Jun 2000 19:33:37 +0200 (MET DST)
From: Oskar Sandberg <[email protected]>
To: freenet-dev at lists.sourceforge.net
Subject: Re: [Freenet-dev] Meaningless hits on metadata
Reply-To: freenet-dev at lists.sourceforge.net
We hash things normally so as to make sure that the routing of
information does not reflect the content of the
(descriptive) keys. However, with searching this is the point, so
hashing makes little or no sense.
Oskar Sandberg
md98-osa at nada.kth.se
On Sun, 25 Jun 2000, Henry Hemming wrote:
> If the metadata keywords would be one way hashed, each separately, this
> would ofcourse not provide full fuzzy logic, but would still be better than
> nothing, and would hide the information from the node containing the
> meta-data. Another one is to do a weak enough hash that partial match can be
> detected, I'm not sure if this is possible but I can imagine it being
> possible.
>
> Other options are to random xor the meta data and give the result to one
> party, and the random key to another, when one of the parties gets a meta
> data query he xors it with his own key, and sends the xored value to someone
> who has the other part of the key, and he performs comparison on the keys.
> Ofcourse this would require a bit more trafic but the meta data would be 99%
> hidden, and full fuzzy logic could be exploited in the meta data search.
>
>
> --typo
>
> ________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
>
>
> _______________________________________________
> Freenet-dev mailing list
> Freenet-dev at lists.sourceforge.net
> http://lists.sourceforge.net/mailman/listinfo/freenet-dev
>
--__--__--
Message: 7
Date: Sun, 25 Jun 2000 19:05:42 +0100
From: Alex Barnell <[email protected]>
To: freenet-dev at lists.sourceforge.net
Subject: Re: [Freenet-dev] Meaningless hits on metadata
Reply-To: freenet-dev at lists.sourceforge.net
"Scott G. Miller" wrote:
>
> >
> > I don't see how. Nodes need the plain-text of values to perform fuzzy
> > matching (and fuzzy routing). Nodes need the plain-text of fields to allow
> > matches to be performed in the case where the request includes just fields
> > A and B, but the node has something matching in its store with fields A, B
> > and C. If the fields were encrypted, there would be no way of knowing it
> > was a match.
> I thought we agreed that situations where the cardinality was different
> (eg A,B search against A,B,C fields) wouldn't work? And this is only true
> if the node does the matching, which it might not have to do, if all the
> matching terms are returned and the client filters them.
>
I don't think we agreed on anything.. we should try out all possibilities
in a simulator first. I originally thought that AB against ABC would be fine for
returning results, but not for routing, but my latest idea (not written up yet)
uses slightly different routing anyway.
--__--__--
Message: 8
Date: Sun, 25 Jun 2000 13:28:40 -0500
To: freenet-dev at lists.sourceforge.net
Subject: Re: [Freenet-dev] JRE availability
protocol="application/pgp-signature"; boundary="tKW2IUtsqtDRztdT"
From: "Scott G. Miller" <[email protected]>
Reply-To: freenet-dev at lists.sourceforge.net
--tKW2IUtsqtDRztdT
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
> You realise that IDG books are going to sue whoever keeps the
> archives of the mailing list now?
My bad. "Freenet for the Intellectually Challenged"
--tKW2IUtsqtDRztdT
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE5Vk9YpXyM95IyRhURAoypAKCesYAtNDyP/IvK6xZOC2Vd6Sa8uwCdFctf
hWC8ac8vmLWCub1X+hFkoJg=
=vSUs
-----END PGP SIGNATURE-----
--tKW2IUtsqtDRztdT--
--__--__--
_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
End of Freenet-dev Digest
