opening crypted files via spotlight bypasses prompt for encryption key

edenzik / macvim

Automatically exported from code.google.com/p/macvim

0 stars 0 forks source link

opening crypted files via spotlight bypasses prompt for encryption key #167

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

In MacOS 10.5.6, install MacVim 7.2-stable in /Applications.
Associate a crypted text file with MacVim.app (via the "Get Info" panel).
Opening the text file by browsing to it in Finder and hitting Cmd-O works as 
expected: a MacVim 
window opens and prompts for the encryption key.
Opening the file by searching for it in Spotlight skips the encryption key 
prompt and displays the 
raw file, as if cat-ted.

Original issue reported on code.google.com by peter.ab...@gmail.com on 7 Apr 2009 at 2:35

GoogleCodeExporter commented 9 years ago

Just noticed two "Vim" processes spawned by launchd after triggering this issue 
a few
times.  Each was taking up all of the idle cycles on one of my CPUs.  I
double-checked that the MacVim Application was completely quit out of.  The 
processes
responded to a normal quit delivered by Activity Monitor.  Sample from Activity
Monitor attached.

Original comment by peter.ab...@gmail.com on 7 Apr 2009 at 3:14

Attachments:

[Sample of Vim.txt](https://storage.googleapis.com/google-code-attachments/macvim/issue-167/comment-1/Sample of Vim.txt)

GoogleCodeExporter commented 9 years ago

What exactly do you mean by a "crypted" text file?  How can I go about creating 
one so that I can try to recreate 
this bug?  (I've never come across this feature!)

Original comment by bjorn.winckler@gmail.com on 7 Apr 2009 at 2:22

GoogleCodeExporter commented 9 years ago

See the vi man page for the "-x" option.  To create a crypted file, execute 
"mvim -x
newfile" at the command line.  Normally, vi detects a previously-crypted file 
even
when opened without the "-x".

Original comment by peter.ab...@gmail.com on 7 Apr 2009 at 3:01

GoogleCodeExporter commented 9 years ago

Thanks, I have found the bug but it will require some thinking before I can fix 
it.  I'll let you know when it is 
done.

Original comment by bjorn.winckler@gmail.com on 7 Apr 2009 at 6:21

GoogleCodeExporter commented 9 years ago

Just checked, problem reproducible in macos 10.6 with snapshot 51.

Original comment by peter.ab...@gmail.com on 6 Dec 2009 at 5:01

GoogleCodeExporter commented 9 years ago

I've finally fixed this problem (to be included in snapshot 52).

Original comment by bjorn.winckler@gmail.com on 1 Mar 2010 at 7:23

Changed state: Fixed