full-disclosure - Re: Temporary Files and Web Sites (swp, ~, etc)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20040812082418.GA30843@mail>
From: trik-news at gmx.de (Spiro Trikaliotis)
Subject: Re: Temporary Files and Web Sites (swp, ~, etc)

Hello,

* On Thu, Aug 12, 2004 at 09:45:20AM +0300 bugtraq@...ondsecurity.com wrote:

> What can you do?
> There isn't much you can do beside:
> 1) Avoid leaving these files behind
> 2) Make rules in Apache/whatever to block access to .swp, ~, etc files.

3) Never edit files directly on the server, but do it in your own sandbox
   (whatever that is), test it (!), and only put it online afterwards,
   if everything works (and only the relevant files). This even avoids
   opening security holes just because a "quick fix" did not work as
   expected.

But, I ask if this fits the topic of this mailing list? Because of this,
replies via PM, please.

Regards,
   Spiro.

-- 
Spiro R. Trikaliotis
http://www.trikaliotis.net/