PenTest/nmap
1
0
Fork 0
mirror of https://github.com/nmap/nmap.git synced 2025-12-07 13:11:28 +00:00
Code Issues Projects Releases Wiki Activity

Update with new mailing list addresses.

Browse Source
This commit is contained in:
david
2012-12-06 02:23:34 +00:00
parent 6a42ef47c0
commit ec53dc049a
45 changed files with 93 additions and 93 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
CHANGELOG
View File

@@ -9250,7 +9250,7 @@ o The write buffer length increased in 4.03 was increased even further
"log_vwrite: write buffer not large enough -- need to increase" "log_vwrite: write buffer not large enough -- need to increase"
o Added a note to the Nmap configure dragon that people sick of him o Added a note to the Nmap configure dragon that people sick of him
can submit their own ASCII art to nmap-dev@insecure.org . If you can submit their own ASCII art to dev@nmap.org . If you
are wondering WTF I am talking about, it is probably because only are wondering WTF I am talking about, it is probably because only
most elite Nmap users -- the ones who compile from source on UNIX -- most elite Nmap users -- the ones who compile from source on UNIX --
get to see the 'l33t ASCII Art. get to see the 'l33t ASCII Art.

8
HACKING
View File

@@ -12,7 +12,7 @@ it. This also allows you to audit the software for security holes
Source code also allows you to port Nmap to new platforms, fix bugs, Source code also allows you to port Nmap to new platforms, fix bugs,
and add new features. You are highly encouraged to send your changes and add new features. You are highly encouraged to send your changes
to nmap-dev@insecure.org for possible incorporation into the main to dev@nmap.org for possible incorporation into the main
distribution. By sending these changes to Fyodor or one of the distribution. By sending these changes to Fyodor or one of the
Insecure.Org development mailing lists, it is assumed that you are Insecure.Org development mailing lists, it is assumed that you are
offering the Nmap Project (Insecure.Com LLC) unlimited, non-exclusive offering the Nmap Project (Insecure.Com LLC) unlimited, non-exclusive
@@ -31,10 +31,10 @@ down and patch a problem, bug reports are always welcome.
Hackers interested in something more major, such as a new feature, are Hackers interested in something more major, such as a new feature, are
encouraged to send a mail describing their plans to encouraged to send a mail describing their plans to
nmap-dev@insecure.org . This is a good way to solicit feedback on dev@nmap.org . This is a good way to solicit feedback on
your proposals. List members are often very willing to help. You your proposals. List members are often very willing to help. You
might want to subscribe to that mailing list as well -- send a blank might want to subscribe to that mailing list as well -- send a blank
email to nmap-dev-subscribe@insecure.org . While you are at it, you email to dev-subscribe@nmap.org . While you are at it, you
might also want to subscribe to nmap-hackers via the same mechanism. might also want to subscribe to nmap-hackers via the same mechanism.
Web archives of those lists are at http://seclists.org . Web archives of those lists are at http://seclists.org .
@@ -66,7 +66,7 @@ How to make code contributions
------------------------------ ------------------------------
The preferred mechanism for submitted changes is unified diffs against The preferred mechanism for submitted changes is unified diffs against
the latest SVN trunk. Please send them to nmap-dev@insecure.org . the latest SVN trunk. Please send them to dev@nmap.org .
Get a local copy of the SVN trunk: Get a local copy of the SVN trunk:

2
docs/legal-notices.xml
View File

@@ -83,7 +83,7 @@ run it. This also allows you to audit the software for security holes
<para>Source code also allows you to port Nmap to new platforms, fix bugs, <para>Source code also allows you to port Nmap to new platforms, fix bugs,
and add new features. You are highly encouraged to send your changes and add new features. You are highly encouraged to send your changes
to <email>nmap-dev@insecure.org</email> for possible incorporation to <email>dev@nmap.org</email> for possible incorporation
into the main distribution. By sending these changes to Fyodor or one into the main distribution. By sending these changes to Fyodor or one
of the Insecure.Org development mailing lists, it is assumed that you of the Insecure.Org development mailing lists, it is assumed that you
are offering the Nmap Project (Insecure.Com LLC) the unlimited, are offering the Nmap Project (Insecure.Com LLC) the unlimited,

4
docs/man-xlate/nmap-man-de.xml
View File

@@ -4329,11 +4329,11 @@ Sie in den <citetitle>nmap-dev</citetitle>-Archiven unter
<ulink url="http://seclists.org/" />.<indexterm><primary><citetitle>nmap-dev</citetitle> Mailingliste</primary></indexterm> <ulink url="http://seclists.org/" />.<indexterm><primary><citetitle>nmap-dev</citetitle> Mailingliste</primary></indexterm>
Lesen Sie auch diese Manpage vollständig. Wenn Sie keine Lösung finden, Lesen Sie auch diese Manpage vollständig. Wenn Sie keine Lösung finden,
schicken Sie einen Fehlerbericht per E-Mail an schicken Sie einen Fehlerbericht per E-Mail an
<email>nmap-dev@insecure.org</email>. Beschreiben Sie darin bitte alles, <email>dev@nmap.org</email>. Beschreiben Sie darin bitte alles,
was Sie über das Problem wissen, inklusive der Nmap-Version und der was Sie über das Problem wissen, inklusive der Nmap-Version und der
Betriebssystemversion, unter der Sie Nmap einsetzen. Berichte von Problemen Betriebssystemversion, unter der Sie Nmap einsetzen. Berichte von Problemen
und Fragen zur Anwendung von Nmap werden sehr viel wahrscheinlicher und Fragen zur Anwendung von Nmap werden sehr viel wahrscheinlicher
beantwortet, wenn sie an <email>nmap-dev@insecure.org</email> geschickt beantwortet, wenn sie an <email>dev@nmap.org</email> geschickt
werden statt direkt an Fyodor. Wenn Sie sich erst auf der nmap-dev-Liste werden statt direkt an Fyodor. Wenn Sie sich erst auf der nmap-dev-Liste
eintragen, bevor Sie Ihre E-Mail schicken, entgeht Ihre Nachricht auch eintragen, bevor Sie Ihre E-Mail schicken, entgeht Ihre Nachricht auch
der Moderation und kommt schneller an. Eintragen können Sie sich unter der Moderation und kommt schneller an. Eintragen können Sie sich unter

4
docs/man-xlate/nmap-man-es.xml
View File

@@ -3576,12 +3576,12 @@ medida que se incrementa el nivel de depuraci
archivos de Nmap-dev en <ulink archivos de Nmap-dev en <ulink
url="http://seclists.org/"/>. Tambi<62>n deber<65>as leer este manual url="http://seclists.org/"/>. Tambi<62>n deber<65>as leer este manual
completo. Si esto no te ayuda, env<6E>a un informe de error en ingl<67>s completo. Si esto no te ayuda, env<6E>a un informe de error en ingl<67>s
a <email>nmap-dev@insecure.org</email>. Por favor, incluya todo a <email>dev@nmap.org</email>. Por favor, incluya todo
lo que haya visto del problema, as<61> como qu<71> versi<73>n de Nmap lo que haya visto del problema, as<61> como qu<71> versi<73>n de Nmap
est<73> utilizando y sobre qu<71> versi<73>n del sistema operativo est<73> est<73> utilizando y sobre qu<71> versi<73>n del sistema operativo est<73>
trabajando. Hay muchas m<>s probabilidades de que un informe de trabajando. Hay muchas m<>s probabilidades de que un informe de
fallo o una pregunta sobre el uso de Nmap se contesten si se fallo o una pregunta sobre el uso de Nmap se contesten si se
env<6E>an a nmap-dev@insecure.org que si se env<6E>an directamente a env<6E>an a dev@nmap.org que si se env<6E>an directamente a
Fyodor.</para> Fyodor.</para>
<para>Es mejor enviar parches para arreglar el c<>digo que un <para>Es mejor enviar parches para arreglar el c<>digo que un

4
docs/man-xlate/nmap-man-fr.xml
View File

@@ -2279,11 +2279,11 @@ le temps suppl
signal<61>. Essayez pour cela de mettre l'erreur en argument sur Google signal<61>. Essayez pour cela de mettre l'erreur en argument sur Google
ou parcourez les archives de Nmap-dev sur <ulink url="http://seclists.org/" />. Lisez ce manuel en entier quoiqu'il en ou parcourez les archives de Nmap-dev sur <ulink url="http://seclists.org/" />. Lisez ce manuel en entier quoiqu'il en
soit. Si rien ne semble fonctionner, envoyez un rapport de bogue <20> soit. Si rien ne semble fonctionner, envoyez un rapport de bogue <20>
<email>nmap-dev@insecure.org</email>. Veillez <20> inclure tout ce que vous avez <email>dev@nmap.org</email>. Veillez <20> inclure tout ce que vous avez
appris au sujet de ce bogue ainsi que la version de Nmap concern<72>e appris au sujet de ce bogue ainsi que la version de Nmap concern<72>e
et le syst<73>me d'exploitation que vous utilisez. et le syst<73>me d'exploitation que vous utilisez.
Les rapports de probl<62>mes et les questions sur l'utilisation de Nmap envoy<6F>s <20> Les rapports de probl<62>mes et les questions sur l'utilisation de Nmap envoy<6F>s <20>
nmap-dev@insecure.org ont plus de chance de trouver une r<>ponse que ceux dev@nmap.org ont plus de chance de trouver une r<>ponse que ceux
envoy<6F>s <20> Fyodor directement.</para> envoy<6F>s <20> Fyodor directement.</para>
<para>Les codes de programmes de correction destin<69>s <20> r<>gler des bogues sont encore meilleurs que les rapports de bogues. <para>Les codes de programmes de correction destin<69>s <20> r<>gler des bogues sont encore meilleurs que les rapports de bogues.
Les instructions de base pour cr<63>er des fichiers de programmes de correction avec vos modifications Les instructions de base pour cr<63>er des fichiers de programmes de correction avec vos modifications

4
docs/man-xlate/nmap-man-hr.xml
View File

