Cerca in PI
Diritto & Internet
Torna alla notizia
Inizia nuova discussione
Censura? Peer-to-peer chiave del porno
30 lug 2001, 00.00
files sharing, porno e privacy
30 lug 2001, 18.16
Avete notato che...
30 lug 2001, 09.43
30 lug 2001, 13.20
ovvio che è una scusa.
30 lug 2001, 08.26
30 lug 2001, 13.17
> mi sa che hanno visto troppo "the
> untouchables" ... come con Al Capone hanno
> usato una pecca fiscale per fermare omicidi,
> qui vorranno usare il porno per fermare gli
> mp3 ...
solo che noi non siamo al capone...
> speriamo che non succeda.
mai sentito di tunneling ??? e solo una delle possibilita...
> e comunque il porno che si trova è davvero
bhe, insomma...il discorso pero e questo...se uno a 15 anni (in media) fa sesso, perche questa legge sulla protezione degli under 18, 21, 300000 anni ???
> scusate. ma questo benedetto freenet? io non
> sono riuscito ad accedere, e non capisco la
> sua natura.
e una rete di comunicazione che
1) encrypta le informazioni in transito
2) l'origine dei dati "viene persa sulla strada", diciamo cosi...
> Va bene un browser?
si...ma ti servono comunque alcune conoscenze informatiche...e la volonta di imparare...
e come navigare sul web (piu o meno), ci sono siti con password e siti senza...
> come si pubblica? come si legge? come si
per cercare al momento si va su passa parola (piu o meno), non c'e un sistema centralizzato di ricerca...
tutto ruota intorno alle KEYS (ALLA FINE TI ALLEGO LA KEYS GUIDE)
vai e leggiti anche la how to publish, guide...
/ (mirror penso)
impara a nuotare da solo...
Publishing in Freenet
A Guide to Freenet Keys
As Freenet nears a state where it should be usable by casual computer users, it is probably about time we actually provided a good explanation about how content can be placed on Freenet for people to view, and also to detail a few tricks which may be useful.
This guide describes each type of key and explains how to use each one.
0.1 The Basics
Freenet, as far as the user is concerned, stores and retrieves information. When you store some information you can choose a key, or in some cases one is chosen for you. If you are chosing your own key it must be unique or Freenet will not allow you to store anything under that key. At
some later date, you, or someone else, can retrieve the information by giving Freenet the key. Freenet doesn't guarantee that you will be able to retrieve a piece of information stored previously, as sometimes Freenet needs to delete older information to make room for newer content.
Freenet itself merely provides the infrastructure for storing and retrieving information, it does not provide an easy-to-use interface for the user. To address this issue we encourage the creation of Freenet clients. A client may be specific, such as one which allows the storing of music in Freenet,
or may be generic, such as one which can store and retrieve files from and to your hard-disk. One client which we anticipate will be particularly
useful is FProxy which allows you to access information on Freenet through your web-browser as if you were just accessing websites on the World
Wide Web. This presents a familiar interface to the end user while taking advantage of the web-browser to handle the presentation of information.
Some of these clients will just provide means to access information on Freenet, where as some will allow you to place information of Freenet too.
Fproxy lets you insert and retrieve keys but the command line interfaces give you more options. Windows users have frequest.exe and finsert.exe
to request and download keys. *nix users have freenet_request and freenet_insert.
One option Fproxy doesn't let you specify is HTL or hops to live. HTL specifies the depth of your insertion or search. The higher the HTL the
farther your data will spread when inserting or the farther Freenet searches for data when you make a request.
In any of the examples that follow you can specify the HTL by adding -htl number. Freenet uses the default value specified in your configuration
file if you do not use the -htl option.
This guide details the use of the command line interfaces. The Fproxy web interface is easy to use and should be familiar to the casual Web user.
0.3 Key types
I mentioned in section 0.1 that sometimes you get to choose your own key, and sometimes one is chosen for you. At present there are four types of
key in Freenet that you have at your disposal:
0.3.1 Content Hash Key (CHK)
CHKs are the work-horses of Freenet. Normally data is not stored under KSKs or SSKs (see below), but is stored under a CHK and a "redirect" to the data is stored under the KSK or SSK. A redirect is a mechanism supported by all clients where the data under one key can instruct the client to download the data under another key and pretend that the data was found under the first key. When you insert a CHK you insert it as CHK@, after the data has been inserted the client will tell you what the CHK's actual name is. The reason for this is that the name of the CHK is determined by the data itself, two CHKs containing the same data will have the same CHK, and two CHKs with different data will have different names.
Note the format - all Freenet keys start with freenet:, then the three letter acronym of the keytype, then an @, and then some stuff specific to the key. You can sometimes leave out the freenet: part and a client will fill it in for you.
With the command line interface you would insert a file named boat.gif as a CHK key like this:
finsert freenet:CHK@ boat.gif
freenet_insert freenet:CHK@ boat.gif
When the insertion is complete you will be told the CHK value which will look something like:
0.3.2 Keyword Signed Key (KSK)
A KSK is probably the simplest and most user-friendly keytype, since it is simply a name that you choose yourself when you insert the data. A typical KSK might look like:
With some clients you can sometimes leave out KSK@ and it will be assumed that you are referring to a KSK.
If you have an image file named 1000.jpg and you want to insert it in Freenet as house.jpg using a KSK key you would do this:
finsert freenet:KSK@house.jpg 1000.jpg
Users could then retrieve your image file with:
frequest freenet:KSK@house.jpg house.jpg
freenet_request freenet:KSK@house.jpg house.jpg
This would save the file as house.jpg in your current directory.
If you try to insert a file that someone has already inserted, but under a different name, you will be informed that a duplicate copy exists. Although your file shares the same CHK your KSK will be inserted with a reference to the CHK.
So, if you insert freenet:KSK@coolboat.jpg and an
Torna alla notizia
Inizia nuova discussione