From: <ope...@li...> - 2013-02-06 19:07:25
|
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "OpenVPN main development repository". The branch, master has been updated via 6e6f55f4ba5deda5649679a13e4e323e07b3e661 (commit) from 607a678d371c56d368319b0a7a1bb147008d5822 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 6e6f55f4ba5deda5649679a13e4e323e07b3e661 Author: Heiko Hund <hei...@so...> Date: Mon Feb 4 11:39:25 2013 +0000 Ignore UTF-8 byte order mark Currently openvpn exits when reading configuration from a file that has an UTF-8 byte order mark (EF BB BF) at its start. While it is useless to put a BOM into UTF-8 encoded files, the Unicode standard [1] permits it (on page 36): "Use of a BOM is neither required nor recommended for UTF-8, but may be encountered in contexts where UTF-8 data is converted from other encoding forms that use a BOM or where the BOM is used as a UTF-8 signature." Notepad.exe, the default text editor on Windows, always puts the BOM into UTF-8 encoded files when saving them. Others may do as well. Just ignoring the UTF-8 BOM will make config files with UTF-8 BOM readable. [1] http://www.unicode.org/versions/Unicode5.0.0/ch02.pdf Signed-off-by: Heiko Hund <hei...@so...> Acked-by: David Sommerseth <da...@re...> Message-Id: 135...@so... URL: http://article.gmane.org/gmane.network.openvpn.devel/7342 Signed-off-by: David Sommerseth <da...@re...> ----------------------------------------------------------------------- Summary of changes: src/openvpn/options.c | 6 +++++- 1 files changed, 5 insertions(+), 1 deletions(-) hooks/post-receive -- OpenVPN main development repository |