@@ -2420,9 +2420,9 @@ samoobjašnjavajuće, ali poruke postaju sve čudnije što je nivo debugiranja v
<ulink url="http://www.insecure.org/nmap/"></ulink>. Ukoliko je problem i dalje tu, istražite da li je već <ulink url="http://www.insecure.org/nmap/"></ulink>. Ukoliko je problem i dalje tu, istražite da li je već
otkriven i prijavljen. Pokušajte "zaguglati" poruku o grešci ili otiđite na Nmap-dev arhive na otkriven i prijavljen. Pokušajte "zaguglati" poruku o grešci ili otiđite na Nmap-dev arhive na
<ulink url="http://seclists.org/"></ulink>. Također pročitajte i kompletan manual. Ukoliko ništa od toga ne <ulink url="http://seclists.org/"></ulink>. Također pročitajte i kompletan manual. Ukoliko ništa od toga ne
pomogne, pošaljite izvještaj o grešci na <email>nmap-dev@insecure.org</email>. Molim Vas napišite sve što ste do pomogne, pošaljite izvještaj o grešci na <email>dev@nmap.org</email>. Molim Vas napišite sve što ste do
tad otkrili o problemu, te koju verziju Nmap- imate i koju verziju OS-a imate. Izvještaji o prijavljenim tad otkrili o problemu, te koju verziju Nmap- imate i koju verziju OS-a imate. Izvještaji o prijavljenim
problemima i upiti o korištenju Nmap-a koji su poslani na nmap-dev@insecure.org imaju više šansi da budu problemima i upiti o korištenju Nmap-a koji su poslani na dev@nmap.org imaju više šansi da budu
odgovoreni nego oni poslani direktno Fyodor-u.</para> odgovoreni nego oni poslani direktno Fyodor-u.</para>
<para>Patchevi za otklanjanje bugova su još i bolji od samih prijava. Osnovne upute za kreiranje patch datoteka s <para>Patchevi za otklanjanje bugova su još i bolji od samih prijava. Osnovne upute za kreiranje patch datoteka s

4
docs/man-xlate/nmap-man-hu.xml
View File

@@ -3660,10 +3660,10 @@ kapuk csak egy számként jelennek meg, ha túl sok van belőlük.
is fennáll, nézzen utána, hogy felfedezték-e már mások is. Keressen rá a is fennáll, nézzen utána, hogy felfedezték-e már mások is. Keressen rá a
Google-ban a hibaüzenetre vagy böngéssze át az Nmap fejlesztői listát a Google-ban a hibaüzenetre vagy böngéssze át az Nmap fejlesztői listát a
<ulink url="http://seclists.org/"></ulink> címen. Olvassa végig ezt a leírást <ulink url="http://seclists.org/"></ulink> címen. Olvassa végig ezt a leírást
is. Ha nem talál semmit, küldjön egy hibajelentést az <email>nmap-dev@insecure.org</email> is. Ha nem talál semmit, küldjön egy hibajelentést az <email>dev@nmap.org</email>
címre. Írjon le mindent, amit a hibával kapcsolatban tapasztalt. Adja meg címre. Írjon le mindent, amit a hibával kapcsolatban tapasztalt. Adja meg
pontosan a használt Nmap változatot és a futtató operációs rendszer változatát pontosan a használt Nmap változatot és a futtató operációs rendszer változatát
is. Az nmap-dev@insecure.org címre küldött hibajelzések és az Nmap használatával is. Az dev@nmap.org címre küldött hibajelzések és az Nmap használatával
kapcsolatos kérdések valószínűleg gyorsabban megválaszolásra kerülnek, mintha kapcsolatos kérdések valószínűleg gyorsabban megválaszolásra kerülnek, mintha
azokat közvetlenül a program készítőjének (Fyodor) küldené.</para> azokat közvetlenül a program készítőjének (Fyodor) küldené.</para>

4
docs/man-xlate/nmap-man-id.xml
View File

@@ -3967,10 +3967,10 @@ banyaknya permintaan. Berikan <option>--open</option> untuk hanya melihat port
membrowsing arsip <citetitle>nmap-dev</citetitle> di <ulink url="http://seclists.org/"/>.<indexterm significance="normal"><primary><citetitle>nmap-dev</citetitle> mailing list</primary></indexterm> membrowsing arsip <citetitle>nmap-dev</citetitle> di <ulink url="http://seclists.org/"/>.<indexterm significance="normal"><primary><citetitle>nmap-dev</citetitle> mailing list</primary></indexterm>
Bacalah juga halaman manual ini dengan baik. Bacalah juga halaman manual ini dengan baik.
Jika masih belum selesai juga, kirimkan laporan bug ke Jika masih belum selesai juga, kirimkan laporan bug ke
<email>nmap-dev@insecure.org</email>. Mohon sertakan semua yang <email>dev@nmap.org</email>. Mohon sertakan semua yang
anda telah pelajari mengenai masalah, dan juga versi Nmap dan sistem operasi anda telah pelajari mengenai masalah, dan juga versi Nmap dan sistem operasi
yang anda gunakan. Laporan kesalahan dan pertanyaan penggunaan Nmap yang dikirim ke yang anda gunakan. Laporan kesalahan dan pertanyaan penggunaan Nmap yang dikirim ke
<email>nmap-dev@insecure.org</email> akan lebih mungkin dijawab daripada yang dikirimkan <email>dev@nmap.org</email> akan lebih mungkin dijawab daripada yang dikirimkan
secara langsung ke Fyodor. Jika anda berlangganan ke list nmap-dev secara langsung ke Fyodor. Jika anda berlangganan ke list nmap-dev
sebelum posting, pesan anda akan melewati moderasi dan akan lewat dengan lebih cepat. sebelum posting, pesan anda akan melewati moderasi dan akan lewat dengan lebih cepat.
Berlangganan di <ulink url="http://nmap.org/mailman/listinfo/dev"/>.</para> Berlangganan di <ulink url="http://nmap.org/mailman/listinfo/dev"/>.</para>

4
docs/man-xlate/nmap-man-it.xml
View File

@@ -3275,11 +3275,11 @@ implicita che permette il passaggio di tutto il traffico proveniente dalla porta
messaggio di errore o sfogliare l'archivio Nmap-dev. Leggi messaggio di errore o sfogliare l'archivio Nmap-dev. Leggi
inoltre tutta questa pagina di manuale. Se nulla di questo inoltre tutta questa pagina di manuale. Se nulla di questo
riguarda il tuo caso, manda una segnalazione di bug a riguarda il tuo caso, manda una segnalazione di bug a
<email>nmap-dev@insecure.org</email>. Accertati di includere <email>dev@nmap.org</email>. Accertati di includere
ogni cosa che sei riuscito a sapere sul problema, la versione di ogni cosa che sei riuscito a sapere sul problema, la versione di
Nmap che stai usando e su quale sistema operativo la stai Nmap che stai usando e su quale sistema operativo la stai
usando. Segnalazioni di problemi ed eventuali domande sull'uso usando. Segnalazioni di problemi ed eventuali domande sull'uso
di Nmap inviate a nmap-dev@insecure.org hanno piu` probabilita di Nmap inviate a dev@nmap.org hanno piu` probabilita
di avere risposta di quelle inviate a Fyodor di avere risposta di quelle inviate a Fyodor
direttamente.</para> direttamente.</para>

2
docs/man-xlate/nmap-man-jp.xml
View File

@@ -1349,7 +1349,7 @@ rttvar: 14987 to: 100000</computeroutput>。こうした行の内容が理解で
<refsect1 id="man-bugs"> <refsect1 id="man-bugs">
<title>バグ</title> <title>バグ</title>
<para>Nmapも作者と同様に完全ではない。それでもNmapのほうは、ユーザによるバグの報告やパッチの作成のおかげで、よりよいものにしてゆくことができる。Nmapを使っていて、思い通りに動かない場合は、まず<ulink url="http://www.insecure.org/nmap/"/>から入手できる最新のバージョンにアップグレードしてみる。問題が続くようなら、すでに発見・対処が行われた問題かどうかを調査して確かめる。エラーメッセージをGoogle検索したり、<ulink url="http://seclists.org/"/>でNmap-devアーカイブを閲覧したりしてみる。このmanページも全体に目を通した方がよい。それでもどうにもならない場合は、バグレポートを<email>nmap-dev@insecure.org</email>宛てにメールで送ること。メールには、使用しているNmapのバージョンと、Nmapを実行しているOSの名前とバージョンなどの情報だけでなく、問題に関して分かったことは何でも書いていただきたい。問題の報告やNmapの使い方についての質問などは、nmap-dev@insecure.org宛てに送るほうが、筆者宛てに直接送るよりも返事がある可能性ははるかに高い。 </para> <para>Nmapも作者と同様に完全ではない。それでもNmapのほうは、ユーザによるバグの報告やパッチの作成のおかげで、よりよいものにしてゆくことができる。Nmapを使っていて、思い通りに動かない場合は、まず<ulink url="http://www.insecure.org/nmap/"/>から入手できる最新のバージョンにアップグレードしてみる。問題が続くようなら、すでに発見・対処が行われた問題かどうかを調査して確かめる。エラーメッセージをGoogle検索したり、<ulink url="http://seclists.org/"/>でNmap-devアーカイブを閲覧したりしてみる。このmanページも全体に目を通した方がよい。それでもどうにもならない場合は、バグレポートを<email>dev@nmap.org</email>宛てにメールで送ること。メールには、使用しているNmapのバージョンと、Nmapを実行しているOSの名前とバージョンなどの情報だけでなく、問題に関して分かったことは何でも書いていただきたい。問題の報告やNmapの使い方についての質問などは、dev@nmap.org宛てに送るほうが、筆者宛てに直接送るよりも返事がある可能性ははるかに高い。 </para>
<para>またバグレポートより、バグを修正するためのコードパッチのほうが歓迎される。ユーザ自身のコード変更によるパッチファイルの作成方法についての基本的な注意事項は<ulink url="http://www.insecure.org/nmap/data/HACKING"/> で参照できる。パッチは、nmap-dev宛てに送る(推奨)か、筆者Fyodorまで直接送っていただきたい。</para> <para>またバグレポートより、バグを修正するためのコードパッチのほうが歓迎される。ユーザ自身のコード変更によるパッチファイルの作成方法についての基本的な注意事項は<ulink url="http://www.insecure.org/nmap/data/HACKING"/> で参照できる。パッチは、nmap-dev宛てに送る(推奨)か、筆者Fyodorまで直接送っていただきたい。</para>
</refsect1> </refsect1>

