In Magit commits are created using the committing popup (c). That popup would therefore be a good place to start looking for gpg support. If you do that, then you will find this:
=S Sign using gpg (--gpg-sign=)
So type = S and the select a key. To avoid having to do that every time you create a commit you can save the value of that argument (and all other ...
18 years ago, you were right to be worried. But time has marched on. Since Emacs 22, there is a decent built-in mechanism to whitelist safe local variables. The details are documented in the Emacs Lisp manual. The most important aspects are:
Lisp authors can declare safe values for each variable. This is a whitelist: if the Lisp programmer hasn't done ...
While I personally don't use babel much, going from the example, this should simply be:
(defun my-org-confirm-babel-evaluate (lang body)
(not (member lang '("C" "clojure" "sh"))))
(setq org-confirm-babel-evaluate 'my-org-confirm-babel-evaluate)
Where C, clojure and sh should be replaced by the languages you don't want the confirmation for.
Emacs is pretty safe when it comes to local variables. It does not actually evaluate anything for file- or directory-local variables, it only parses Lisp syntax. Also, a variable has to be declared "safe" before it will be set by Emacs, and that declaration also includes a predicate. So a variable can say "a file may set this, but only if it is a string".
The short answer is unless you read through the code yourself you are taking a lot on trust. Having said that trusting a project sourced from an upstream SCM is a little safer than one which has been pulled directly from the Emacs Wiki for example. However fundamentally you are trusting the author of the package not to turn evil and abuse the ability to run ...
shr.el has a (defvar shr-inhibit-images nil), and a
(defcustom shr-blocked-images nil
"Images that have URLs matching this regexp will be blocked."
:type '(choice (const nil) regexp))
It seems like (setq shr-inhibit-images t) stops the web requests when I view HTML emails.
Note that it turns off image display for eww ...
We can set
(setq mm-sign-option 'guided)
and now we will be prompted with key selection menu before sending a message.
Option of creating signed parts. nil, use default signing keys; guided, ask user to select signing keys from the menu.
We should be able to automate key selection based on e.g. From: field with ...
I use pass to store my passwords, and a lisp wrapper to set the value appropriately:
(defun my-password (pass)
(concat "pass show " pass))))
(setq my-jabber-password (my-password "Personal/jabber"))
You could use the approach described in this article, which uses a call to head to get the first bits/8 bytes from /dev/urandom using the following snippet:
(with-temp-buffer (set-buffer-multibyte nil)
(call-process "head" "/dev/urandom" t nil "-c" (format "%d" (/ bits 8)))
(let ((f (apply-partially #'format "%02x")))
(concat "16#" (mapconcat f (...
(setq org-confirm-shell-link-function nil)
Shell links can be dangerous: just think about a link
[[shell:rm -rf ~/*][Google Search]]
This link would show up in your Org document as "Google Search",
but really it would remove your entire home directory.
Therefore we advise against setting this variable to nil.
Just change it to ‘y-or-n-p’ if ...
The first thing to do is confirm which fields need to be included in the secret. Frequently this includes host and user. For smtp, this also includes port. You can find this information by looking for an auth-source-search call (or using edebug to pause execution on it).
If all you need is host and user, you can use a graphical client like Seahorse if you ...
You do not need to use a full Emacs email client like Gnus or mu4e (although I recommend it); message-mode should be sufficient to compose and send email, and to encrypt or sign outgoing messages. I have not used smtpmail before. My setup relies on an external smtp client (msmtp), but this should not be necessary.
To compose emails, use message-mail. To ...
Dunno the official answer. For that you had better ask email@example.com.
My guess is no. Emacs 24.3 will not be updated for ordinary, non-security reasons, at least. Of that I'm pretty sure.
But security fixes are taken very seriously. Whether they are backported, and if so how far, I don't know.