improve layout

git-svn-id: file:///home/svn/samba-web/trunk@1365 44aeb9d7-1cd8-0310-b257-a505e0beeac2

diff --git a/news/symlink_attack.html b/news/symlink_attack.html
index 5db3929192f15ce3d0b9769659573ffaab907850..0b9990b451ff133bcbd8d75c421e135367ef456e 100644 (file)
--- a/news/symlink_attack.html
+++ b/news/symlink_attack.html
@@ -8,7 +8,7 @@
 
 <p>A user named "kcopedarookie" posted what they claim to be a video
 of a
-zero-day <a href="http://www.youtube.com/watch?v=NN50RtZ2N74&aia=true">exploit
+zero-day <a href="http://www.youtube.com/watch?v=NN50RtZ2N74&amp;aia=true">exploit
 in Samba</a> on youtube yesterday.</p>
 
 <p>The video shows modifications to smbclient allowing
@@ -25,6 +25,7 @@ in Samba.</p>
 </pre>
 in the [global] section of your smb.conf and restart
 smbd to eliminate this problem.</p>
+<p></p>
 
 <h5>Longer FAQ: The real issue</h5>
 
@@ -38,21 +39,21 @@ problem).</p>
 allows Administrators to locally (on the server) add a symbolic link
 inside an exported share which SMB/CIFS clients will follow.</p>
 
-<p>As an example, given a share definition:
+<p>As an example, given a share definition:</p>
 <pre>
   [tmp]
        path = /tmp
        read only = no
        guest ok = yes
-</pre></p>
+</pre>
 
-<p>The administrator could add a symlink:
+<p>The administrator could add a symlink:</p>
 
 <pre>
   $ ln -s /etc/passwd /tmp/passwd
 </pre>
 
-and SMB/CIFS clients would then see a file called "passwd" within
+<p>and SMB/CIFS clients would then see a file called "passwd" within
 the [tmp] share that could be read and would allow clients to read
 /etc/passwd.</p>