4
docs/man-xlate/nmap-man-pl.xml
View File

@@ -3066,11 +3066,11 @@ podobnie jak i UDP.</para>
b&#322;&#281;du lub poprzegl&#261;daj archiwa listy dyskusyjnej Nmap-dev pod adresem b&#322;&#281;du lub poprzegl&#261;daj archiwa listy dyskusyjnej Nmap-dev pod adresem
<ulink url="http://seclists.org/"/>. Przeczytaj r&#243;wnie&#380; ca&#322;a dokumentacj&#281;. <ulink url="http://seclists.org/"/>. Przeczytaj r&#243;wnie&#380; ca&#322;a dokumentacj&#281;.
Je&#347;li nic nie pomo&#380;e, wy&#347;lij raport opisuj&#261;cy b&#322;&#261;d po angielsku na adres Je&#347;li nic nie pomo&#380;e, wy&#347;lij raport opisuj&#261;cy b&#322;&#261;d po angielsku na adres
<email>nmap-dev@insecure.org</email>. Prosz&#281; do&#322;&#261;cz wszystko co uda&#322;o Ci <email>dev@nmap.org</email>. Prosz&#281; do&#322;&#261;cz wszystko co uda&#322;o Ci
si&#281; ustali&#263; na temat tego problemu, jak r&#243;wnie&#380; informacj&#281; o u&#380;ywanej si&#281; ustali&#263; na temat tego problemu, jak r&#243;wnie&#380; informacj&#281; o u&#380;ywanej
wersji Nmapa i systemie operacyjnym na kt&#243;rym jest uruchamiany. wersji Nmapa i systemie operacyjnym na kt&#243;rym jest uruchamiany.
Opisy problem&#243;w i pytania dotycz&#261;ce u&#380;ywania Nmapa wys&#322;ane na adres Opisy problem&#243;w i pytania dotycz&#261;ce u&#380;ywania Nmapa wys&#322;ane na adres
nmap-dev@insecure.org z wi&#281;kszym prawdopodobie&#324;stwem doczekaj&#261; sie dev@nmap.org z wi&#281;kszym prawdopodobie&#324;stwem doczekaj&#261; sie
szybkiej odpowiedzi, ni&#380; wys&#322;ane bezpo&#347;rednio do Fyodora.</para> szybkiej odpowiedzi, ni&#380; wys&#322;ane bezpo&#347;rednio do Fyodora.</para>
<para>Poprawki b&#322;&#281;dnego kodu s&#261; milej widziane, ni&#380; opisy b&#322;ed&#243;w. <para>Poprawki b&#322;&#281;dnego kodu s&#261; milej widziane, ni&#380; opisy b&#322;ed&#243;w.

2
docs/man-xlate/nmap-man-pt_BR.xml
View File

@@ -3794,7 +3794,7 @@ EXAMPLES:
Tente procurar no Google pela mensagem de erro ou navegar nos arquivos Tente procurar no Google pela mensagem de erro ou navegar nos arquivos
da Nmap-dev em <ulink url="http://seclists.org/" />. Se não encontrar da Nmap-dev em <ulink url="http://seclists.org/" />. Se não encontrar
nada, envie uma mensagem com um relatório do erro para nada, envie uma mensagem com um relatório do erro para
<email>nmap-dev@insecure.org</email>. Por favor, inclua tudo o que <email>dev@nmap.org</email>. Por favor, inclua tudo o que
souber sobre o problema, bem como a versão do Nmap que você está souber sobre o problema, bem como a versão do Nmap que você está
executando e em qual versão e sistema operacional você está executando e em qual versão e sistema operacional você está
rodando-o.</para> rodando-o.</para>

2
docs/man-xlate/nmap-man-pt_PT.xml
View File

@@ -3096,7 +3096,7 @@ EXEMPLOS:
encaminhado. Tente procurar no Google pela mensagem de erro ou navegar encaminhado. Tente procurar no Google pela mensagem de erro ou navegar
nos arquivos da Nmap-dev em <ulink url="http://seclists.org/" />. Se n<>o nos arquivos da Nmap-dev em <ulink url="http://seclists.org/" />. Se n<>o
encontrar nada envie uma mensagem com um relat<61>rio do erro para encontrar nada envie uma mensagem com um relat<61>rio do erro para
<email>nmap-dev@insecure.org</email>. Por favor inclua tudo o que <email>dev@nmap.org</email>. Por favor inclua tudo o que
souber sobre o problema bem como a vers<72>o do Nmap que est<73> souber sobre o problema bem como a vers<72>o do Nmap que est<73>
executando e em qual vers<72>o e sistema operativo que est<73> a usar.</para> executando e em qual vers<72>o e sistema operativo que est<73> a usar.</para>

4
docs/man-xlate/nmap-man-ro.xml
View File

@@ -2957,10 +2957,10 @@
eroare sau navigand prin arhivele Nmap-dev la eroare sau navigand prin arhivele Nmap-dev la
<ulink url="http://seclists.org/"></ulink>. Cititi acest manual in <ulink url="http://seclists.org/"></ulink>. Cititi acest manual in
intregime de asemenea. Daca nimic nu se rezolva, trimiteti un mail la intregime de asemenea. Daca nimic nu se rezolva, trimiteti un mail la
<email>nmap-dev@insecure.org</email>. Va rog sa includeti tot ce ati <email>dev@nmap.org</email>. Va rog sa includeti tot ce ati
aflat despre problema, precum si versiunea de Nmap pe care o folositi si aflat despre problema, precum si versiunea de Nmap pe care o folositi si
sistemul de operare. Problemele si intrebarile legate de utilizarea sistemul de operare. Problemele si intrebarile legate de utilizarea
Nmapului trimise la nmap-dev@insecure.org au sanse mult mai mari de a li Nmapului trimise la dev@nmap.org au sanse mult mai mari de a li
se raspunde decat cele trimise direct la Fyodor.</para> se raspunde decat cele trimise direct la Fyodor.</para>
<para>Patchurile de rezolvare a problemelor sunt si mai bune decat <para>Patchurile de rezolvare a problemelor sunt si mai bune decat
rapoartele despre problema in sine. Instructiuni de baza pentru crearea rapoartele despre problema in sine. Instructiuni de baza pentru crearea

4
docs/man-xlate/nmap-man-ru.xml
View File

@@ -3477,9 +3477,9 @@ rttvar: 14987 to: 100000</computeroutput>. Если вы не понимаете
Попробуйте поискать сообщения об ошибках на нашей странице поиска <ulink url="http://insecure.org/search.html"/> Попробуйте поискать сообщения об ошибках на нашей странице поиска <ulink url="http://insecure.org/search.html"/>
или в Google. Также попробуйте просмотреть <citetitle>nmap-dev</citetitle> архивы на <ulink url="http://seclists.org/"/>.<indexterm significance="normal"><primary><citetitle>nmap-dev</citetitle> mailing list</primary></indexterm> или в Google. Также попробуйте просмотреть <citetitle>nmap-dev</citetitle> архивы на <ulink url="http://seclists.org/"/>.<indexterm significance="normal"><primary><citetitle>nmap-dev</citetitle> mailing list</primary></indexterm>
Также прочитайте полностью страницу руководства. Если ничего не помогло, отправьте сообщение об ошибке на Также прочитайте полностью страницу руководства. Если ничего не помогло, отправьте сообщение об ошибке на
<email>nmap-dev@insecure.org</email>. Пожалуйста, включите всю известную вам информацию об ошибке, какую версию <email>dev@nmap.org</email>. Пожалуйста, включите всю известную вам информацию об ошибке, какую версию
Nmap вы используете, и на какой операционной системы вы запускаете Nmap. Сообщения о проблемах и вопросы по Nmap вы используете, и на какой операционной системы вы запускаете Nmap. Сообщения о проблемах и вопросы по
использованию Nmap отправленные на <email>nmap-dev@insecure.org</email> имеют больше шансов на ответ, чем если бы использованию Nmap отправленные на <email>dev@nmap.org</email> имеют больше шансов на ответ, чем если бы
вы послали их непосредственно Fyodor'у. Если вы подпишитесь на рассылку nmap-dev перед отправкой сообщения, вы послали их непосредственно Fyodor'у. Если вы подпишитесь на рассылку nmap-dev перед отправкой сообщения,
то ваше сообщение будет обработано быстрее. Подпишитесь на рассылку на <ulink url="http://nmap.org/mailman/listinfo/dev"/>.</para> то ваше сообщение будет обработано быстрее. Подпишитесь на рассылку на <ulink url="http://nmap.org/mailman/listinfo/dev"/>.</para>

4
docs/man-xlate/nmap-man-sk.xml
View File

@@ -2821,10 +2821,10 @@ Niektore riadku su samovysvetlujuce, no zvysovanim stupna debugovania sa straca
s vyrazom chybovej spravy alebo prehladajte archivy Nmap-dev na adrese s vyrazom chybovej spravy alebo prehladajte archivy Nmap-dev na adrese
<ulink url="http://seclists.org/"/>. Precitajte si aj tento plny manual. <ulink url="http://seclists.org/"/>. Precitajte si aj tento plny manual.
Ak nenajdete nic podobne, poslite mail o bugu na adresu Ak nenajdete nic podobne, poslite mail o bugu na adresu
<email>nmap-dev@insecure.org</email>. Zahrnte vsetko, co ste sa dozvedeli <email>dev@nmap.org</email>. Zahrnte vsetko, co ste sa dozvedeli
o probleme spolu s verziou Nmapu a operacnym systemom. Spravy o problemoch o probleme spolu s verziou Nmapu a operacnym systemom. Spravy o problemoch
a otazky na pouzivanie Nmapu budu ovela pravdepodobnejsie zodpovedane, ak budu odoslane a otazky na pouzivanie Nmapu budu ovela pravdepodobnejsie zodpovedane, ak budu odoslane
na nmap-dev@insecure.org namiesto odosielania priamo Fyodorovi.</para> na dev@nmap.org namiesto odosielania priamo Fyodorovi.</para>
<para>Patche s kodom na opravu bugov su este lepsie ako samotne spravy o bugoch. Zakladne <para>Patche s kodom na opravu bugov su este lepsie ako samotne spravy o bugoch. Zakladne
instrukcie na tvorbu suborov patchov s vasimi zmenami su dostupne na instrukcie na tvorbu suborov patchov s vasimi zmenami su dostupne na

