From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.179.196 with SMTP id br4cs270257icb; Wed, 1 Dec 2010 16:53:14 -0800 (PST) Received: by 10.224.67.84 with SMTP id q20mr6350603qai.246.1291251190216; Wed, 01 Dec 2010 16:53:10 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id l13si1429951qck.98.2010.12.01.16.53.09; Wed, 01 Dec 2010 16:53:10 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id A250A19783C8; Wed, 1 Dec 2010 19:53:07 -0500 (EST) Received: from mail-qy0-f171.google.com (mail-qy0-f171.google.com [209.85.216.171]) by rubyforge.org (Postfix) with ESMTP id 37CA1197828C for ; Wed, 1 Dec 2010 19:18:09 -0500 (EST) Received: by qyk32 with SMTP id 32so3252929qyk.2 for ; Wed, 01 Dec 2010 16:18:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=sqnQoxLHnhgvi9t20j2D6vXmBFpLb5dvnn+vZvuVe3Y=; b=YtHlnnOKXND8gUL7/bCm3kOsPsSjPoNGHajkO/Y9o5NC+V1hBkMlw4ix/jBOsFwiGG L8bpjBilabQkhCd1H7zeTCAh1fY39H+2xUjSiQULijhn9d845OBqSj8dYBH5COQUvbe8 vozXdP8680eqFT207y4jIBhJlgsvSIaKC2Z1k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=cURa0t3iUXvHGB2YOxYbeEa/92J+Klcz/so521S95OOrs/XbTISjcnVvPKuofHO8jj 3/FeySoDlEsMEEHn9tlbjXyVp7W9XohZqKixdHeBavpo1sMnhJF+D+fvG/Q1v5dLMm2g 8G6W9x9Fe+oB28dz6w0ooAZ2Izg6flgEG/OMc= MIME-Version: 1.0 Received: by 10.229.228.79 with SMTP id jd15mr5491721qcb.67.1291249088873; Wed, 01 Dec 2010 16:18:08 -0800 (PST) Received: by 10.229.225.196 with HTTP; Wed, 1 Dec 2010 16:18:08 -0800 (PST) Date: Thu, 2 Dec 2010 00:18:08 +0000 Message-ID: From: Hamish D To: sup-talk Subject: [sup-talk] sup leaves unencrypted emails in /tmp X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org I noticed that sup appears to leave the unencrypted contents of emails in /tmp - at least it did on my system. This is a pretty serious issue on shared computers. I'm not sure why - my attempts at a quick fix failed. The files are created using Tempfile.new and close is called, but after that the files are written to by gpg. I'm not sure if this means that the tempfile system then doesn't delete them later for some reason. The tempfile stuff does seem to work for the files containing the output from gpg. They do (eventually) get deleted. But the "temporary" files that gpg puts the plaintext into seem to hang around even after I've done a clean exit from sup. If anyone has got good ideas about how to fix this for sup 0.12 I think that would be a fine thing to do. Note that this is the mainline version of sup, not the gpgme version I've been developing - using gpgme means the plaintexts never have to be written to disk, so if we move to gpgme (once I've got it up to scratch) then these problems will go away. Thought people ought to know. Hamish Downer _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk