comparison packet.c @ 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 c5d3ef11155f
children 9c61e7af0156
comparison
equal deleted inserted replaced
425:1afa503e33f5 426:695413c59b6a
444 ses.writepayload->len); 444 ses.writepayload->len);
445 buf_incrwritepos(clearwritebuf, ses.writepayload->len); 445 buf_incrwritepos(clearwritebuf, ses.writepayload->len);
446 } 446 }
447 447
448 /* finished with payload */ 448 /* finished with payload */
449 buf_burn(ses.writepayload); /* XXX This is probably a good idea, and isn't
450 _that_ likely to hurt performance too badly.
451 Buffers can have cleartext passwords etc, or
452 other sensitive data */
453 buf_setpos(ses.writepayload, 0); 449 buf_setpos(ses.writepayload, 0);
454 buf_setlen(ses.writepayload, 0); 450 buf_setlen(ses.writepayload, 0);
455 451
456 /* length of padding - packet length must be a multiple of blocksize, 452 /* length of padding - packet length must be a multiple of blocksize,
457 * with a minimum of 4 bytes of padding */ 453 * with a minimum of 4 bytes of padding */