Mercurial > dropbear
changeset 361:461c4b1fb35f insecure-nocrypto
Comment cleanups
| author | Matt Johnston <matt@ucc.asn.au> |
|---|---|
| date | Mon, 02 Oct 2006 06:40:51 +0000 |
| parents | 09cb54106e89 |
| children | 582cb38e4eb5 |
| files | options.h |
| diffstat | 1 files changed, 3 insertions(+), 3 deletions(-) [+] |
line wrap: on
line diff
--- a/options.h Mon Oct 02 06:39:32 2006 +0000 +++ b/options.h Mon Oct 02 06:40:51 2006 +0000 @@ -81,8 +81,8 @@ * ciphers above in the client if you want to use this, or implement cipher * prioritisation in cli-runopts. * - * The best way to do things is probably make normal compile of dropbear with all - * ciphers including "none" as the server, then recompile a special + * The best way to do things is probably make normal compile of dropbear with + * all ciphers including "none" as the server, then recompile a special * "dbclient-insecure" client. */ #define DROPBEAR_NONE_CIPHER @@ -105,7 +105,7 @@ /* You can also disable integrity. Don't bother disabling this if you're * still using a cipher, it's relatively cheap. Don't disable this if you're * using 'none' cipher, since it's dead simple to run arbitrary commands - * on the remote host. Go ahead. Hang yourself with your own rope. */ + * on the remote host. Beware. */ /*#define DROPBEAR_NONE_INTEGRITY*/ /* Hostkey/public key algorithms - at least one required, these are used