4
docs/man-xlate/nmap-man-zh.xml
View File

@@ -2324,9 +2324,9 @@ rttvar: 14987 to: 100000</computeroutput>。如果对某行输出不明白，
升级最新版本。如果总问题仍然存在，需要进行调查以确定问题是否 升级最新版本。如果总问题仍然存在，需要进行调查以确定问题是否
已经被解决。在<ulink url="http://seclists.org/"/>尝试搜索出错消息或 已经被解决。在<ulink url="http://seclists.org/"/>尝试搜索出错消息或
浏览Nmap-dev档案，以及仔细阅读使用手册。如果问题还是不能解决，发送 浏览Nmap-dev档案，以及仔细阅读使用手册。如果问题还是不能解决，发送
Bug报告至<email>nmap-dev@insecure.org</email>。在报告中包含所有 Bug报告至<email>dev@nmap.org</email>。在报告中包含所有
有关问题的信息，以及所使用的Nmap版本、操作系统版本。问题报告以及 有关问题的信息，以及所使用的Nmap版本、操作系统版本。问题报告以及
Nmap的使用问题发送给nmap-dev@insecure.org比直接发送给Gyodor能更好回答。</para> Nmap的使用问题发送给dev@nmap.org比直接发送给Gyodor能更好回答。</para>
<para>解决Bug的代码补丁比Bug报告更受欢迎，在<ulink url="http://www.insecure.org/nmap/data/HACKING"/> <para>解决Bug的代码补丁比Bug报告更受欢迎，在<ulink url="http://www.insecure.org/nmap/data/HACKING"/>
可获得建立补丁文件的基本指令。补丁可发送给nmap-dev(建议) 可获得建立补丁文件的基本指令。补丁可发送给nmap-dev(建议)

4
docs/refguide.xml
View File

@@ -4477,11 +4477,11 @@ Service scan Timing: About 33.33% done; ETC: 20:57 (0:00:12 remaining)
url="http://seclists.org/" />.<indexterm><primary><citetitle>nmap-dev</citetitle> mailing list</primary></indexterm> url="http://seclists.org/" />.<indexterm><primary><citetitle>nmap-dev</citetitle> mailing list</primary></indexterm>
Read this full manual page as Read this full manual page as
well. If nothing comes of this, mail a bug report to well. If nothing comes of this, mail a bug report to
<email>nmap-dev@insecure.org</email>. Please include everything <email>dev@nmap.org</email>. Please include everything
you have learned about the problem, as well as what version of you have learned about the problem, as well as what version of
Nmap you are running and what operating system version it is Nmap you are running and what operating system version it is
running on. Problem reports and Nmap usage questions sent to running on. Problem reports and Nmap usage questions sent to
<email>nmap-dev@insecure.org</email> are far more likely to be answered than <email>dev@nmap.org</email> are far more likely to be answered than
those sent to Fyodor directly. If you subscribe to the nmap-dev those sent to Fyodor directly. If you subscribe to the nmap-dev
list before posting, your message will bypass moderation and get list before posting, your message will bypass moderation and get
through more quickly. Subscribe at <ulink url="http://nmap.org/mailman/listinfo/dev"/>.</para> through more quickly. Subscribe at <ulink url="http://nmap.org/mailman/listinfo/dev"/>.</para>

4
docs/zenmap.xml
View File

@@ -135,10 +135,10 @@
the <citetitle>nmap-dev</citetitle> archives at <ulink url="http://seclists.org/" />. the <citetitle>nmap-dev</citetitle> archives at <ulink url="http://seclists.org/" />.
Read this Read this
full manual page as well. If nothing comes of this, mail a bug report to full manual page as well. If nothing comes of this, mail a bug report to
<email>nmap-dev@insecure.org</email>. Please include everything you have <email>dev@nmap.org</email>. Please include everything you have
learned about the problem, as well as what version of Zenmap you are running learned about the problem, as well as what version of Zenmap you are running
and what operating system version it is running on. Problem reports and and what operating system version it is running on. Problem reports and
Zenmap usage questions sent to nmap-dev@insecure.org are far more likely to Zenmap usage questions sent to dev@nmap.org are far more likely to
be answered than those sent to Fyodor directly.</para> be answered than those sent to Fyodor directly.</para>
<para>Code patches to fix bugs are even better than bug reports. Basic <para>Code patches to fix bugs are even better than bug reports. Basic

6
ncat/docs/ncat.xml
View File

@@ -887,11 +887,11 @@
<indexterm><primary><citetitle>nmap-dev</citetitle> mailing list</primary></indexterm> <indexterm><primary><citetitle>nmap-dev</citetitle> mailing list</primary></indexterm>
Read this full manual page as Read this full manual page as
well. If nothing comes of this, mail a bug report to well. If nothing comes of this, mail a bug report to
<email>nmap-dev@insecure.org</email>. Please include everything <email>dev@nmap.org</email>. Please include everything
you have learned about the problem, as well as what version of you have learned about the problem, as well as what version of
Ncat you are running and what operating system version it is Ncat you are running and what operating system version it is
running on. Problem reports and Ncat usage questions sent to running on. Problem reports and Ncat usage questions sent to
nmap-dev@insecure.org are far more likely to be answered than dev@nmap.org are far more likely to be answered than
those sent to Fyodor directly.</para> those sent to Fyodor directly.</para>
<para>Code patches to fix bugs are even better than bug reports. <para>Code patches to fix bugs are even better than bug reports.
@@ -965,7 +965,7 @@ run it. This also allows you to audit the software for security holes
<para>Source code also allows you to port Nmap (which includes Ncat) <para>Source code also allows you to port Nmap (which includes Ncat)
to new platforms, fix bugs, and add new features. You are highly to new platforms, fix bugs, and add new features. You are highly
encouraged to send your changes to encouraged to send your changes to
<email>nmap-dev@insecure.org</email> for possible incorporation into <email>dev@nmap.org</email> for possible incorporation into
the main distribution. By sending these changes to Fyodor or one of the main distribution. By sending these changes to Fyodor or one of
the Insecure.Org development mailing lists, it is assumed that you are the Insecure.Org development mailing lists, it is assumed that you are
offering the Nmap Project (Insecure.Com LLC) the unlimited, offering the Nmap Project (Insecure.Com LLC) the unlimited,

2
ncat/ncat_main.c
View File

@@ -768,7 +768,7 @@ int main(int argc, char *argv[])
bye("UDP mode does not support the -k or --keep-open options, except with --exec or --sh-exec."); bye("UDP mode does not support the -k or --keep-open options, except with --exec or --sh-exec.");
if (o.broker) if (o.broker)
bye("UDP mode does not support connection brokering.\n\ bye("UDP mode does not support connection brokering.\n\
If this feature is important to you, write nmap-dev@insecure.org with a\n\ If this feature is important to you, write dev@nmap.org with a\n\
description of how you intend to use it, as an aid to deciding how UDP\n\ description of how you intend to use it, as an aid to deciding how UDP\n\
connection brokering should work."); connection brokering should work.");
} }

2
ndiff/docs/ndiff.xml
View File

@@ -373,7 +373,7 @@ ln -sf scan-$date.xml scan-prev.xml
<title>Bugs</title> <title>Bugs</title>
<para> <para>
Report bugs to the <citetitle>nmap-dev</citetitle> mailing list at Report bugs to the <citetitle>nmap-dev</citetitle> mailing list at
<email>nmap-dev@insecure.org</email>. <email>dev@nmap.org</email>.
</para> </para>
</refsect1> </refsect1>

4
nping/docs/nping-man.xml
View File

@@ -3532,11 +3532,11 @@ NSOCK (1.0000s) Callback: TIMER SUCCESS for EID 12; tcpconnect_event_handler<con
<primary><citetitle>nmap-dev</citetitle> mailing list</primary></indexterm> <primary><citetitle>nmap-dev</citetitle> mailing list</primary></indexterm>
Read this full manual page as Read this full manual page as
well. If nothing comes out of this, mail a bug report to well. If nothing comes out of this, mail a bug report to
<email>nmap-dev@insecure.org</email>. Please include everything <email>dev@nmap.org</email>. Please include everything
you have learned about the problem, as well as what version of you have learned about the problem, as well as what version of
Nping you are running and what operating system version it is Nping you are running and what operating system version it is
running on. Problem reports and Nping usage questions sent to running on. Problem reports and Nping usage questions sent to
<email>nmap-dev@insecure.org</email> are far more likely to be answered than <email>dev@nmap.org</email> are far more likely to be answered than
those sent to Fyodor directly. If you subscribe to the nmap-dev those sent to Fyodor directly. If you subscribe to the nmap-dev
list before posting, your message will bypass moderation and get list before posting, your message will bypass moderation and get
through more quickly. Subscribe at through more quickly. Subscribe at

2
nselib/data/http-fingerprints.lua
View File

@@ -64,7 +64,7 @@ local table = require "table"
-- captures can be used with \1, \2, etc. -- captures can be used with \1, \2, etc.
-- --
-- --
-- If you have any questions, feel free to email nmap-dev@insecure.org or contact Ron Bowes! -- If you have any questions, feel free to email dev@nmap.org or contact Ron Bowes!
-- --
-- CHANGELOG: -- CHANGELOG:
-- Added 120 new signatures taken from exploit-db.com archives from July 2009 to July 2011 [Paulino Calderon] -- Added 120 new signatures taken from exploit-db.com archives from July 2009 to July 2011 [Paulino Calderon]

2
scripts/http-sql-injection.nse
View File

