Newsgroup: it.cultura.linguistica.inglese
Titolo: Controllo bontà di un testo

Un saluto a tutti. Spero di non abusare del ng e che la mia richiesta non 
sia OT.
Ho da poco fatto un programma di cui ho steso una breve relazione in inglese 
in cui ne spiego il funzionamento. In linea di massima credo di averla 
scritto benino ma vi sono di sicuro alcune parti che andrebbero rivedute. 
Provo ad incollare alcune parti di testo sulle quali nutro dei dubbi:
1 -  A port knocking system is a method used to dinamically open a specified 
port in case that a certain IP attempts to connect on a set of prespecfied 
closed ports. Once a correct sequence of connection is received by the knock 
daemon, the firewall rules are dinamically modified to allow the "knocker" 
to connect over a certain port(s). A system like this could results useful 
in case that you'd want to make "non-public" a daemon that tipically listens 
on a public interface (e.g. SSH).
2 -  How does it work?
Knockd.py is a daemon that must be started on the remote server. The daemon 
must be configured by specifying:
- An ethernet interface(s) on wich the daemon have to listens on (e.g. 
eth1).
- A general timeout value (expressed in seconds) within the sequences have 
to take place (e.g. 5 seconds).
- A TCP (SYN) packet sequence that, if satisfied, executes a command (e.g. 
5200, 5400, 5600).
- The command that, once executed, opens a port
- (optional but rencommended) Another sequence (e.g. 10100, 10200, 10300) 
including the command used to close the port again
3  -  Encrypted one-way hashed-based authentication  - This kind of approach 
prevent an eventual Man In The Middle attacker (like could be, for example, 
the client's default gateway) to sniff a sequence and use it on its own.
%LOCAL_TIME% mixed to %LOCAL_IP_ADDRESS% variable makes possible that the 
hash value is univoque for every time a new knock occurs, and prevents MITM 
to gain unauthorized access by moving on the host's machine or by spoofing 
its IP address, even if he's able to sniff port sequence and hash value.
Note: This method requires a perfect clock syncronization on both hosts.
4 -  Next features I'd like to implement
Encrypted one-way hash-based authentication.
Remote SSL asymmetrical authentication by using UDP sockets.
UDP and ICMP protocols support to enlarge the range of possible sequence 
combinations.
Implement a fully customizable system and permit the user to manage a large 
gamma of packet's header parameters on different layers or their payload, 
enlarging the range of possible sequence combinations. Some examples:
IP: TTL, id...
TCP: type (SYN, ACK, RST, FIN...), src_port, seq_n, opts...
ICMP: type (ECHO, REPLY, PORT_UNREACHABLE...), code, id...

 %LOCAL_TIME% mixed to %LOCAL_IP_ADDRESS% variable makes possible that the
Io direi "... makes it possible that...", ma non ne sono sicuro al 100%.
Tschüss,
Enrico il Pentolaio.
--
"There are only two kinds of people who really are fascinating - people who 
know absolutely everything, and people who know absolutely nothing." (Oscar 
Wilde, The Picture of Dorian Gray) 

>> in case that you'd want...
Direi: "in case you want..."

 Enrico il Pentolaio.
Grazie per il tuo aiuto.
billiejoex 


Mike

 Direi: "in case you want..."
Possibly ; I'd simply say 'if you wanted ' :'A system like this could be 
useful if you wanted to make...'
Also in line 2 the OP uses 'in case that' (which is never possible in 
English) . Here 'in case a certain IP attempts to connect' is correct , but 
I think it probably doesn't convey the intended meaning . 'I will wear a hat 
in case it rains' means I wear my hat whether it rains or not , in 
anticipation of possible rain . Here , I think the intention is 'nel caso 
che' - i.e. on each and every occasion that a certain IP does attempt to 
connect etc., the system opens a specified port ; so I would say
 'in the event that'  (or just 'whenever' , or even 'if') .
Mike 

 to gain unauthorized access by moving on the host's machine or by spoofing
'prevents MITM gaining' (or , strictly , 'prevents MITM's gaining' ('prevent 
to' isn't possible in English)
Mike 

 meaning)
Ops!
In questa frase ho toppato proprio!!
:-DDD


 Grazie per il tuo aiuto.
Prego!
Tschüss,
Enrico il Pentolaio.
P.S. Mi sono appena accorto che ti ho anche corretto un errore che non hai 
fatto, ossia quando dici "sequences have to....". In questo caso ovviamente 
va bene "have" e non "has" come ti ho scritto io per chissà quale motivo. 
Per fortuna Mike mi ha corretto al volo. :-)


 wrote in message
news:q4nEf.64683$av6....@tornado.fastwebnet.it...

hash-based, as you state in another section
(hashed authentication, hash-based authentication)
Maybe you could post a revised version of your text, after
implementing those changes you deem appropriate, so we could have
another look at it?
Joe from Massachusetts

Grazie davvero.
Gia che ci sono (sempre se avete voglia ovviamente) vi chiederei di darmi 
un'occhiata anche a questo testo, se possibile: 
http://billiejoex.altervista.org/Prj_Py_soicmp.shtml

 wrote in message 
news:M_KEf.66816$av6....@tornado.fastwebnet.it...

Mostly typos :-
'Soicmp consists in two free and open source application'  - 'Soicmp 
consists OF two free and open source applicationS'
'must respect a certain protocol rules' -  'must respect certain protocol 
rules'
'indipendent' (twice)  -  'independent'
'in uniques "one-way" etc packets' - 'in unique etc'
'the correct packets delivering'  -  'the correct packets delivery'  (?)
'things becomes a little bit harder'  - 'things become a little bit harder'
'choosen'  -  'chosen'
'priviledges'  -  'privileges'
'succesfully' -  'successfully'
'specifies a single NIC on witch listen on'  -  'witch' ? strega ? is this 
IT-speak , or should it be 'switch' ?
Mike

 IT-speak , or should it be 'switch' ?
No, sarebbe proprio 'witch'. E' scorretto?
Volevo dire:
"specifica una singola interfaccia su cui stare/mettersi in ascolto." 

 No, sarebbe proprio 'witch'.
"witch" è "strega" e non c'entra molto, direi. :)
Tu pensavi a "which", ma in questo caso puoi dire semplicemente "... 
specifies a single NIC to listen on". Se vuoi usare "which", dirai: "... a 
single NIC on which to listen".
Max

 ha scritto nel messaggio 
news:ds0krk$sal$1...@newsreader.mailgate.org...

Azz! E' vero hai ragione. Grazie davvero. Per ora pare essere tutto. :-)
PS - A breve dovrei rilasciare un'altra documentazione simile riguardo un 
altro applicativo. Spero di poter contare di nuovo sul tuo ineccepibile e 
gentile aiuto.
Saluti.