X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=blobdiff_plain;f=doc%2Ffaq.but;h=ff3bd6d45660c6fee5bc12489097bd3434fe0ac4;hb=f4713d37b88290e8ba8d1315bf5811ac145a9838;hp=6227a809dd92a7519657345e207cff6d0f4fc3cd;hpb=bb6dd987eee2cc52bdbb50d540a9b463c747d367;p=PuTTY.git

diff --git a/doc/faq.but b/doc/faq.but
index 6227a809..ff3bd6d4 100644
--- a/doc/faq.but
+++ b/doc/faq.but
@@ -252,10 +252,6 @@ Pageant.
 If you don't have \i{Gtk}, you should still be able to build the
 command-line tools.
 
-Note that Unix PuTTY has mostly only been tested on Linux so far;
-portability problems such as BSD-style ptys or different header file
-requirements are expected.
-
 \S{faq-unix-why}{Question} What's the point of the Unix port? Unix
 has OpenSSH.
 
@@ -1110,8 +1106,13 @@ The PuTTY policy changed because the developers were informed of
 ways to implement DSA which do not suffer nearly as badly from this
 weakness, and indeed which don't need to rely on random numbers at
 all. For this reason we now believe PuTTY's DSA implementation is
-probably OK. However, if you have the choice, we still recommend you
-use RSA instead.
+probably OK.
+
+The recently added elliptic-curve signature methods are also DSA-style
+algorithms, so they have this same weakness in principle. Our ECDSA
+implementation uses the same defence as DSA, while our Ed25519
+implementation uses the similar system (but different in details) that
+the Ed25519 spec mandates.
 
 \S{faq-virtuallock}{Question} Couldn't Pageant use
 \cw{VirtualLock()} to stop private keys being written to disk?