@@ -43,7 +43,7 @@ categories = {"intrusive", "vuln"}
-- comments). The default file is nselib/data/http-sql-errors.lst -- comments). The default file is nselib/data/http-sql-errors.lst
-- which was taken from fuzzdb project, for more info, see http://code.google.com/p/fuzzdb/. -- which was taken from fuzzdb project, for more info, see http://code.google.com/p/fuzzdb/.
-- If someone detects some strings in that file causing a lot of false positives, -- If someone detects some strings in that file causing a lot of false positives,
-- then please report them to nmap-dev@insecure.org. -- then please report them to dev@nmap.org.
-- --
-- @output -- @output
-- PORT STATE SERVICE -- PORT STATE SERVICE

6
scripts/smb-psexec.nse
View File

@@ -293,7 +293,7 @@ files are deleted.
And that's how it works! And that's how it works!
Please post any questions, or suggestions for better modules, to nmap-dev@insecure.org. Please post any questions, or suggestions for better modules, to dev@nmap.org.
And, as usual, since this tool can be dangerous and can easily be viewed as a malicious And, as usual, since this tool can be dangerous and can easily be viewed as a malicious
tool -- use this responsibly, and don't break any laws with it. tool -- use this responsibly, and don't break any laws with it.
@@ -1279,9 +1279,9 @@ local function parse_output(config, data)
-- Go to the next module, and make sure it exists -- Go to the next module, and make sure it exists
mod = config.enabled_modules[module_num + 1] mod = config.enabled_modules[module_num + 1]
if(mod == nil) then if(mod == nil) then
stdnse.print_debug(1, "Server's response wasn't formatted properly (mod %d); if you can reproduce, place report to nmap-dev@insecure.org", module_num) stdnse.print_debug(1, "Server's response wasn't formatted properly (mod %d); if you can reproduce, place report to dev@nmap.org", module_num)
stdnse.print_debug(1, "--\n" .. string.gsub("%%", "%%", data) .. "\n--") stdnse.print_debug(1, "--\n" .. string.gsub("%%", "%%", data) .. "\n--")
return false, "Server's response wasn't formatted properly; if you can reproduce, place report to nmap-dev@insecure.org" return false, "Server's response wasn't formatted properly; if you can reproduce, place report to dev@nmap.org"
end end
-- Save this result -- Save this result

2
zenmap/share/zenmap/locale/Makefile
View File

@@ -6,7 +6,7 @@ SOURCEDIRS = zenmapCore zenmapGUI radialnet
PROFILE_EDITOR_XML = share/zenmap/misc/profile_editor.xml PROFILE_EDITOR_XML = share/zenmap/misc/profile_editor.xml
XGETTEXT = xgettext XGETTEXT = xgettext
MSGID_BUGS_ADDRESS = nmap-dev@insecure.org MSGID_BUGS_ADDRESS = dev@nmap.org
ZENMAP_POT = zenmap.pot ZENMAP_POT = zenmap.pot
TMP_POT = tmp.pot TMP_POT = tmp.pot

10
zenmap/share/zenmap/locale/de.po
View File

@@ -6,7 +6,7 @@
msgid "" msgid ""
msgstr "" msgstr ""
"Project-Id-Version: nmap 5.00-3\n" "Project-Id-Version: nmap 5.00-3\n"
"Report-Msgid-Bugs-To: nmap-dev@insecure.org\n" "Report-Msgid-Bugs-To: dev@nmap.org\n"
"POT-Creation-Date: 2010-07-18 07:46-0600\n" "POT-Creation-Date: 2010-07-18 07:46-0600\n"
"PO-Revision-Date: 2009-08-31 21:13+GMT\n" "PO-Revision-Date: 2009-08-31 21:13+GMT\n"
"Last-Translator: Chris Leick <c.leick@vollbio.de>\n" "Last-Translator: Chris Leick <c.leick@vollbio.de>\n"
@@ -163,10 +163,10 @@ msgid ""
"research to determine whether it has already been discovered and addressed. " "research to determine whether it has already been discovered and addressed. "
"Try Googling the error message or browsing the nmap-dev archives at http://" "Try Googling the error message or browsing the nmap-dev archives at http://"
"seclists.org/. Read the full manual page as well. If nothing comes of this, " "seclists.org/. Read the full manual page as well. If nothing comes of this, "
"mail a bug report to <b>&lt;nmap-dev@insecure.org&gt;</b>. Please include " "mail a bug report to <b>&lt;dev@nmap.org&gt;</b>. Please include "
"everything you have learned about the problem, as well as what version of " "everything you have learned about the problem, as well as what version of "
"Nmap you are running and what operating system version it is running on. " "Nmap you are running and what operating system version it is running on. "
"Problem reports and %(nmap)s usage questions sent to nmap-dev@insecure.org " "Problem reports and %(nmap)s usage questions sent to dev@nmap.org "
"are far more likely to be answered than those sent to Fyodor directly.\n" "are far more likely to be answered than those sent to Fyodor directly.\n"
"\n" "\n"
"Code patches to fix bugs are even better than bug reports. Basic " "Code patches to fix bugs are even better than bug reports. Basic "
@@ -185,11 +185,11 @@ msgstr ""
"Versuchen Sie, die Fehlermeldung mit einer Suchmaschine zu finden oder " "Versuchen Sie, die Fehlermeldung mit einer Suchmaschine zu finden oder "
"durchstöbern Sie die Nmap-dev-Archive unter http://seclists.org/. Lesen Sie " "durchstöbern Sie die Nmap-dev-Archive unter http://seclists.org/. Lesen Sie "
"außerdem die vollständige Handbuchseite. Wenn dabei nichts herauskommt, " "außerdem die vollständige Handbuchseite. Wenn dabei nichts herauskommt, "
"mailen Sie einen Fehlerbericht an <b>&lt;nmap-dev@insecure.org&gt;</b>. " "mailen Sie einen Fehlerbericht an <b>&lt;dev@nmap.org&gt;</b>. "
"Bitte fügen Sie alles hinzu, was Sie über das Problem in Erfahrung gebracht " "Bitte fügen Sie alles hinzu, was Sie über das Problem in Erfahrung gebracht "
"haben, auch Ihre Version von Nmap und auf welcher Betriebssystemversion Sie " "haben, auch Ihre Version von Nmap und auf welcher Betriebssystemversion Sie "
"es ausführen. Problemberichte und Fragen zum Aufruf von %(nmap)s, die an " "es ausführen. Problemberichte und Fragen zum Aufruf von %(nmap)s, die an "
"nmap-dev@insecure.org geschickt werden, werden viel lieber beantwortet als " "dev@nmap.org geschickt werden, werden viel lieber beantwortet als "
"solche, die direkt an Fyodor geschickt werden.\n" "solche, die direkt an Fyodor geschickt werden.\n"
"\n" "\n"
"Code-Patches zum Beheben von Fehlern sind sogar besser als Fehlerberichte. " "Code-Patches zum Beheben von Fehlern sind sogar besser als Fehlerberichte. "

BIN
zenmap/share/zenmap/locale/de/LC_MESSAGES/zenmap.mo
View File

Binary file not shown.

10
zenmap/share/zenmap/locale/fr.po
View File

@@ -4,7 +4,7 @@
msgid "" msgid ""
msgstr "" msgstr ""
"Project-Id-Version: Zenmap\n" "Project-Id-Version: Zenmap\n"
"Report-Msgid-Bugs-To: nmap-dev@insecure.org\n" "Report-Msgid-Bugs-To: dev@nmap.org\n"
"POT-Creation-Date: 2010-07-18 07:46-0600\n" "POT-Creation-Date: 2010-07-18 07:46-0600\n"
"PO-Revision-Date: 2011-01-20 23:01+0100\n" "PO-Revision-Date: 2011-01-20 23:01+0100\n"
"Last-Translator: \n" "Last-Translator: \n"
@@ -168,10 +168,10 @@ msgid ""
"research to determine whether it has already been discovered and addressed. " "research to determine whether it has already been discovered and addressed. "
"Try Googling the error message or browsing the nmap-dev archives at http://" "Try Googling the error message or browsing the nmap-dev archives at http://"
"seclists.org/. Read the full manual page as well. If nothing comes of this, " "seclists.org/. Read the full manual page as well. If nothing comes of this, "
"mail a bug report to <b>&lt;nmap-dev@insecure.org&gt;</b>. Please include " "mail a bug report to <b>&lt;dev@nmap.org&gt;</b>. Please include "
"everything you have learned about the problem, as well as what version of " "everything you have learned about the problem, as well as what version of "
"Nmap you are running and what operating system version it is running on. " "Nmap you are running and what operating system version it is running on. "
"Problem reports and %(nmap)s usage questions sent to nmap-dev@insecure.org " "Problem reports and %(nmap)s usage questions sent to dev@nmap.org "
"are far more likely to be answered than those sent to Fyodor directly.\n" "are far more likely to be answered than those sent to Fyodor directly.\n"
"\n" "\n"
"Code patches to fix bugs are even better than bug reports. Basic " "Code patches to fix bugs are even better than bug reports. Basic "
@@ -189,11 +189,11 @@ msgstr ""
"déterminer si cela a déja été découvert et rapporté. Essayez de rechercher " "déterminer si cela a déja été découvert et rapporté. Essayez de rechercher "
"le message d'erreur sur Google ou les archives de développement sur http://" "le message d'erreur sur Google ou les archives de développement sur http://"
"seclists.org/. Lisez aussi le manuel en entier. Si rien de ceci n'aboutit, " "seclists.org/. Lisez aussi le manuel en entier. Si rien de ceci n'aboutit, "
"envoyez un rapport de bug à  <b>&lt;nmap-dev@insecure.org&gt;</b>. Veuillez " "envoyez un rapport de bug à  <b>&lt;dev@nmap.org&gt;</b>. Veuillez "
"inclure tout ce que vous pouvez avoir appris au sujet du problà¨me, ainsi " "inclure tout ce que vous pouvez avoir appris au sujet du problà¨me, ainsi "
"que la version de Nmap que vous utilisez et sur quel systà¨me d'exploitation " "que la version de Nmap que vous utilisez et sur quel systà¨me d'exploitation "
"il est lancé. Les rapports de problà¨mes et les questions sur l'utilisation " "il est lancé. Les rapports de problà¨mes et les questions sur l'utilisation "
"de %(nmap)s envoyés à  nmap-dev@insecure.org ont plus de chance de trouver " "de %(nmap)s envoyés à  dev@nmap.org ont plus de chance de trouver "
"des réponses que ceux envoyés à  Fyodor directement.\n" "des réponses que ceux envoyés à  Fyodor directement.\n"
"\n" "\n"
"Les code correctifs pour réparer un bug sont encore meilleurs que les " "Les code correctifs pour réparer un bug sont encore meilleurs que les "

