> Thank you, Ben! That's exactly what I meant. For this, keeping a variable in a script-local function would suffice -- I personally haven't found a way yet to access a s:var. (If you know of a vim-only solution, please tell me.) Although rot13 is of course is no encryption/obfuscation at all, IMHO a randomized replacement table method probably won't be any less secure than saving the passwords to disk (ready for take-away and later inspection).
Also, you will most likely have to define functions that decrypt the stuff. So, if bad people really gained access to your terminal, nothing would stop them from calling these functions (calling script-local functions isn't difficult). This could be less safe than keeping them plain text in a script-local variable (which I don't know how to access from within an unpatched vim). BTW maybe I missed something but if you store passwords in a script local variable how could they show up in session files? Against which kind of attacks would you like to protect the passwords? #1 echo :echo g:my_passwords #2 session :exec 'edit '. v:this_session #3 core dump inspection? #4 ... thomas. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---