After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 139629 - Security warning dialog doesn't say what the correct extension is
Security warning dialog doesn't say what the correct extension is
Status: RESOLVED DUPLICATE of bug 138033
Product: nautilus
Classification: Core
Component: File and Folder Operations
unspecified
Other All
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-04-10 01:36 UTC by Peter De Wachter
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Peter De Wachter 2004-04-10 01:36:03 UTC
I have a file called "c-faq.txt" containing a
saved Usenet posting of the comp.lang.c FAQ. When
I try to open this file, I get the following warning:

<quote>
Cannot open c-faq.txt

The filename "c-faq.txt" indicates that this file
is of type "Plain text document". The contents of
the file indicate that the file is of type "Email
message/mailbox". If you open this file, the file
might present a security risk to your system.

Do not open the file unless you created the file
yourself, or received the file from a trusted
source. To open the file, rename the file to the
correct extension for "Email message/mailbox",
then open the file normally. Alternatively, use
the Open With menu to choose a specific
application for the file. 
</quote>

This doesn't give any hint to what Nautilus
considers the correct extension for an email message.

(I'll file seperate bugs about Nautilus
misidentifying a Usenet post as a email message,
and there is nothing dangerous about opening
something as a plain text file.)
Comment 1 Matthew Gatto 2004-10-29 01:14:19 UTC
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you find.

Discussion of this is in bug 138033.

*** This bug has been marked as a duplicate of 138033 ***