linux/meta-openembedded.git/meta-networking/recipes-daemons/vsftpd/vsftpd_3.0.0.bb, branch scarthgapMirror of git.openembedded.org/meta-openembeddedhttps://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=scarthgap2014-09-24T01:59:56+00:00vftpd: update to version 3.0.22014-09-24T01:59:56+00:00Joe Slaterjslater@windriver.com2014-09-15T23:43:51+00:00urn:sha1:2fab4b8902320d0323e3a59ea72e743f24eb36c9
No changes other than source checksum.
Signed-off-by: Joe Slater <jslater@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
vsftpd: fix install warning2014-07-21T22:01:47+00:00Wenzong Fanwenzong.fan@windriver.com2014-07-15T00:59:46+00:00urn:sha1:27981cbef19db115fa81704468721580dedfb1fd
WARNING: QA Issue: vsftpd: Files/directories were installed but not shipped
/run
/run/vsftpd
/run/vsftpd/empty
Signed-off-by: Roy Li <rongqing.li@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
ntp: comment out the invalid server2013-11-29T15:56:31+00:00Roy Lirongqing.li@windriver.com2013-11-29T02:37:37+00:00urn:sha1:03e758cd6744d2be22636ce59dd74d8cfafd4783
When ntpd starts, it will create a daemon to connect this invalid server,
and fail, then ntpd will create other daemon to connect the local-only
(127.127.1.0) server.
The users should be aware that they need to configure the correct ntp
servers, a invalid server will lead to a redundant daemon, so it is better
to comment this example server to wait user to configure
Signed-off-by: Roy Li <rongqing.li@windriver.com>
Signed-off-by: Joe MacDonald <joe@deserted.net>
vsftpd: use quotes to wrap variable2013-10-18T16:26:55+00:00Roy Lirongqing.li@windriver.com2013-10-10T08:34:44+00:00urn:sha1:bcaa7aabf8088aadfdbda4da4a3f1c30af8dd9d6
"test -z ${PAMLIB}" in do_install() may report error if ${PAMLIB}
has space chars. This commit added double quotes to wrap it in
case of errors.
Signed-off-by: Qiang Chen <qiang.chen@windriver.com>
Signed-off-by: Roy Li <rongqing.li@windriver.com>
Signed-off-by: Joe MacDonald <joe@deserted.net>
vsftpd: change default secure_chroot_dir2013-09-23T14:07:23+00:00Ming Liuming.liu@windriver.com2013-09-18T01:44:20+00:00urn:sha1:1c4921817e202909ae97e8108ab1de17ca14f6ce
Change default value of secure_chroot_dir to /var/run/vsftpd/empty, add
volatiles entry for it, to ensure it won't fail to start with error:
"500 OOPS: vsftpd: not found: directory given in 'secure_chroot_dir':/var/share/empty"
This shows up in both standalone mode or started by xined.
Signed-off-by: Ming Liu <ming.liu@windriver.com>
Signed-off-by: Joe MacDonald <joe@deserted.net>
Upgrade vsftpd to 3.0.02013-07-19T15:00:43+00:00Roy.Lirongqing.li@windriver.com2013-07-19T02:19:25+00:00urn:sha1:441502b68d03a4ce7796436a53c5e95399724ad2
Upgrade vsftpd to 3.0.0 with below modification:
1. more strict access limitation, like: do not allow anonymous access
2. use vsftpd.ftpusers and vsftpd.user_list to confine user access
3. enable pam if DISTRO_FEATURE includes pam
4. enable tcp-wrapper
5. install vsftpd.conf with 0600 permission, not 0755
Signed-off-by: Roy.Li <rongqing.li@windriver.com>
Signed-off-by: Joe MacDonald <joe.macdonald@windriver.com>