changeset 426:695413c59b6a

Don't erase every buffer, it's too time consuming. On systems where it matters encrypted swap should be enabled anyway.
author Matt Johnston <matt@ucc.asn.au>
date Mon, 12 Feb 2007 10:44:47 +0000
parents 1afa503e33f5
children ce14fab86732
files packet.c process-packet.c
diffstat 2 files changed, 0 insertions(+), 5 deletions(-) [+]
line wrap: on
line diff
--- a/packet.c	Mon Feb 12 10:43:44 2007 +0000
+++ b/packet.c	Mon Feb 12 10:44:47 2007 +0000
@@ -446,10 +446,6 @@
 	}
 
 	/* finished with payload */
-	buf_burn(ses.writepayload); /* XXX This is probably a good idea, and isn't
-								   _that_ likely to hurt performance too badly.
-								   Buffers can have cleartext passwords etc, or
-								   other sensitive data */
 	buf_setpos(ses.writepayload, 0);
 	buf_setlen(ses.writepayload, 0);
 
--- a/process-packet.c	Mon Feb 12 10:43:44 2007 +0000
+++ b/process-packet.c	Mon Feb 12 10:44:47 2007 +0000
@@ -119,7 +119,6 @@
 	recv_unimplemented();
 
 out:
-	buf_burn(ses.payload); /* Clear the memory to avoid swapping it out */
 	buf_free(ses.payload);
 	ses.payload = NULL;