otp.git - Mirror of Erlang/OTP repository.

Age	Commit message (Collapse)	Author
2010-11-17	Allow user to specify the IP address epmd binds to	Holger Weiß
	The IP address(es) epmd binds to can now be specified by the user, either via epmd's new "-address" option or (if that's not used) by setting the environment variable ERL_EPMD_ADDRESS. Multiple addresses may be specified using a comma-separated list. If the loopback address is not in this list, it will be added implicitly, so that the daemon can be queried by an interactive epmd process.
2010-08-31	Fix anomalies in epmd not yet reported as security issues	Patrik Nyblom
	Use erts_(v)snprintf to ensure no buffer overruns in debug printouts. Disallow everything except port and name requests from remote nodes. Disallow kill command even from localhost if alive nodes exist. -relaxed_command_check when starting epmd returns the possibility to kill this epmd when nodes are alive (from localhost). Disallow stop command completely except if -relaxed_command_check is given when epmd was started. Environment variable ERL_EPMD_RELAXED_COMMAND_CHECK can be set to always get -relaxed_command_check.
2010-08-31	Remove two buffer overflow vulnerabilities in EPMD	Patrik Nyblom

2010-05-03	Exit if an error occurs with the listening socket	Michael Santos
	Check errno if either select() or accept() returns an error and exit. This prevents epmd from looping and taking up 100% CPU.
2010-04-30	epmd: Remove stray OSE/Delta support	Björn Gustavsson

2010-03-23	Fix compilation of epmd with IPv6 enabled	John-Mark Bell
	Modify IPv6 variants of SET_ADDR_LOOPBACK and SET_ADDR_ANY to use in6addr_loopback and in6addr_any.
2010-01-11	Merge branch 'kj/epmd-port2resp-trunc-extra' into ccase/r13b04_dev	Erlang/OTP
	* kj/epmd-port2resp-trunc-extra: Handle "extra" field according to specs in ALIVE2_REQ and PORT2_RESP. OTP-8361 EPMD now correctly handles the extra data field which can be given in the ALIVE2_REQ request and retrieved in the PORT2_RESP response. (Thanks to Klas Johansson.)
2009-12-22	Handle "extra" field according to specs in ALIVE2_REQ and PORT2_RESP.	Klas Johansson
	Don't let the length field pollute the value of the "extra" field in ALIVE2_REQ. Extra was read, starting at the second byte of the two byte length field, which meant that it was included in the result and the last byte of the value was skipped: if "extra" is <<1, 2>>, return <<0, 2, 1, 2>> not <<0, 2, 2, 1>> Increment the offset correctly when sending PORT2_RESP, in order to make sure the "extra" field won't be truncated: if "extra" is <<>>, return <<0, 0>> not <<0>> if "extra" is <<1, 2>>, return <<0, 2, 1, 2>> not <<0, 2, 1>> Allow null characters in "extra".
2009-11-20	The R13B03 release.OTP_R13B03	Erlang/OTP