** Changed in: nautilus
Status: Invalid = Expired
** Changed in: nautilus
Importance: Unknown = High
--
nautilus's clever anti-hax0r detection is really dumb
https://bugs.launchpad.net/bugs/19101
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
** Changed in: nautilus
Status: Confirmed = Invalid
--
nautilus's clever anti-hax0r detection is really dumb
https://bugs.launchpad.net/bugs/19101
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs mailing
the bug is fixed in the current nautilus gio version
** Changed in: nautilus (Ubuntu)
Status: Triaged = Fix Released
--
nautilus's clever anti-hax0r detection is really dumb
https://bugs.launchpad.net/bugs/19101
You received this bug notification because you are a member of Ubuntu
(Importance seems inflated - demoting.)
** Changed in: nautilus (Ubuntu)
Importance: Medium = Wishlist
--
nautilus's clever anti-hax0r detection is really dumb
https://bugs.launchpad.net/bugs/19101
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
** Changed in: nautilus (Ubuntu)
Status: Confirmed = Triaged
--
nautilus's clever anti-hax0r detection is really dumb
https://bugs.launchpad.net/bugs/19101
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs
Hi All,
Don't know if this is fixed or not, but please find below what I had to
do to fix it.
The error I had is the exact same as the one outlined in the bug
description.
I downloaded Java3d in a tar.Z file and everything was fine, I got the
error message when I tried to open it and whenever I
I can confirm this bug, however it happens to me in Fedora Core
2.6.20-1.2948.fc6 , Gnome ver. 2.6.13
It is REALLY annoying and I guess it is a GNOME problem rather and an
Ubuntu problem. I am attaching two screens with examples of the bug in
action. Originally I was going to attach the PDF
This is probably not strictly a nautilus bug. But is damn annoying.
What is happening is a mismatch in the mime-type definitions. In my
case, (and I am using fedora 6, though I suspect Ubuntu will have the
same issue and fix - s/o please test) the freedesktop.org.xml file in
Limiting to things that can be runned might make sense, the discussion
would be better placed upstream though since we are not making decisions
for them and they might have some reason to not limit it to this case
--
nautilus's clever anti-hax0r detection is really dumb
The default would be on cancel and the text explains to user that they
are trying to open a file which has a content different of what the
filename indicates which could be a trojan
--
nautilus's clever anti-hax0r detection is really dumb
https://bugs.launchpad.net/bugs/19101
You received this
On Sun, 2007-05-13 at 15:00 +, Sebastien Bacher wrote:
The default would be on cancel and the text explains to user that they
are trying to open a file which has a content different of what the
filename indicates which could be a trojan
That risk could only ever occur if one tries to run a
Regarding Sebastien's suggestion of adding an open anyway button. If
you put in such a button most users will just press it without regard to
the monologue text. So there would be no point having the monologue at
all - it would just be annoying.
What problem is this message actually supposed to
I had the same problems after a recent upgrade from Dapper 6.06LTS to
Edgy 6.10. It particularly affected HTML and XML files which I noticed
first in yelp - it opened these files in gedit. I also had similar
problems with icons like bug 41772. With .tar.gz archives I also got the
message No
I can confirm this bug (feature?). I installed 7.04 from scratch, and moved
my home dir over from my old Ubuntu laptop. When I try to open png files I get
the error:
The contents of the file indicate that the file is of type PNG image. If
you open this file, the file might present a security
This upload allows you to set a gconf key to not get thar dialog:
nautilus (2.18.0.1-0ubuntu2) feisty; urgency=low
.
* debian/patches/08_display_mimetype_warning.patch:
- new preferences/display_mimetype_warning gconf key which allow to use
or not the mismatching mimetype warning
Is there some way to get gnome to report the source of the MIME values?
For example, having something like:
gnomevfs-info --source-source image.jpg
/usr/blah/mime.something: JPEG Image
/home/user/.local/mime/blah.mime: jpg document
Are the MIME source file locations kept when loading the MIME
There is no command for that Kees, the mimetype database is made from
the .desktop installed and the cache is located to
/usr/share/applications/mimeinfo.cache, the user version is
~/.local/share/applications/mimeinfo.cache. What do you mean by 'Are the
MIME source file locations kept when loading
On Sun, Feb 18, 2007 at 07:49:47PM -, Sebastien Bacher wrote:
There is no command for that Kees, the mimetype database is made from
the .desktop installed and the cache is located to
/usr/share/applications/mimeinfo.cache, the user version is
~/.local/share/applications/mimeinfo.cache.
there is no mention of the location no, that's not really useful though,
you have one user directory to look at and then at the system one
--
nautilus's clever anti-hax0r detection is really dumb
https://launchpad.net/bugs/19101
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Carsten, Caminomaster, could you open new bugs about that, so we don't
bug flood people subscribed to that bug which is not about detection
mistakes themself but what nautilus does when they happen
--
nautilus's clever anti-hax0r detection is really dumb
https://launchpad.net/bugs/19101
--
I've attached detailed files with a comment when I reported the bug as #57038,
with the related information.
Maybe I can add more imformation (see the images):
1. try to open file, and get the horror message.
2. Open the file with rightclickopen withgthumb, then
3. See the image
4. Switch to
Sorry for so long without notice.
On my box this problem occurs with _every_ pdf file. I have no problems with
e.g. jpg files or so. As an example I attach one of the files for which I
verified that it doesn't open upon double-clicking (giving the cited error
message instead).
** Attachment
For most of users it works just fine, maybe you face a buggy case where
the mimetype database should be fixed though. If you want to get that
fixed the right way would be to attach an example of file not opening
fine on your box so we can fix it instead of complaining it happens
hundred of times a
Because time is pasing and we still affected by that bug, I suggest you
to make an update (or tell-us-how) to disable this feature until the bug
is fixed, and launch it when it proved stable or better.
Please note that i'm not the only one suggesting to disable that feature. One
of the thing
that dialog is not a bug, it happens only when the mimetype is not
correct, do you have an example of problematic file to point?
--
nautilus's clever anti-hax0r detection is really dumb
https://launchpad.net/bugs/19101
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
On 1/11/07, Sebastien Bacher [EMAIL PROTECTED] wrote:
that dialog is not a bug, it happens only when the mimetype is not
correct,
Which happens a lot and is handled in a very wrong and stupid way -
thus making it a bug.
--
nautilus's clever anti-hax0r detection is really dumb
it doesn't happen that often and such comment are not really useful, if
you want to get that bug fixed the best way would probable to talk with
upstream about the proper way to fix it
--
nautilus's clever anti-hax0r detection is really dumb
https://launchpad.net/bugs/19101
--
desktop-bugs
On 1/11/07, Sebastien Bacher [EMAIL PROTECTED] wrote:
it doesn't happen that often
lol.. And this is an argument, how?
It happens often enough, and when it happens it happens every time as
a n00b does not know how to fix it permanently -- he is stuck. For
example I have friends and family that
--- Sebastien Bacher [EMAIL PROTECTED] wrote:
it doesn't happen that often and such comment are not really
useful, if you want to get that bug fixed the best way would
probable to talk with upstream about the proper way to fix it
Several hundred times a day is not not that often. It is
a
--- Sebastien Bacher [EMAIL PROTECTED] wrote:
it doesn't happen that often and such comment are not really
useful, if you want to get that bug fixed the best way would
probable to talk with upstream about the proper way to fix it
A couple of hundred times a day is not not that often. It is
Does anyone have a work-around handy, for disabling this entire
security feature?
In my web searches, I find nothing about how to turn it off.
What I do see, are instances of the same error message
reported in numerous forums. The problem is normally
misinterpreted by the local geeks and
*gah* ... I'm also having these problems. Non-geek family-members and
friends do not understand what to do when this happens. :}
It happens a lot with mis-named videos downloaded with FrostWire. Right-
clicking then selecting open with from the context-menu works of
course - but it sucks
I have the same bug when opening codeblocks projects: there file ending
is cbp but Code::Blocks uses XML for its project files.
(sry i have only german message:)
Der Dateiname »GetDotA.cbp« deutet darauf hin, dass der Typ dieser Datei
»Code::Blocks Project« ist. Dem Dateiinhalt zu Folge handelt
Sebastian, here is the result of the two commands:
=
$ grep png document ~/.local -r
/home/ajlewis2/.local/share/mime/packages/Override.xml:mime-type
type=application/x-extension-jpgcommentjpg document/commentglob
pattern=*.jpg//mime-typemime-type
Whatever has installed that
/home/ajlewis2/.local/share/mime/packages/Override.xml and
/home/ajlewis2/.local/share/mime/application/x-extension-png.xml is
responsive for your issue, that's not due to nautilus or the
distribution. Move those files away and your issue should be fixed
--
nautilus's
I moved both files to my Desktop. I rebooted and the problem remains.
I also logged in as another user and did not have the problem opening a
.png. So, it is definitely something with my user.
I did look with dpkg -S to try to determine where the files came from.
They were not a part of any
Ok, here is what I did that works.
cd ~/.local/share/
mv mime bu-mime
Try to open an existing .png and it fails
Right-click/properties/ and choose something other than Image Viewer.
It then opens. Repeat and set back to Image Viewer. It works.
The same works for .jpg and .ogg.
Download
Also changing the file's name will allow it to open:
Double-click linuxreality031.ogg. It fails with the message.
Rename it to linuxreality31.ogg - no change in the extension, just a new
name. Double-click and it opens.
Anita
--
nautilus's clever anti-hax0r detection is really dumb
I've upgraded dapper to edgy and have been getting that message on .wav,
.ogg, .png, .jpg, but not on .gif or .jpeg. Mine says it like this:
The filename PNG_transparency_demonstration_1.png indicates that this
file is of type png document. The contents of the file indicate that
the file is of
** Bug 57038 has been marked a duplicate of this bug
--
nautilus's clever anti-hax0r detection is really dumb
https://launchpad.net/bugs/19101
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Changed in: nautilus (upstream)
Status: Unconfirmed = Confirmed
--
nautilus's clever anti-hax0r detection is really dumb
https://launchpad.net/bugs/19101
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I think your recent comments have more to do with bug 41772.
Does nautilus still warn spuriously for harmless files?
** Changed in: nautilus (Ubuntu)
Status: Unconfirmed = Needs Info
--
nautilus's clever anti-hax0r detection is really dumb
https://launchpad.net/bugs/19101
--
yes
** Changed in: nautilus (Ubuntu)
Status: Needs Info = Confirmed
--
nautilus's clever anti-hax0r detection is really dumb
https://launchpad.net/bugs/19101
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
this is definitely different from bug 41772 (but caused by a similar issue --
two different systems for detecting mime type).
this bug is much easier to fix and i'm astounded that it hasn't been fixed yet.
--
nautilus's clever anti-hax0r detection is really dumb
Ryan, the behaviour would be easy to change ... if upstream agreed to do
that. I'm still not sure we should distro change that rather than
argumenting with upstream until they change it for everybody ;)
--
nautilus's clever anti-hax0r detection is really dumb
https://launchpad.net/bugs/19101
--
45 matches
Mail list logo