BIN
zenmap/share/zenmap/locale/fr/LC_MESSAGES/zenmap.mo
View File

Binary file not shown.

8
zenmap/share/zenmap/locale/hr.po
View File

@@ -6,7 +6,7 @@
msgid "" msgid ""
msgstr "" msgstr ""
"Project-Id-Version: hr\n" "Project-Id-Version: hr\n"
"Report-Msgid-Bugs-To: nmap-dev@insecure.org\n" "Report-Msgid-Bugs-To: dev@nmap.org\n"
"POT-Creation-Date: 2010-07-18 07:46-0600\n" "POT-Creation-Date: 2010-07-18 07:46-0600\n"
"PO-Revision-Date: 2009-02-08 23:49+0100\n" "PO-Revision-Date: 2009-02-08 23:49+0100\n"
"Last-Translator: Vlatko Kosturjak <kost@linux.hr>\n" "Last-Translator: Vlatko Kosturjak <kost@linux.hr>\n"
@@ -159,10 +159,10 @@ msgid ""
"research to determine whether it has already been discovered and addressed. " "research to determine whether it has already been discovered and addressed. "
"Try Googling the error message or browsing the nmap-dev archives at http://" "Try Googling the error message or browsing the nmap-dev archives at http://"
"seclists.org/. Read the full manual page as well. If nothing comes of this, " "seclists.org/. Read the full manual page as well. If nothing comes of this, "
"mail a bug report to <b>&lt;nmap-dev@insecure.org&gt;</b>. Please include " "mail a bug report to <b>&lt;dev@nmap.org&gt;</b>. Please include "
"everything you have learned about the problem, as well as what version of " "everything you have learned about the problem, as well as what version of "
"Nmap you are running and what operating system version it is running on. " "Nmap you are running and what operating system version it is running on. "
"Problem reports and %(nmap)s usage questions sent to nmap-dev@insecure.org " "Problem reports and %(nmap)s usage questions sent to dev@nmap.org "
"are far more likely to be answered than those sent to Fyodor directly.\n" "are far more likely to be answered than those sent to Fyodor directly.\n"
"\n" "\n"
"Code patches to fix bugs are even better than bug reports. Basic " "Code patches to fix bugs are even better than bug reports. Basic "
@@ -183,7 +183,7 @@ msgstr ""
"dev@insecure.org&gt;</b>. Molimo uključite sve što ste saznali o problemu, " "dev@insecure.org&gt;</b>. Molimo uključite sve što ste saznali o problemu, "
"kao i inačicu Nmapa koju pokrećete i na kojem se operativnom sustavu izvodi. " "kao i inačicu Nmapa koju pokrećete i na kojem se operativnom sustavu izvodi. "
"Izvješće o problemu i %(nmap)s pitanja oko njegovog korištenja poslana na " "Izvješće o problemu i %(nmap)s pitanja oko njegovog korištenja poslana na "
"nmap-dev@insecure.org će vjerojatno biti prije odgovorena nego poslana " "dev@nmap.org će vjerojatno biti prije odgovorena nego poslana "
"Fyodoru direktno.\n" "Fyodoru direktno.\n"
"\n" "\n"
"Popravci za kod koji ispravljaju greške su mnogo bolji nego izvješće o " "Popravci za kod koji ispravljaju greške su mnogo bolji nego izvješće o "

BIN
zenmap/share/zenmap/locale/hr/LC_MESSAGES/zenmap.mo
View File

Binary file not shown.

14
zenmap/share/zenmap/locale/it.po
View File

@@ -4,7 +4,7 @@
msgid "" msgid ""
msgstr "" msgstr ""
"Project-Id-Version: Zenmap\n" "Project-Id-Version: Zenmap\n"
"Report-Msgid-Bugs-To: nmap-dev@insecure.org\n" "Report-Msgid-Bugs-To: dev@nmap.org\n"
"POT-Creation-Date: 2012-05-22 12:52-0700\n" "POT-Creation-Date: 2012-05-22 12:52-0700\n"
"PO-Revision-Date: 2012-05-30 05:00+0100\n" "PO-Revision-Date: 2012-05-30 05:00+0100\n"
"MIME-Version: 1.0\n" "MIME-Version: 1.0\n"
@@ -101,12 +101,12 @@ msgstr "Rapporto di crash"
#: zenmapGUI/CrashReport.py:130 #: zenmapGUI/CrashReport.py:130
#, python-format #, python-format
msgid "An unexpected error has crashed %(app_name)s. Please copy the stack trace below and send it to the <a href=\"mailto:nmap-dev@insecure.org\">nmap-dev@insecure.org</a> mailing list. (<a href=\"http://seclists.org/nmap-dev/\">More about the list.</a>) The developers will see your report and try to fix the problem." msgid "An unexpected error has crashed %(app_name)s. Please copy the stack trace below and send it to the <a href=\"mailto:dev@nmap.org\">dev@nmap.org</a> mailing list. (<a href=\"http://seclists.org/nmap-dev/\">More about the list.</a>) The developers will see your report and try to fix the problem."
msgstr "Un errore inaspettato ha mandato in crash %(app_name)s. Siete pregati di copiare lo stack trace sottostante ed inviarlo alla <a href=\"mailto:nmap-dev@insecure.org\">nmap-dev@insecure.org</a> mailing list. (<a href=\"http://seclists.org/nmap-dev/\">Per saperne di più sulla lista.</a>) Gli sviluppatori vedranno il tuo rapporto e proveranno a risolvere il problema." msgstr "Un errore inaspettato ha mandato in crash %(app_name)s. Siete pregati di copiare lo stack trace sottostante ed inviarlo alla <a href=\"mailto:dev@nmap.org\">dev@nmap.org</a> mailing list. (<a href=\"http://seclists.org/nmap-dev/\">Per saperne di più sulla lista.</a>) Gli sviluppatori vedranno il tuo rapporto e proveranno a risolvere il problema."
#: zenmapGUI/CrashReport.py:138 #: zenmapGUI/CrashReport.py:138
msgid "<b>Copy and email to <a href=\"mailto:nmap-dev@insecure.org\">nmap-dev@insecure.org</a>:</b>" msgid "<b>Copy and email to <a href=\"mailto:dev@nmap.org\">dev@nmap.org</a>:</b>"
msgstr "<b>Copia e spedisci via email a <a href=\"mailto:nmap-dev@insecure.org\">nmap-dev@insecure.org</a>:</b>" msgstr "<b>Copia e spedisci via email a <a href=\"mailto:dev@nmap.org\">dev@nmap.org</a>:</b>"
#: zenmapGUI/OptionBuilder.py:258 #: zenmapGUI/OptionBuilder.py:258
msgid "Choose file" msgid "Choose file"
@@ -789,13 +789,13 @@ msgstr "Come segnalare un errore"
msgid "" msgid ""
"<big><b>How to report a bug</b></big>\n" "<big><b>How to report a bug</b></big>\n"
"\n" "\n"
"Like their author, %(nmap)s and %(app)s aren't perfect. But you can help make it better by sending bug reports or even writing patches. If %(nmap)s doesn't behave the way you expect, first upgrade to the latest version available from <b>%(nmap_web)s</b>. If the problem persists, do some research to determine whether it has already been discovered and addressed. Try Googling the error message or browsing the nmap-dev archives at http://seclists.org/. Read the full manual page as well. If nothing comes of this, mail a bug report to <b>&lt;nmap-dev@insecure.org&gt;</b>. Please include everything you have learned about the problem, as well as what version of Nmap you are running and what operating system version it is running on. Problem reports and %(nmap)s usage questions sent to nmap-dev@insecure.org are far more likely to be answered than those sent to Fyodor directly.\n" "Like their author, %(nmap)s and %(app)s aren't perfect. But you can help make it better by sending bug reports or even writing patches. If %(nmap)s doesn't behave the way you expect, first upgrade to the latest version available from <b>%(nmap_web)s</b>. If the problem persists, do some research to determine whether it has already been discovered and addressed. Try Googling the error message or browsing the nmap-dev archives at http://seclists.org/. Read the full manual page as well. If nothing comes of this, mail a bug report to <b>&lt;dev@nmap.org&gt;</b>. Please include everything you have learned about the problem, as well as what version of Nmap you are running and what operating system version it is running on. Problem reports and %(nmap)s usage questions sent to dev@nmap.org are far more likely to be answered than those sent to Fyodor directly.\n"
"\n" "\n"
"Code patches to fix bugs are even better than bug reports. Basic instructions for creating patch files with your changes are available at http://nmap.org/data/HACKING. Patches may be sent to nmap-dev (recommended) or to Fyodor directly.\n" "Code patches to fix bugs are even better than bug reports. Basic instructions for creating patch files with your changes are available at http://nmap.org/data/HACKING. Patches may be sent to nmap-dev (recommended) or to Fyodor directly.\n"
msgstr "" msgstr ""
"<big><b>Come segnalare un errore</b></big>\n" "<big><b>Come segnalare un errore</b></big>\n"
"\n" "\n"
"Come il loro autore, %(nmap)s e %(app)s non sono perfetti. Ma potete aiutare a renderli migliori inviando segnalazioni d'errore o persino scrivendo patches. Se %(nmap)s non si comporta nel modo che vi aspettate, per prima cosa aggiornatelo all'ultima versione disponibile da <b>%(nmap_web)s</b>. Se il problema persiste, fate qualche ricerca per determinare se è stato già scoperto e risolto. Provate a cercare su Google il messaggio di errore o sfogliate gli archivi di nmap-dev su http://seclists.org/. Leggete anche il manuale completo. Se non ne ricavate nulla, scrivete un email con la segnalazione d'errore a <b>&lt;nmap-dev@insecure.org&gt;</b>. Siete pregati di includere ogni cosa appresa sul problema, assieme alla versione di Nmap che state eseguendo e su quale versione di sistema operativo gira. Segnalazioni di errore e domande sull'uso di %(nmap)s inviate a nmap-dev@insecure.org otterranno una risposta più facilmente di quelle inviate direttamente a Fyodor.\n" "Come il loro autore, %(nmap)s e %(app)s non sono perfetti. Ma potete aiutare a renderli migliori inviando segnalazioni d'errore o persino scrivendo patches. Se %(nmap)s non si comporta nel modo che vi aspettate, per prima cosa aggiornatelo all'ultima versione disponibile da <b>%(nmap_web)s</b>. Se il problema persiste, fate qualche ricerca per determinare se è stato già scoperto e risolto. Provate a cercare su Google il messaggio di errore o sfogliate gli archivi di nmap-dev su http://seclists.org/. Leggete anche il manuale completo. Se non ne ricavate nulla, scrivete un email con la segnalazione d'errore a <b>&lt;dev@nmap.org&gt;</b>. Siete pregati di includere ogni cosa appresa sul problema, assieme alla versione di Nmap che state eseguendo e su quale versione di sistema operativo gira. Segnalazioni di errore e domande sull'uso di %(nmap)s inviate a dev@nmap.org otterranno una risposta più facilmente di quelle inviate direttamente a Fyodor.\n"
"\n" "\n"
"Patches di codice per risolvere errori sono anche meglio delle segnalazioni. Semplici informazioni su come creare un file patch files con i vostri cambiamenti sono disponibili su http://nmap.org/data/HACKING. Le patches possono essere inviate direttamente a nmap-dev (raccomandato) o a Fyodor.\n" "Patches di codice per risolvere errori sono anche meglio delle segnalazioni. Semplici informazioni su come creare un file patch files con i vostri cambiamenti sono disponibili su http://nmap.org/data/HACKING. Le patches possono essere inviate direttamente a nmap-dev (raccomandato) o a Fyodor.\n"

