Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In /etc/ssh/sshd_config, there is an option called AcceptEnv that allows the ssh client to send environment variables. I need to be able to send a large number of environment variables. These change on every connection from the client, so putting them in a login script on the server would be more difficult.

I've read that "AcceptEnv *" is insecure. I'd like to understand why before I try to get a list of all of the environment variables that are attempted to be set to put there.

Why is it considered insecure? Can I get an example?

share|improve this question
up vote 10 down vote accepted

Enabling environment processing may enable users to bypass access restrictions in some configurations using mechanisms such as LD_PRELOAD.

Not all version of the man pages for sshd_config mention this. If your environment variables are changed beforehand and certain privileged processes are executed with new libraries specified by this, issues can result.

Take a look at and search for "LD_PRELOAD Exploit". Sorry, the page has no anchor links.

See also this StackOverflow question, "What is the LD_PRELOAD trick?"

Setting environment variables after connection is fine, but when those variable are interpreted by the ssh daemon as set by AcceptEnv, Bad Things may occur.

share|improve this answer
How is it any different than when they set the variables manually after logging in? – Joseph Garvin Feb 9 '15 at 15:05

Do not accept environment variables:

See this exploit that came out recently.. if you accept environment variables then you are opening up a really nasty exploit:

share|improve this answer
You are spreading fear IMO. If you are that worried why do they have SSH access? And btw you can't stop them from setting environment variables once they are in the shell or even functions. That exploit is about unauthorized shell access through stuff like nginx, not authorized shell access. – Jordon Bedwell Oct 18 '14 at 9:35
Anyway you accept at least one env. variable named TERM. There can be valid needs to accept other variables like PRINTER, EDITOR, PAGER, ... – ibre5041 Sep 11 '15 at 9:51

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.