lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Thu, 10 Jul 2014 11:51:15 -0300
From: Pablo <paa.listas@...il.com>
To: Full Disclosure Mailing List <fulldisclosure@...lists.org>
Subject: [FD] Should it be better ...

Should it be better to include the Advisory Details/exploit/code in the 
body of the email to FD, and not in a link to a blog/site/company so the 
list archive will be an archive and not a index to some, possible down, 
link?

I saw some reports using this format. It is good for a blog or site 
traffic, but in time, if that sites/blog/entry is deleted or down, the 
de FD archive (and its mirrors) will point to nothing usefull.

I am wrong or it is a good idea?

Sorry for my  poor english.


_______________________________________________
Sent through the Full Disclosure mailing list
http://nmap.org/mailman/listinfo/fulldisclosure
Web Archives & RSS: http://seclists.org/fulldisclosure/

Powered by blists - more mailing lists