BIN
zenmap/share/zenmap/locale/it/LC_MESSAGES/zenmap.mo
View File

Binary file not shown.

14
zenmap/share/zenmap/locale/ja.po
View File

@@ -1,7 +1,7 @@
msgid "" msgid ""
msgstr "" msgstr ""
"Project-Id-Version: \n" "Project-Id-Version: \n"
"Report-Msgid-Bugs-To: nmap-dev@insecure.org\n" "Report-Msgid-Bugs-To: dev@nmap.org\n"
"POT-Creation-Date: 2012-05-22 12:52-0700\n" "POT-Creation-Date: 2012-05-22 12:52-0700\n"
"PO-Revision-Date: \n" "PO-Revision-Date: \n"
"Last-Translator: Yuji Tounai <bogus@bogus.jp>\n" "Last-Translator: Yuji Tounai <bogus@bogus.jp>\n"
@@ -102,12 +102,12 @@ msgstr "クラッシュを報告"
#: zenmapGUI/CrashReport.py:130 #: zenmapGUI/CrashReport.py:130
#, python-format #, python-format
msgid "An unexpected error has crashed %(app_name)s. Please copy the stack trace below and send it to the <a href=\"mailto:nmap-dev@insecure.org\">nmap-dev@insecure.org</a> mailing list. (<a href=\"http://seclists.org/nmap-dev/\">More about the list.</a>) The developers will see your report and try to fix the problem." msgid "An unexpected error has crashed %(app_name)s. Please copy the stack trace below and send it to the <a href=\"mailto:dev@nmap.org\">dev@nmap.org</a> mailing list. (<a href=\"http://seclists.org/nmap-dev/\">More about the list.</a>) The developers will see your report and try to fix the problem."
msgstr "予期しないエラーが発生しました。%(app_name)s. スタックトレースをコピーして以下の宛先のメーリングリストに送信してください。<a href=\"mailto:nmap-dev@insecure.org\">nmap-dev@insecure.org</a> (<a href=\"http://seclists.org/nmap-dev/\">このメーリングリストについて</a>) 開発者たちはレポートを見て問題解決に取り組みます。" msgstr "予期しないエラーが発生しました。%(app_name)s. スタックトレースをコピーして以下の宛先のメーリングリストに送信してください。<a href=\"mailto:dev@nmap.org\">dev@nmap.org</a> (<a href=\"http://seclists.org/nmap-dev/\">このメーリングリストについて</a>) 開発者たちはレポートを見て問題解決に取り組みます。"
#: zenmapGUI/CrashReport.py:138 #: zenmapGUI/CrashReport.py:138
msgid "<b>Copy and email to <a href=\"mailto:nmap-dev@insecure.org\">nmap-dev@insecure.org</a>:</b>" msgid "<b>Copy and email to <a href=\"mailto:dev@nmap.org\">dev@nmap.org</a>:</b>"
msgstr "<b>コピーして、<a href=\"mailto:nmap-dev@insecure.org\">nmap-dev@insecure.org</a>:にメールを送ってください。</b>" msgstr "<b>コピーして、<a href=\"mailto:dev@nmap.org\">dev@nmap.org</a>:にメールを送ってください。</b>"
#: zenmapGUI/OptionBuilder.py:258 #: zenmapGUI/OptionBuilder.py:258
msgid "Choose file" msgid "Choose file"
@@ -790,13 +790,13 @@ msgstr "バグレポート方法"
msgid "" msgid ""
"<big><b>How to report a bug</b></big>\n" "<big><b>How to report a bug</b></big>\n"
"\n" "\n"
"Like their author, %(nmap)s and %(app)s aren't perfect. But you can help make it better by sending bug reports or even writing patches. If %(nmap)s doesn't behave the way you expect, first upgrade to the latest version available from <b>%(nmap_web)s</b>. If the problem persists, do some research to determine whether it has already been discovered and addressed. Try Googling the error message or browsing the nmap-dev archives at http://seclists.org/. Read the full manual page as well. If nothing comes of this, mail a bug report to <b>&lt;nmap-dev@insecure.org&gt;</b>. Please include everything you have learned about the problem, as well as what version of Nmap you are running and what operating system version it is running on. Problem reports and %(nmap)s usage questions sent to nmap-dev@insecure.org are far more likely to be answered than those sent to Fyodor directly.\n" "Like their author, %(nmap)s and %(app)s aren't perfect. But you can help make it better by sending bug reports or even writing patches. If %(nmap)s doesn't behave the way you expect, first upgrade to the latest version available from <b>%(nmap_web)s</b>. If the problem persists, do some research to determine whether it has already been discovered and addressed. Try Googling the error message or browsing the nmap-dev archives at http://seclists.org/. Read the full manual page as well. If nothing comes of this, mail a bug report to <b>&lt;dev@nmap.org&gt;</b>. Please include everything you have learned about the problem, as well as what version of Nmap you are running and what operating system version it is running on. Problem reports and %(nmap)s usage questions sent to dev@nmap.org are far more likely to be answered than those sent to Fyodor directly.\n"
"\n" "\n"
"Code patches to fix bugs are even better than bug reports. Basic instructions for creating patch files with your changes are available at http://nmap.org/data/HACKING. Patches may be sent to nmap-dev (recommended) or to Fyodor directly.\n" "Code patches to fix bugs are even better than bug reports. Basic instructions for creating patch files with your changes are available at http://nmap.org/data/HACKING. Patches may be sent to nmap-dev (recommended) or to Fyodor directly.\n"
msgstr "" msgstr ""
"<big><b>バグレポートの送り方</b></big>\n" "<big><b>バグレポートの送り方</b></big>\n"
"\n" "\n"
"Like their author, %(nmap)s and %(app)s aren't perfect. But you can help make it better by sending bug reports or even writing patches. If %(nmap)s doesn't behave the way you expect, first upgrade to the latest version available from <b>%(nmap_web)s</b>. If the problem persists, do some research to determine whether it has already been discovered and addressed. Try Googling the error message or browsing the nmap-dev archives at http://seclists.org/. Read the full manual page as well. If nothing comes of this, mail a bug report to <b>&lt;nmap-dev@insecure.org&gt;</b>. Please include everything you have learned about the problem, as well as what version of Nmap you are running and what operating system version it is running on. Problem reports and %(nmap)s usage questions sent to nmap-dev@insecure.org are far more likely to be answered than those sent to Fyodor directly.\n" "Like their author, %(nmap)s and %(app)s aren't perfect. But you can help make it better by sending bug reports or even writing patches. If %(nmap)s doesn't behave the way you expect, first upgrade to the latest version available from <b>%(nmap_web)s</b>. If the problem persists, do some research to determine whether it has already been discovered and addressed. Try Googling the error message or browsing the nmap-dev archives at http://seclists.org/. Read the full manual page as well. If nothing comes of this, mail a bug report to <b>&lt;dev@nmap.org&gt;</b>. Please include everything you have learned about the problem, as well as what version of Nmap you are running and what operating system version it is running on. Problem reports and %(nmap)s usage questions sent to dev@nmap.org are far more likely to be answered than those sent to Fyodor directly.\n"
"\n" "\n"
"Code patches to fix bugs are even better than bug reports. Basic instructions for creating patch files with your changes are available at http://nmap.org/data/HACKING. Patches may be sent to nmap-dev (recommended) or to Fyodor directly.\n" "Code patches to fix bugs are even better than bug reports. Basic instructions for creating patch files with your changes are available at http://nmap.org/data/HACKING. Patches may be sent to nmap-dev (recommended) or to Fyodor directly.\n"

BIN
zenmap/share/zenmap/locale/ja/LC_MESSAGES/zenmap.mo
View File

Binary file not shown.

6
zenmap/share/zenmap/locale/pt_BR.po
View File

