- Add link to the new advisory page into the support sidebar. - Do not include release info in advisory list as it's not that interesting in this context. - Try to make it more clear where to report security issues to. - Include public key directly on web site instead of referring to FTP site. - Remove some stale information. - Misc minor cleanup. Reviewed by: cperciva, remko, bz (various versions)
		
			
				
	
	
		
			26 lines
		
	
	
	
		
			785 B
		
	
	
	
		
			Text
		
	
	
	
	
	
			
		
		
	
	
			26 lines
		
	
	
	
		
			785 B
		
	
	
	
		
			Text
		
	
	
	
	
	
| <!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
 | |
| <!ENTITY base CDATA "..">
 | |
| <!ENTITY date "$FreeBSD$">
 | |
| <!ENTITY title "FreeBSD Security Advisories">
 | |
| <!ENTITY % navinclude.support "INCLUDE">
 | |
| <!ENTITY % developers SYSTEM "../developers.sgml"> %developers;
 | |
| <!ENTITY advisories.html.inc SYSTEM "advisories.html.inc">
 | |
| ]>
 | |
| 
 | |
| <html>
 | |
|   &header;
 | |
| 
 | |
|   <p>This web page contains a list of released FreeBSD Security
 | |
|     Advisories.  See the <a href="security.html">FreeBSD Security
 | |
|       Information</a> page for general security information about
 | |
|     &os;.</p>
 | |
| 
 | |
|   <p>Issues affecting the FreeBSD Ports Collection are covered in <a
 | |
|       href="http://vuxml.FreeBSD.org/">the FreeBSD VuXML
 | |
|       document</a>.</p>
 | |
| 
 | |
|   &advisories.html.inc;
 | |
| 
 | |
|   &footer;
 | |
| </body>
 | |
| </html>
 |