diff --git a/CHANGELOG b/CHANGELOG index 33cc6ef60..4e7817d9a 100644 --- a/CHANGELOG +++ b/CHANGELOG @@ -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" 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 most elite Nmap users -- the ones who compile from source on UNIX -- get to see the 'l33t ASCII Art. diff --git a/HACKING b/HACKING index 40f0a41b2..6a99471e3 100644 --- a/HACKING +++ b/HACKING @@ -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, 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 Insecure.Org development mailing lists, it is assumed that you are 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 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 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. 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 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: diff --git a/docs/legal-notices.xml b/docs/legal-notices.xml index 563c26219..6254f02b1 100644 --- a/docs/legal-notices.xml +++ b/docs/legal-notices.xml @@ -83,7 +83,7 @@ run 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, and add new features. You are highly encouraged to send your changes -to nmap-dev@insecure.org for possible incorporation +to dev@nmap.org for possible incorporation into the main distribution. By sending these changes to Fyodor or one of the Insecure.Org development mailing lists, it is assumed that you are offering the Nmap Project (Insecure.Com LLC) the unlimited, diff --git a/docs/man-xlate/nmap-man-de.xml b/docs/man-xlate/nmap-man-de.xml index 020c2accc..ed485bc28 100644 --- a/docs/man-xlate/nmap-man-de.xml +++ b/docs/man-xlate/nmap-man-de.xml @@ -4329,11 +4329,11 @@ Sie in den nmap-dev-Archiven unter .nmap-dev Mailingliste Lesen Sie auch diese Manpage vollständig. Wenn Sie keine Lösung finden, schicken Sie einen Fehlerbericht per E-Mail an -nmap-dev@insecure.org. Beschreiben Sie darin bitte alles, +dev@nmap.org. Beschreiben Sie darin bitte alles, was Sie über das Problem wissen, inklusive der Nmap-Version und der Betriebssystemversion, unter der Sie Nmap einsetzen. Berichte von Problemen und Fragen zur Anwendung von Nmap werden sehr viel wahrscheinlicher -beantwortet, wenn sie an nmap-dev@insecure.org geschickt +beantwortet, wenn sie an dev@nmap.org geschickt 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 der Moderation und kommt schneller an. Eintragen können Sie sich unter diff --git a/docs/man-xlate/nmap-man-es.xml b/docs/man-xlate/nmap-man-es.xml index 5939cea8f..5e522d911 100644 --- a/docs/man-xlate/nmap-man-es.xml +++ b/docs/man-xlate/nmap-man-es.xml @@ -3576,12 +3576,12 @@ medida que se incrementa el nivel de depuraci archivos de Nmap-dev en . Tambin deberas leer este manual completo. Si esto no te ayuda, enva un informe de error en ingls - a nmap-dev@insecure.org. Por favor, incluya todo + a dev@nmap.org. Por favor, incluya todo lo que haya visto del problema, as como qu versin de Nmap est utilizando y sobre qu versin del sistema operativo est trabajando. Hay muchas ms probabilidades de que un informe de fallo o una pregunta sobre el uso de Nmap se contesten si se - envan a nmap-dev@insecure.org que si se envan directamente a + envan a dev@nmap.org que si se envan directamente a Fyodor. Es mejor enviar parches para arreglar el cdigo que un diff --git a/docs/man-xlate/nmap-man-fr.xml b/docs/man-xlate/nmap-man-fr.xml index 6cba527ec..4f8e155cf 100644 --- a/docs/man-xlate/nmap-man-fr.xml +++ b/docs/man-xlate/nmap-man-fr.xml @@ -2279,11 +2279,11 @@ le temps suppl signal. Essayez pour cela de mettre l'erreur en argument sur Google ou parcourez les archives de Nmap-dev sur . Lisez ce manuel en entier quoiqu'il en soit. Si rien ne semble fonctionner, envoyez un rapport de bogue - nmap-dev@insecure.org. Veillez inclure tout ce que vous avez + dev@nmap.org. Veillez inclure tout ce que vous avez appris au sujet de ce bogue ainsi que la version de Nmap concerne et le systme d'exploitation que vous utilisez. Les rapports de problmes et les questions sur l'utilisation de Nmap envoys - nmap-dev@insecure.org ont plus de chance de trouver une rponse que ceux + dev@nmap.org ont plus de chance de trouver une rponse que ceux envoys Fyodor directement. Les codes de programmes de correction destins rgler des bogues sont encore meilleurs que les rapports de bogues. Les instructions de base pour crer des fichiers de programmes de correction avec vos modifications diff --git a/docs/man-xlate/nmap-man-hr.xml b/docs/man-xlate/nmap-man-hr.xml index b078a11aa..04619de52 100644 --- a/docs/man-xlate/nmap-man-hr.xml +++ b/docs/man-xlate/nmap-man-hr.xml @@ -2420,9 +2420,9 @@ samoobjašnjavajuće, ali poruke postaju sve čudnije što je nivo debugiranja v . 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 . Također pročitajte i kompletan manual. Ukoliko ništa od toga ne - pomogne, pošaljite izvještaj o grešci na nmap-dev@insecure.org. Molim Vas napišite sve što ste do + pomogne, pošaljite izvještaj o grešci na dev@nmap.org. 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 - 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. Patchevi za otklanjanje bugova su još i bolji od samih prijava. Osnovne upute za kreiranje patch datoteka s diff --git a/docs/man-xlate/nmap-man-hu.xml b/docs/man-xlate/nmap-man-hu.xml index c0c5df840..955aa682c 100644 --- a/docs/man-xlate/nmap-man-hu.xml +++ b/docs/man-xlate/nmap-man-hu.xml @@ -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 Google-ban a hibaüzenetre vagy böngéssze át az Nmap fejlesztői listát a címen. Olvassa végig ezt a leírást - is. Ha nem talál semmit, küldjön egy hibajelentést az nmap-dev@insecure.org + is. Ha nem talál semmit, küldjön egy hibajelentést az dev@nmap.org 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 - 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 azokat közvetlenül a program készítőjének (Fyodor) küldené. diff --git a/docs/man-xlate/nmap-man-id.xml b/docs/man-xlate/nmap-man-id.xml index 42c882ac1..8f8573643 100755 --- a/docs/man-xlate/nmap-man-id.xml +++ b/docs/man-xlate/nmap-man-id.xml @@ -3967,10 +3967,10 @@ banyaknya permintaan. Berikan untuk hanya melihat port membrowsing arsip nmap-dev di .nmap-dev mailing list Bacalah juga halaman manual ini dengan baik. Jika masih belum selesai juga, kirimkan laporan bug ke - nmap-dev@insecure.org. Mohon sertakan semua yang + dev@nmap.org. Mohon sertakan semua yang anda telah pelajari mengenai masalah, dan juga versi Nmap dan sistem operasi yang anda gunakan. Laporan kesalahan dan pertanyaan penggunaan Nmap yang dikirim ke - nmap-dev@insecure.org akan lebih mungkin dijawab daripada yang dikirimkan + dev@nmap.org akan lebih mungkin dijawab daripada yang dikirimkan secara langsung ke Fyodor. Jika anda berlangganan ke list nmap-dev sebelum posting, pesan anda akan melewati moderasi dan akan lewat dengan lebih cepat. Berlangganan di . diff --git a/docs/man-xlate/nmap-man-it.xml b/docs/man-xlate/nmap-man-it.xml index 5b54b4f57..63ff6bef5 100644 --- a/docs/man-xlate/nmap-man-it.xml +++ b/docs/man-xlate/nmap-man-it.xml @@ -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 inoltre tutta questa pagina di manuale. Se nulla di questo riguarda il tuo caso, manda una segnalazione di bug a - nmap-dev@insecure.org. Accertati di includere + dev@nmap.org. Accertati di includere ogni cosa che sei riuscito a sapere sul problema, la versione di Nmap che stai usando e su quale sistema operativo la stai 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 direttamente. diff --git a/docs/man-xlate/nmap-man-jp.xml b/docs/man-xlate/nmap-man-jp.xml index c5c0b7b4f..cdc696a71 100644 --- a/docs/man-xlate/nmap-man-jp.xml +++ b/docs/man-xlate/nmap-man-jp.xml @@ -1349,7 +1349,7 @@ rttvar: 14987 to: 100000。こうした行の内容が理解で バグ - Nmapも作者と同様に完全ではない。それでもNmapのほうは、ユーザによるバグの報告やパッチの作成のおかげで、よりよいものにしてゆくことができる。Nmapを使っていて、思い通りに動かない場合は、まずから入手できる最新のバージョンにアップグレードしてみる。問題が続くようなら、すでに発見・対処が行われた問題かどうかを調査して確かめる。エラーメッセージをGoogle検索したり、でNmap-devアーカイブを閲覧したりしてみる。このmanページも全体に目を通した方がよい。それでもどうにもならない場合は、バグレポートをnmap-dev@insecure.org宛てにメールで送ること。メールには、使用しているNmapのバージョンと、Nmapを実行しているOSの名前とバージョンなどの情報だけでなく、問題に関して分かったことは何でも書いていただきたい。問題の報告やNmapの使い方についての質問などは、nmap-dev@insecure.org宛てに送るほうが、筆者宛てに直接送るよりも返事がある可能性ははるかに高い。 + Nmapも作者と同様に完全ではない。それでもNmapのほうは、ユーザによるバグの報告やパッチの作成のおかげで、よりよいものにしてゆくことができる。Nmapを使っていて、思い通りに動かない場合は、まずから入手できる最新のバージョンにアップグレードしてみる。問題が続くようなら、すでに発見・対処が行われた問題かどうかを調査して確かめる。エラーメッセージをGoogle検索したり、でNmap-devアーカイブを閲覧したりしてみる。このmanページも全体に目を通した方がよい。それでもどうにもならない場合は、バグレポートをdev@nmap.org宛てにメールで送ること。メールには、使用しているNmapのバージョンと、Nmapを実行しているOSの名前とバージョンなどの情報だけでなく、問題に関して分かったことは何でも書いていただきたい。問題の報告やNmapの使い方についての質問などは、dev@nmap.org宛てに送るほうが、筆者宛てに直接送るよりも返事がある可能性ははるかに高い。 またバグレポートより、バグを修正するためのコードパッチのほうが歓迎される。ユーザ自身のコード変更によるパッチファイルの作成方法についての基本的な注意事項は で参照できる。パッチは、nmap-dev宛てに送る(推奨)か、筆者Fyodorまで直接送っていただきたい。 diff --git a/docs/man-xlate/nmap-man-pl.xml b/docs/man-xlate/nmap-man-pl.xml index 2b6552381..5ed8010da 100644 --- a/docs/man-xlate/nmap-man-pl.xml +++ b/docs/man-xlate/nmap-man-pl.xml @@ -3066,11 +3066,11 @@ podobnie jak i UDP. błędu lub poprzeglądaj archiwa listy dyskusyjnej Nmap-dev pod adresem . Przeczytaj również cała dokumentację. Jeśli nic nie pomoże, wyślij raport opisujący błąd po angielsku na adres - nmap-dev@insecure.org. Proszę dołącz wszystko co udało Ci + dev@nmap.org. Proszę dołącz wszystko co udało Ci się ustalić na temat tego problemu, jak również informację o używanej wersji Nmapa i systemie operacyjnym na którym jest uruchamiany. Opisy problemów i pytania dotyczące używania Nmapa wysłane na adres - nmap-dev@insecure.org z większym prawdopodobieństwem doczekają sie + dev@nmap.org z większym prawdopodobieństwem doczekają sie szybkiej odpowiedzi, niż wysłane bezpośrednio do Fyodora. Poprawki błędnego kodu są milej widziane, niż opisy błedów. diff --git a/docs/man-xlate/nmap-man-pt_BR.xml b/docs/man-xlate/nmap-man-pt_BR.xml index 1812269db..d8436b781 100644 --- a/docs/man-xlate/nmap-man-pt_BR.xml +++ b/docs/man-xlate/nmap-man-pt_BR.xml @@ -3794,7 +3794,7 @@ EXAMPLES: Tente procurar no Google pela mensagem de erro ou navegar nos arquivos da Nmap-dev em . Se não encontrar nada, envie uma mensagem com um relatório do erro para - nmap-dev@insecure.org. Por favor, inclua tudo o que + dev@nmap.org. Por favor, inclua tudo o que 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á rodando-o. diff --git a/docs/man-xlate/nmap-man-pt_PT.xml b/docs/man-xlate/nmap-man-pt_PT.xml index adebf74ef..66ec71233 100644 --- a/docs/man-xlate/nmap-man-pt_PT.xml +++ b/docs/man-xlate/nmap-man-pt_PT.xml @@ -3096,7 +3096,7 @@ EXEMPLOS: encaminhado. Tente procurar no Google pela mensagem de erro ou navegar nos arquivos da Nmap-dev em . Se no encontrar nada envie uma mensagem com um relatrio do erro para - nmap-dev@insecure.org. Por favor inclua tudo o que + dev@nmap.org. Por favor inclua tudo o que souber sobre o problema bem como a verso do Nmap que est executando e em qual verso e sistema operativo que est a usar. diff --git a/docs/man-xlate/nmap-man-ro.xml b/docs/man-xlate/nmap-man-ro.xml index 9692455fc..5667a7411 100644 --- a/docs/man-xlate/nmap-man-ro.xml +++ b/docs/man-xlate/nmap-man-ro.xml @@ -2957,10 +2957,10 @@ eroare sau navigand prin arhivele Nmap-dev la . Cititi acest manual in intregime de asemenea. Daca nimic nu se rezolva, trimiteti un mail la - nmap-dev@insecure.org. Va rog sa includeti tot ce ati + dev@nmap.org. Va rog sa includeti tot ce ati aflat despre problema, precum si versiunea de Nmap pe care o folositi si 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. Patchurile de rezolvare a problemelor sunt si mai bune decat rapoartele despre problema in sine. Instructiuni de baza pentru crearea diff --git a/docs/man-xlate/nmap-man-ru.xml b/docs/man-xlate/nmap-man-ru.xml index d696c3f97..a590e0170 100644 --- a/docs/man-xlate/nmap-man-ru.xml +++ b/docs/man-xlate/nmap-man-ru.xml @@ -3477,9 +3477,9 @@ rttvar: 14987 to: 100000. Если вы не понимаете Попробуйте поискать сообщения об ошибках на нашей странице поиска или в Google. Также попробуйте просмотреть nmap-dev архивы на .nmap-dev mailing list Также прочитайте полностью страницу руководства. Если ничего не помогло, отправьте сообщение об ошибке на - nmap-dev@insecure.org. Пожалуйста, включите всю известную вам информацию об ошибке, какую версию + dev@nmap.org. Пожалуйста, включите всю известную вам информацию об ошибке, какую версию Nmap вы используете, и на какой операционной системы вы запускаете Nmap. Сообщения о проблемах и вопросы по - использованию Nmap отправленные на nmap-dev@insecure.org имеют больше шансов на ответ, чем если бы + использованию Nmap отправленные на dev@nmap.org имеют больше шансов на ответ, чем если бы вы послали их непосредственно Fyodor'у. Если вы подпишитесь на рассылку nmap-dev перед отправкой сообщения, то ваше сообщение будет обработано быстрее. Подпишитесь на рассылку на . diff --git a/docs/man-xlate/nmap-man-sk.xml b/docs/man-xlate/nmap-man-sk.xml index f43732307..31012d510 100644 --- a/docs/man-xlate/nmap-man-sk.xml +++ b/docs/man-xlate/nmap-man-sk.xml @@ -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 . Precitajte si aj tento plny manual. Ak nenajdete nic podobne, poslite mail o bugu na adresu - nmap-dev@insecure.org. Zahrnte vsetko, co ste sa dozvedeli + dev@nmap.org. Zahrnte vsetko, co ste sa dozvedeli o probleme spolu s verziou Nmapu a operacnym systemom. Spravy o problemoch a otazky na pouzivanie Nmapu budu ovela pravdepodobnejsie zodpovedane, ak budu odoslane - na nmap-dev@insecure.org namiesto odosielania priamo Fyodorovi. + na dev@nmap.org namiesto odosielania priamo Fyodorovi. 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 diff --git a/docs/man-xlate/nmap-man-zh.xml b/docs/man-xlate/nmap-man-zh.xml index efd2a2eb0..7c4d1665a 100644 --- a/docs/man-xlate/nmap-man-zh.xml +++ b/docs/man-xlate/nmap-man-zh.xml @@ -2324,9 +2324,9 @@ rttvar: 14987 to: 100000。如果对某行输出不明白， 升级最新版本。如果总问题仍然存在，需要进行调查以确定问题是否 已经被解决。在尝试搜索出错消息或 浏览Nmap-dev档案，以及仔细阅读使用手册。如果问题还是不能解决，发送 - Bug报告至nmap-dev@insecure.org。在报告中包含所有 + Bug报告至dev@nmap.org。在报告中包含所有 有关问题的信息，以及所使用的Nmap版本、操作系统版本。问题报告以及 - Nmap的使用问题发送给nmap-dev@insecure.org比直接发送给Gyodor能更好回答。 + Nmap的使用问题发送给dev@nmap.org比直接发送给Gyodor能更好回答。 解决Bug的代码补丁比Bug报告更受欢迎，在 可获得建立补丁文件的基本指令。补丁可发送给nmap-dev(建议) diff --git a/docs/refguide.xml b/docs/refguide.xml index f526a9ae3..f7f6e1775 100644 --- a/docs/refguide.xml +++ b/docs/refguide.xml @@ -4477,11 +4477,11 @@ Service scan Timing: About 33.33% done; ETC: 20:57 (0:00:12 remaining) url="http://seclists.org/" />.nmap-dev mailing list Read this full manual page as well. If nothing comes of this, mail a bug report to - nmap-dev@insecure.org. Please include everything + dev@nmap.org. 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 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. If you subscribe to the nmap-dev list before posting, your message will bypass moderation and get through more quickly. Subscribe at . diff --git a/docs/zenmap.xml b/docs/zenmap.xml index ec1738f1e..c1bce6e5c 100644 --- a/docs/zenmap.xml +++ b/docs/zenmap.xml @@ -135,10 +135,10 @@ the nmap-dev archives at . Read this full manual page as well. If nothing comes of this, mail a bug report to - nmap-dev@insecure.org. Please include everything you have + dev@nmap.org. Please include everything you have 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 - 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. Code patches to fix bugs are even better than bug reports. Basic diff --git a/ncat/docs/ncat.xml b/ncat/docs/ncat.xml index 7ecb0d659..948cf33db 100644 --- a/ncat/docs/ncat.xml +++ b/ncat/docs/ncat.xml @@ -887,11 +887,11 @@ nmap-dev mailing list Read this full manual page as well. If nothing comes of this, mail a bug report to - nmap-dev@insecure.org. Please include everything + dev@nmap.org. Please include everything you have learned about the problem, as well as what version of Ncat you are running and what operating system version it is 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. 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 Source code also allows you to port Nmap (which includes Ncat) to new platforms, fix bugs, and add new features. You are highly encouraged to send your changes to -nmap-dev@insecure.org for possible incorporation into +dev@nmap.org for possible incorporation into the main distribution. By sending these changes to Fyodor or one of the Insecure.Org development mailing lists, it is assumed that you are offering the Nmap Project (Insecure.Com LLC) the unlimited, diff --git a/ncat/ncat_main.c b/ncat/ncat_main.c index c1f638239..6b202536a 100644 --- a/ncat/ncat_main.c +++ b/ncat/ncat_main.c @@ -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."); if (o.broker) 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\ connection brokering should work."); } diff --git a/ndiff/docs/ndiff.xml b/ndiff/docs/ndiff.xml index 8cdb1090d..9e8844666 100644 --- a/ndiff/docs/ndiff.xml +++ b/ndiff/docs/ndiff.xml @@ -373,7 +373,7 @@ ln -sf scan-$date.xml scan-prev.xml Bugs Report bugs to the nmap-dev mailing list at - nmap-dev@insecure.org. + dev@nmap.org. diff --git a/nping/docs/nping-man.xml b/nping/docs/nping-man.xml index 14ec8d45b..8d0108ce6 100644 --- a/nping/docs/nping-man.xml +++ b/nping/docs/nping-man.xml @@ -3532,11 +3532,11 @@ NSOCK (1.0000s) Callback: TIMER SUCCESS for EID 12; tcpconnect_event_handlernmap-dev mailing list Read this full manual page as well. If nothing comes out of this, mail a bug report to - nmap-dev@insecure.org. Please include everything + dev@nmap.org. Please include everything you have learned about the problem, as well as what version of Nping you are running and what operating system version it is running on. Problem reports and Nping 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. If you subscribe to the nmap-dev list before posting, your message will bypass moderation and get through more quickly. Subscribe at diff --git a/nselib/data/http-fingerprints.lua b/nselib/data/http-fingerprints.lua index 6be2d5856..5632d13a6 100644 --- a/nselib/data/http-fingerprints.lua +++ b/nselib/data/http-fingerprints.lua @@ -64,7 +64,7 @@ local table = require "table" -- 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: -- Added 120 new signatures taken from exploit-db.com archives from July 2009 to July 2011 [Paulino Calderon] diff --git a/scripts/http-sql-injection.nse b/scripts/http-sql-injection.nse index b7fda71f8..05f0ef299 100644 --- a/scripts/http-sql-injection.nse +++ b/scripts/http-sql-injection.nse @@ -43,7 +43,7 @@ categories = {"intrusive", "vuln"} -- 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/. -- 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 -- PORT STATE SERVICE diff --git a/scripts/smb-psexec.nse b/scripts/smb-psexec.nse index c0620488d..36a6273ec 100644 --- a/scripts/smb-psexec.nse +++ b/scripts/smb-psexec.nse @@ -293,7 +293,7 @@ files are deleted. 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 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 mod = config.enabled_modules[module_num + 1] 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--") - 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 -- Save this result diff --git a/zenmap/share/zenmap/locale/Makefile b/zenmap/share/zenmap/locale/Makefile index bb6e1be5b..43b5a715c 100644 --- a/zenmap/share/zenmap/locale/Makefile +++ b/zenmap/share/zenmap/locale/Makefile @@ -6,7 +6,7 @@ SOURCEDIRS = zenmapCore zenmapGUI radialnet PROFILE_EDITOR_XML = share/zenmap/misc/profile_editor.xml XGETTEXT = xgettext -MSGID_BUGS_ADDRESS = nmap-dev@insecure.org +MSGID_BUGS_ADDRESS = dev@nmap.org ZENMAP_POT = zenmap.pot TMP_POT = tmp.pot diff --git a/zenmap/share/zenmap/locale/de.po b/zenmap/share/zenmap/locale/de.po index 1f8f85c23..895d98b0e 100644 --- a/zenmap/share/zenmap/locale/de.po +++ b/zenmap/share/zenmap/locale/de.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "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" "PO-Revision-Date: 2009-08-31 21:13+GMT\n" "Last-Translator: Chris Leick \n" @@ -163,10 +163,10 @@ msgid "" "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 <nmap-dev@insecure.org>. Please include " +"mail a bug report to <dev@nmap.org>. 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 " +"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" "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 " "durchstöbern Sie die Nmap-dev-Archive unter http://seclists.org/. Lesen Sie " "außerdem die vollständige Handbuchseite. Wenn dabei nichts herauskommt, " -"mailen Sie einen Fehlerbericht an <nmap-dev@insecure.org>. " +"mailen Sie einen Fehlerbericht an <dev@nmap.org>. " "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 " "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" "\n" "Code-Patches zum Beheben von Fehlern sind sogar besser als Fehlerberichte. " diff --git a/zenmap/share/zenmap/locale/de/LC_MESSAGES/zenmap.mo b/zenmap/share/zenmap/locale/de/LC_MESSAGES/zenmap.mo index 982d5672d..d9dd89a6c 100644 Binary files a/zenmap/share/zenmap/locale/de/LC_MESSAGES/zenmap.mo and b/zenmap/share/zenmap/locale/de/LC_MESSAGES/zenmap.mo differ diff --git a/zenmap/share/zenmap/locale/fr.po b/zenmap/share/zenmap/locale/fr.po index a4c9c7b4e..90a0c34f3 100644 --- a/zenmap/share/zenmap/locale/fr.po +++ b/zenmap/share/zenmap/locale/fr.po @@ -4,7 +4,7 @@ msgid "" msgstr "" "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" "PO-Revision-Date: 2011-01-20 23:01+0100\n" "Last-Translator: \n" @@ -168,10 +168,10 @@ msgid "" "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 <nmap-dev@insecure.org>. Please include " +"mail a bug report to <dev@nmap.org>. 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 " +"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" "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 " "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, " -"envoyez un rapport de bug à  <nmap-dev@insecure.org>. Veuillez " +"envoyez un rapport de bug à  <dev@nmap.org>. Veuillez " "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 " "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" "\n" "Les code correctifs pour réparer un bug sont encore meilleurs que les " diff --git a/zenmap/share/zenmap/locale/fr/LC_MESSAGES/zenmap.mo b/zenmap/share/zenmap/locale/fr/LC_MESSAGES/zenmap.mo index 56a1756eb..69731f581 100644 Binary files a/zenmap/share/zenmap/locale/fr/LC_MESSAGES/zenmap.mo and b/zenmap/share/zenmap/locale/fr/LC_MESSAGES/zenmap.mo differ diff --git a/zenmap/share/zenmap/locale/hr.po b/zenmap/share/zenmap/locale/hr.po index e72f6c9c2..cc95023a1 100644 --- a/zenmap/share/zenmap/locale/hr.po +++ b/zenmap/share/zenmap/locale/hr.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "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" "PO-Revision-Date: 2009-02-08 23:49+0100\n" "Last-Translator: Vlatko Kosturjak \n" @@ -159,10 +159,10 @@ msgid "" "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 <nmap-dev@insecure.org>. Please include " +"mail a bug report to <dev@nmap.org>. 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 " +"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" "Code patches to fix bugs are even better than bug reports. Basic " @@ -183,7 +183,7 @@ msgstr "" "dev@insecure.org>. Molimo uključite sve što ste saznali o problemu, " "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 " -"nmap-dev@insecure.org će vjerojatno biti prije odgovorena nego poslana " +"dev@nmap.org će vjerojatno biti prije odgovorena nego poslana " "Fyodoru direktno.\n" "\n" "Popravci za kod koji ispravljaju greške su mnogo bolji nego izvješće o " diff --git a/zenmap/share/zenmap/locale/hr/LC_MESSAGES/zenmap.mo b/zenmap/share/zenmap/locale/hr/LC_MESSAGES/zenmap.mo index 548ce1c7c..9d5a367f7 100644 Binary files a/zenmap/share/zenmap/locale/hr/LC_MESSAGES/zenmap.mo and b/zenmap/share/zenmap/locale/hr/LC_MESSAGES/zenmap.mo differ diff --git a/zenmap/share/zenmap/locale/it.po b/zenmap/share/zenmap/locale/it.po index 1db4da48d..95fc58a81 100644 --- a/zenmap/share/zenmap/locale/it.po +++ b/zenmap/share/zenmap/locale/it.po @@ -4,7 +4,7 @@ msgid "" msgstr "" "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" "PO-Revision-Date: 2012-05-30 05:00+0100\n" "MIME-Version: 1.0\n" @@ -101,12 +101,12 @@ msgstr "Rapporto di crash" #: zenmapGUI/CrashReport.py:130 #, python-format -msgid "An unexpected error has crashed %(app_name)s. Please copy the stack trace below and send it to the nmap-dev@insecure.org mailing list. (More about the list.) 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 nmap-dev@insecure.org mailing list. (Per saperne di più sulla lista.) Gli sviluppatori vedranno il tuo rapporto e proveranno a risolvere il problema." +msgid "An unexpected error has crashed %(app_name)s. Please copy the stack trace below and send it to the dev@nmap.org mailing list. (More about the list.) 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 dev@nmap.org mailing list. (Per saperne di più sulla lista.) Gli sviluppatori vedranno il tuo rapporto e proveranno a risolvere il problema." #: zenmapGUI/CrashReport.py:138 -msgid "Copy and email to nmap-dev@insecure.org:" -msgstr "Copia e spedisci via email a nmap-dev@insecure.org:" +msgid "Copy and email to dev@nmap.org:" +msgstr "Copia e spedisci via email a dev@nmap.org:" #: zenmapGUI/OptionBuilder.py:258 msgid "Choose file" @@ -789,13 +789,13 @@ msgstr "Come segnalare un errore" msgid "" "How to report a bug\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 %(nmap_web)s. 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 <nmap-dev@insecure.org>. 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 %(nmap_web)s. 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 <dev@nmap.org>. 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" "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 "" "Come segnalare un errore\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 %(nmap_web)s. 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 <nmap-dev@insecure.org>. 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 %(nmap_web)s. 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 <dev@nmap.org>. 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" "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" diff --git a/zenmap/share/zenmap/locale/it/LC_MESSAGES/zenmap.mo b/zenmap/share/zenmap/locale/it/LC_MESSAGES/zenmap.mo index 5ef08b95e..1fa6763a2 100644 Binary files a/zenmap/share/zenmap/locale/it/LC_MESSAGES/zenmap.mo and b/zenmap/share/zenmap/locale/it/LC_MESSAGES/zenmap.mo differ diff --git a/zenmap/share/zenmap/locale/ja.po b/zenmap/share/zenmap/locale/ja.po index 08859d78f..9588c2140 100644 --- a/zenmap/share/zenmap/locale/ja.po +++ b/zenmap/share/zenmap/locale/ja.po @@ -1,7 +1,7 @@ msgid "" msgstr "" "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" "PO-Revision-Date: \n" "Last-Translator: Yuji Tounai \n" @@ -102,12 +102,12 @@ msgstr "クラッシュを報告" #: zenmapGUI/CrashReport.py:130 #, python-format -msgid "An unexpected error has crashed %(app_name)s. Please copy the stack trace below and send it to the nmap-dev@insecure.org mailing list. (More about the list.) The developers will see your report and try to fix the problem." -msgstr "予期しないエラーが発生しました。%(app_name)s. スタックトレースをコピーして以下の宛先のメーリングリストに送信してください。nmap-dev@insecure.org (このメーリングリストについて) 開発者たちはレポートを見て問題解決に取り組みます。" +msgid "An unexpected error has crashed %(app_name)s. Please copy the stack trace below and send it to the dev@nmap.org mailing list. (More about the list.) The developers will see your report and try to fix the problem." +msgstr "予期しないエラーが発生しました。%(app_name)s. スタックトレースをコピーして以下の宛先のメーリングリストに送信してください。dev@nmap.org (このメーリングリストについて) 開発者たちはレポートを見て問題解決に取り組みます。" #: zenmapGUI/CrashReport.py:138 -msgid "Copy and email to nmap-dev@insecure.org:" -msgstr "コピーして、nmap-dev@insecure.org:にメールを送ってください。" +msgid "Copy and email to dev@nmap.org:" +msgstr "コピーして、dev@nmap.org:にメールを送ってください。" #: zenmapGUI/OptionBuilder.py:258 msgid "Choose file" @@ -790,13 +790,13 @@ msgstr "バグレポート方法" msgid "" "How to report a bug\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 %(nmap_web)s. 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 <nmap-dev@insecure.org>. 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 %(nmap_web)s. 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 <dev@nmap.org>. 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" "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 "" "バグレポートの送り方\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 %(nmap_web)s. 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 <nmap-dev@insecure.org>. 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 %(nmap_web)s. 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 <dev@nmap.org>. 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" "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" diff --git a/zenmap/share/zenmap/locale/ja/LC_MESSAGES/zenmap.mo b/zenmap/share/zenmap/locale/ja/LC_MESSAGES/zenmap.mo index 2b91e0221..097c8ad99 100644 Binary files a/zenmap/share/zenmap/locale/ja/LC_MESSAGES/zenmap.mo and b/zenmap/share/zenmap/locale/ja/LC_MESSAGES/zenmap.mo differ diff --git a/zenmap/share/zenmap/locale/pt_BR.po b/zenmap/share/zenmap/locale/pt_BR.po index 019dd5fcf..afb530be0 100644 --- a/zenmap/share/zenmap/locale/pt_BR.po +++ b/zenmap/share/zenmap/locale/pt_BR.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "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" "PO-Revision-Date: 2006-04-12 11:53-0300\n" "Last-Translator: Adriano Monteiro Marques \n" @@ -148,10 +148,10 @@ msgid "" "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 <nmap-dev@insecure.org>. Please include " +"mail a bug report to <dev@nmap.org>. 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 " +"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" "Code patches to fix bugs are even better than bug reports. Basic " diff --git a/zenmap/share/zenmap/locale/pt_BR/LC_MESSAGES/zenmap.mo b/zenmap/share/zenmap/locale/pt_BR/LC_MESSAGES/zenmap.mo index 5d26620e5..dc78aa531 100644 Binary files a/zenmap/share/zenmap/locale/pt_BR/LC_MESSAGES/zenmap.mo and b/zenmap/share/zenmap/locale/pt_BR/LC_MESSAGES/zenmap.mo differ diff --git a/zenmap/share/zenmap/locale/ru.po b/zenmap/share/zenmap/locale/ru.po index 285a53399..d40aa126b 100644 --- a/zenmap/share/zenmap/locale/ru.po +++ b/zenmap/share/zenmap/locale/ru.po @@ -4,7 +4,7 @@ msgid "" msgstr "" "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" "PO-Revision-Date: 2009-08-18 12:45+0400\n" "Last-Translator: \n" @@ -159,10 +159,10 @@ msgid "" "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 <nmap-dev@insecure.org>. Please include " +"mail a bug report to <dev@nmap.org>. 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 " +"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" "Code patches to fix bugs are even better than bug reports. Basic " diff --git a/zenmap/share/zenmap/locale/ru/LC_MESSAGES/zenmap.mo b/zenmap/share/zenmap/locale/ru/LC_MESSAGES/zenmap.mo index d3b0ff95d..fb7dc5365 100644 Binary files a/zenmap/share/zenmap/locale/ru/LC_MESSAGES/zenmap.mo and b/zenmap/share/zenmap/locale/ru/LC_MESSAGES/zenmap.mo differ diff --git a/zenmap/share/zenmap/locale/zenmap.pot b/zenmap/share/zenmap/locale/zenmap.pot index 33ef58584..ddd52fca4 100644 --- a/zenmap/share/zenmap/locale/zenmap.pot +++ b/zenmap/share/zenmap/locale/zenmap.pot @@ -5,7 +5,7 @@ msgid "" msgstr "" "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" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "MIME-Version: 1.0\n" @@ -105,7 +105,7 @@ msgstr "" #, python-format msgid "" "An unexpected error has crashed %(app_name)s. Please copy the stack trace " -"below and send it to the nmap-" +"below and send it to the nmap-" "dev@insecure.org mailing list. (More about the list.) The developers will see your report and try to " "fix the problem." @@ -113,7 +113,7 @@ msgstr "" #: zenmapGUI/CrashReport.py:138 msgid "" -"Copy and email to nmap-" +"Copy and email to nmap-" "dev@insecure.org:" msgstr "" @@ -767,10 +767,10 @@ msgid "" "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 <nmap-dev@insecure.org>. Please include " +"mail a bug report to <dev@nmap.org>. 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 " +"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" "Code patches to fix bugs are even better than bug reports. Basic " diff --git a/zenmap/zenmapGUI/BugReport.py b/zenmap/zenmapGUI/BugReport.py index fae9a452a..b231f8f42 100644 --- a/zenmap/zenmapGUI/BugReport.py +++ b/zenmap/zenmapGUI/BugReport.py @@ -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 \ archives at http://seclists.org/. Read the full manual page as well. If \ nothing comes of this, mail a bug report to \ -<nmap-dev@insecure.org>. Please include everything you have \ +<dev@nmap.org>. 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 \ +reports and %(nmap)s usage questions sent to dev@nmap.org are \ far more likely to be answered than those sent to Fyodor directly. Code patches to fix bugs are even better than bug reports. Basic \ diff --git a/zenmap/zenmapGUI/CrashReport.py b/zenmap/zenmapGUI/CrashReport.py index d2d25ce3f..66a15d5f8 100644 --- a/zenmap/zenmapGUI/CrashReport.py +++ b/zenmap/zenmapGUI/CrashReport.py @@ -128,14 +128,14 @@ class CrashReport(HIGDialog): self.bug_text = gtk.Label() self.bug_text.set_markup(_("""\ An unexpected error has crashed %(app_name)s. Please copy the stack trace below and \ -send it to the nmap-dev@insecure.org \ +send it to the dev@nmap.org \ mailing list. (More about the list.) \ The developers will see your report and try to fix the problem.""") % \ { "app_name": escape(APP_DISPLAY_NAME) }) self.email_frame = gtk.Frame() self.email_label = gtk.Label() self.email_label.set_markup(_("""\ -Copy and email to nmap-dev@insecure.org:\ +Copy and email to dev@nmap.org:\ """)) self.btn_copy = gtk.Button(stock=gtk.STOCK_COPY) self.btn_ok = gtk.Button(stock=gtk.STOCK_OK)