@@ -6,7 +6,7 @@
msgid "" msgid ""
msgstr "" msgstr ""
"Project-Id-Version: Zenmap\n" "Project-Id-Version: Zenmap\n"
"Report-Msgid-Bugs-To: nmap-dev@insecure.org\n" "Report-Msgid-Bugs-To: dev@nmap.org\n"
"POT-Creation-Date: 2010-07-18 07:46-0600\n" "POT-Creation-Date: 2010-07-18 07:46-0600\n"
"PO-Revision-Date: 2006-04-12 11:53-0300\n" "PO-Revision-Date: 2006-04-12 11:53-0300\n"
"Last-Translator: Adriano Monteiro Marques <py.adriano@gmail.com>\n" "Last-Translator: Adriano Monteiro Marques <py.adriano@gmail.com>\n"
@@ -148,10 +148,10 @@ msgid ""
"research to determine whether it has already been discovered and addressed. " "research to determine whether it has already been discovered and addressed. "
"Try Googling the error message or browsing the nmap-dev archives at http://" "Try Googling the error message or browsing the nmap-dev archives at http://"
"seclists.org/. Read the full manual page as well. If nothing comes of this, " "seclists.org/. Read the full manual page as well. If nothing comes of this, "
"mail a bug report to <b>&lt;nmap-dev@insecure.org&gt;</b>. Please include " "mail a bug report to <b>&lt;dev@nmap.org&gt;</b>. Please include "
"everything you have learned about the problem, as well as what version of " "everything you have learned about the problem, as well as what version of "
"Nmap you are running and what operating system version it is running on. " "Nmap you are running and what operating system version it is running on. "
"Problem reports and %(nmap)s usage questions sent to nmap-dev@insecure.org " "Problem reports and %(nmap)s usage questions sent to dev@nmap.org "
"are far more likely to be answered than those sent to Fyodor directly.\n" "are far more likely to be answered than those sent to Fyodor directly.\n"
"\n" "\n"
"Code patches to fix bugs are even better than bug reports. Basic " "Code patches to fix bugs are even better than bug reports. Basic "

BIN
zenmap/share/zenmap/locale/pt_BR/LC_MESSAGES/zenmap.mo
View File

Binary file not shown.

6
zenmap/share/zenmap/locale/ru.po
View File

@@ -4,7 +4,7 @@
msgid "" msgid ""
msgstr "" msgstr ""
"Project-Id-Version: Zenmap\n" "Project-Id-Version: Zenmap\n"
"Report-Msgid-Bugs-To: nmap-dev@insecure.org\n" "Report-Msgid-Bugs-To: dev@nmap.org\n"
"POT-Creation-Date: 2010-07-18 07:46-0600\n" "POT-Creation-Date: 2010-07-18 07:46-0600\n"
"PO-Revision-Date: 2009-08-18 12:45+0400\n" "PO-Revision-Date: 2009-08-18 12:45+0400\n"
"Last-Translator: <spxnezzar@gmail.com>\n" "Last-Translator: <spxnezzar@gmail.com>\n"
@@ -159,10 +159,10 @@ msgid ""
"research to determine whether it has already been discovered and addressed. " "research to determine whether it has already been discovered and addressed. "
"Try Googling the error message or browsing the nmap-dev archives at http://" "Try Googling the error message or browsing the nmap-dev archives at http://"
"seclists.org/. Read the full manual page as well. If nothing comes of this, " "seclists.org/. Read the full manual page as well. If nothing comes of this, "
"mail a bug report to <b>&lt;nmap-dev@insecure.org&gt;</b>. Please include " "mail a bug report to <b>&lt;dev@nmap.org&gt;</b>. Please include "
"everything you have learned about the problem, as well as what version of " "everything you have learned about the problem, as well as what version of "
"Nmap you are running and what operating system version it is running on. " "Nmap you are running and what operating system version it is running on. "
"Problem reports and %(nmap)s usage questions sent to nmap-dev@insecure.org " "Problem reports and %(nmap)s usage questions sent to dev@nmap.org "
"are far more likely to be answered than those sent to Fyodor directly.\n" "are far more likely to be answered than those sent to Fyodor directly.\n"
"\n" "\n"
"Code patches to fix bugs are even better than bug reports. Basic " "Code patches to fix bugs are even better than bug reports. Basic "

BIN
zenmap/share/zenmap/locale/ru/LC_MESSAGES/zenmap.mo
View File

Binary file not shown.

10
zenmap/share/zenmap/locale/zenmap.pot
View File

@@ -5,7 +5,7 @@
msgid "" msgid ""
msgstr "" msgstr ""
"Project-Id-Version: Zenmap\n" "Project-Id-Version: Zenmap\n"
"Report-Msgid-Bugs-To: nmap-dev@insecure.org\n" "Report-Msgid-Bugs-To: dev@nmap.org\n"
"POT-Creation-Date: 2012-05-22 12:52-0700\n" "POT-Creation-Date: 2012-05-22 12:52-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"MIME-Version: 1.0\n" "MIME-Version: 1.0\n"
@@ -105,7 +105,7 @@ msgstr ""
#, python-format #, python-format
msgid "" msgid ""
"An unexpected error has crashed %(app_name)s. Please copy the stack trace " "An unexpected error has crashed %(app_name)s. Please copy the stack trace "
"below and send it to the <a href=\"mailto:nmap-dev@insecure.org\">nmap-" "below and send it to the <a href=\"mailto:dev@nmap.org\">nmap-"
"dev@insecure.org</a> mailing list. (<a href=\"http://seclists.org/nmap-dev/" "dev@insecure.org</a> mailing list. (<a href=\"http://seclists.org/nmap-dev/"
"\">More about the list.</a>) The developers will see your report and try to " "\">More about the list.</a>) The developers will see your report and try to "
"fix the problem." "fix the problem."
@@ -113,7 +113,7 @@ msgstr ""
#: zenmapGUI/CrashReport.py:138 #: zenmapGUI/CrashReport.py:138
msgid "" msgid ""
"<b>Copy and email to <a href=\"mailto:nmap-dev@insecure.org\">nmap-" "<b>Copy and email to <a href=\"mailto:dev@nmap.org\">nmap-"
"dev@insecure.org</a>:</b>" "dev@insecure.org</a>:</b>"
msgstr "" msgstr ""
@@ -767,10 +767,10 @@ msgid ""
"research to determine whether it has already been discovered and addressed. " "research to determine whether it has already been discovered and addressed. "
"Try Googling the error message or browsing the nmap-dev archives at http://" "Try Googling the error message or browsing the nmap-dev archives at http://"
"seclists.org/. Read the full manual page as well. If nothing comes of this, " "seclists.org/. Read the full manual page as well. If nothing comes of this, "
"mail a bug report to <b>&lt;nmap-dev@insecure.org&gt;</b>. Please include " "mail a bug report to <b>&lt;dev@nmap.org&gt;</b>. Please include "
"everything you have learned about the problem, as well as what version of " "everything you have learned about the problem, as well as what version of "
"Nmap you are running and what operating system version it is running on. " "Nmap you are running and what operating system version it is running on. "
"Problem reports and %(nmap)s usage questions sent to nmap-dev@insecure.org " "Problem reports and %(nmap)s usage questions sent to dev@nmap.org "
"are far more likely to be answered than those sent to Fyodor directly.\n" "are far more likely to be answered than those sent to Fyodor directly.\n"
"\n" "\n"
"Code patches to fix bugs are even better than bug reports. Basic " "Code patches to fix bugs are even better than bug reports. Basic "

4
zenmap/zenmapGUI/BugReport.py
View File

@@ -131,10 +131,10 @@ some research to determine whether it has already been discovered and \
addressed. Try Googling the error message or browsing the nmap-dev \ addressed. Try Googling the error message or browsing the nmap-dev \
archives at http://seclists.org/. Read the full manual page as well. If \ archives at http://seclists.org/. Read the full manual page as well. If \
nothing comes of this, mail a bug report to \ nothing comes of this, mail a bug report to \
<b>&lt;nmap-dev@insecure.org&gt;</b>. Please include everything you have \ <b>&lt;dev@nmap.org&gt;</b>. Please include everything you have \
learned about the problem, as well as what version of Nmap you are \ learned about the problem, as well as what version of Nmap you are \
running and what operating system version it is running on. Problem \ running and what operating system version it is running on. Problem \
reports and %(nmap)s usage questions sent to nmap-dev@insecure.org are \ reports and %(nmap)s usage questions sent to dev@nmap.org are \
far more likely to be answered than those sent to Fyodor directly. far more likely to be answered than those sent to Fyodor directly.
Code patches to fix bugs are even better than bug reports. Basic \ Code patches to fix bugs are even better than bug reports. Basic \

4
zenmap/zenmapGUI/CrashReport.py
View File

@@ -128,14 +128,14 @@ class CrashReport(HIGDialog):
self.bug_text = gtk.Label() self.bug_text = gtk.Label()
self.bug_text.set_markup(_("""\ self.bug_text.set_markup(_("""\
An unexpected error has crashed %(app_name)s. Please copy the stack trace below and \ An unexpected error has crashed %(app_name)s. Please copy the stack trace below and \
send it to the <a href="mailto:nmap-dev@insecure.org">nmap-dev@insecure.org</a> \ send it to the <a href="mailto:dev@nmap.org">dev@nmap.org</a> \
mailing list. (<a href="http://seclists.org/nmap-dev/">More about the list.</a>) \ mailing list. (<a href="http://seclists.org/nmap-dev/">More about the list.</a>) \
The developers will see your report and try to fix the problem.""") % \ The developers will see your report and try to fix the problem.""") % \
{ "app_name": escape(APP_DISPLAY_NAME) }) { "app_name": escape(APP_DISPLAY_NAME) })
self.email_frame = gtk.Frame() self.email_frame = gtk.Frame()
self.email_label = gtk.Label() self.email_label = gtk.Label()
self.email_label.set_markup(_("""\ self.email_label.set_markup(_("""\
<b>Copy and email to <a href="mailto:nmap-dev@insecure.org">nmap-dev@insecure.org</a>:</b>\ <b>Copy and email to <a href="mailto:dev@nmap.org">dev@nmap.org</a>:</b>\
""")) """))
self.btn_copy = gtk.Button(stock=gtk.STOCK_COPY) self.btn_copy = gtk.Button(stock=gtk.STOCK_COPY)
self.btn_ok = gtk.Button(stock=gtk.STOCK_OK) self.btn_ok = gtk.Button(stock=gtk.STOCK_OK)