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: <200404021827.i32IRJj4004353@turing-police.cc.vt.edu>
From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks@...edu)
Subject: FD should block attachments 

On Fri, 02 Apr 2004 08:27:18 PST, Tim <tim-security@...tinelchicken.org>  said:

> I have to agree here.  There are some who would say that email was never
> intended as a means to transfer files.  It is a very impolite way of
> getting a group of people a file.  Sending a link, is much more
> considerate to the subscribers and to those hosting the list.

This will be more useful once there's a way to do all of the following:

1) Upload the file to a webserver (which Joe User often doesn't have)
2) Set permissions on the file so only the recipients can get it.
3) Figure out the resulting URL for inclusion in the mail.
4) Deal with removing the file after a week or so.
5) All the *other* cruft involved in that whole process.

In general, *not* something your Aunt Tillie can deal with.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20040402/5acbd901/attachment.bin

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