Closed Bug 264930 Opened 20 years ago Closed 18 years ago

security alert: attachment filename "summary2004.txt .pif"

Categories

(SeaMonkey :: MailNews: Message Display, defect)

1.7 Branch
x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 186974

People

(Reporter: jps, Unassigned)

References

(Blocks 1 open bug)

Details

When a filename wider than a certain number of characters, including spaces, is
displayed in the attachment window of the email message view, then "..." at the
right side is used to indicate that the file name is actually longer.  This is a
very small indicator.

Please advise a-priority junk rule authors that I will never consider a 
file with more than two spaces in a row ending in a dangerous extention 
to be anything ever than junk, and I believe all but the worm-curious 
agree with this position.

Also, please consider a more prominent indicator than "..." when the truncated
filename containes consecutive whitespace.

Reproduction of worms is ill-advised.  You may however mail yourself an
ordinary text file named "diagram.gif                                          
                           .exe" to understand the importance of this problem.
Dup of bug to put the elipsis in the middle, not end.
Group: security
Keywords: crash, dataloss, privacy
Whiteboard: DUPME
Agreed, but I still wish we would enhance our a-priori junk rules to clobber a
worm now and then.  If the users don't like it, they can explicitly un-junk them.
I can find no such bug asking elipses to be placed in the middle of cropped
filenames, and therefore, until such a duplicate is found, I am blocking bug
74697 with just that suggestion.

I continue to suggest that another bug needs to be filed establishing some
a-priori junk rules to blast such unfreindly attachments with the
recyccle-these-bits icon.
Blocks: 74697
Whiteboard: DUPME
Product: Browser → Seamonkey
related to Bug 254913
Assignee: sspitzer → mail
Duping to the RFE for ellipsis mid-name.  See bug 74697 comment 20 for why this really isn't a critical or security issue, at least not with the current file handling.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.