* Upgrade networkmanager from 1.0.6 to 1.0.10.
* add patches:
- Apply three bug fix patches from NM git.
- Apply a patch to fix a bug in the header files breaking gnome-panel build.
- fix ppp rdepend: pppd is not on the target if NM does not rdepend on it.
Signed-off-by: Adrian Freihofer <adrian.freihofer@gmail.com>
Signed-off-by: Dai Caiyun <daicy.fnst@cn.fujitsu.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
The current recipe make no difference between
the source and the build directory. There are
source files outside this directory and isn't
possible to patch these files.
This changes adds the build directory path to
the recipe, now is possible to patch files in
other directories, if required.
Signed-off-by: Mariano Lopez <mariano.lopez@linux.intel.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
The iakerb_gss_export_sec_context function in lib/gssapi/krb5/iakerb.c
in MIT Kerberos 5 (aka krb5) 1.14 pre-release 2015-09-14 improperly
accesses a certain pointer, which allows remote authenticated users
to cause a denial of service (memory corruption) or possibly have
unspecified other impact by interacting with an application that calls
the gss_export_sec_context function. NOTE: this vulnerability exists
because of an incorrect fix for CVE-2015-2696.
Backport upstream commit to fix it:
3db8dfec1e
Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
The build_principal_va function in lib/krb5/krb/bld_princ.c in MIT
Kerberos 5 (aka krb5) before 1.14 allows remote authenticated users
to cause a denial of service (out-of-bounds read and KDC crash) via
an initial '\0' character in a long realm field within a TGS request.
Backport upstream commit to fix it:
f0c094a1b7
Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
lib/gssapi/krb5/iakerb.c in MIT Kerberos 5 (aka krb5) before 1.14
relies on an inappropriate context handle, which allows remote
attackers to cause a denial of service (incorrect pointer read and
process crash) via a crafted IAKERB packet that is mishandled during
a gss_inquire_context call.
Backport upstream commit to fix it:
e04f028351
Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
lib/gssapi/spnego/spnego_mech.c in MIT Kerberos 5 (aka krb5) before
1.14 relies on an inappropriate context handle, which allows remote
attackers to cause a denial of service (incorrect pointer read and
process crash) via a crafted SPNEGO packet that is mishandled during
a gss_inquire_context call.
Backport upstream commit to fix it:
b51b33f2bc
Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Fix remaining QA issues (dependency-wise) like
WARNING: QA Issue: samba rdepends on libacl, but it isn't a build dependency? [build-deps]
WARNING: QA Issue: samba rdepends on libavahi-client, but it isn't a build dependency? [build-deps]
broken perl library path, having a default PACKAGECONFIG, but allow
user-defined one and rely on PACKAGECONFIG instead of DISTRO_FEATURES.
Signed-off-by: Jens Rehsack <sno@netbsd.org>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Since there're surely lot's of individual distibutions not moved to systemd,
allow sane samba start/stop with systemv anyway. Rely on lsb-init-functions
for improved control.
Signed-off-by: Jens Rehsack <sno@netbsd.org>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Drop 'inline' from some functions that had 'inline' keyword without
a definition at that point (they were defined in a different file).
Signed-off-by: S. Lockwood-Childs <sjl@vctlabs.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Package QA complains about these files being installed but not shipped:
/run
/run/NetworkManager
Signed-off-by: Maciej Borzecki <maciej.borzecki@open-rnd.pl>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
4.1.3 has the dependence on libsodium,
4.1.3 asks pkgconfig bbclass to configure,
add a target to build ptest, since the orignial check will build and run
which is not suitable for cross-compile, and change the ptest installation
directories
Signed-off-by: Roy Li <rongqing.li@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
The 2.4 version is the only version available so makes no sense to set
it as lower preference.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
The patch has not been available in the 2.4 version form and thus the
recipe was unbuildable.
Fix by removing the patch file, which is unused, and the reference for
it from the recipe.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Update the checksum of COPYING,since the date in it has been changed,
but the LICENSE has not been changed.
Signed-off-by: Li Xin <lixin.fnst@cn.fujitsu.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
The bluetooth.service runs bluetoothd to manage bluetooth devices, if
present, in the system. By design, it should be running in either of
two cases:
1. A userspace utility (e.g. networkmanager) has made a dbus request
for bluetooth services provided by org.bluez. Even without this
patch, the bluetooth.service gets run via dbus activation under the
systmed aliased name 'dbus-org-bluez.service'. Perfect!
2. A bluetooth device is added to the system. When a bluetooth device
is added, udev triggers the special systemd target, bluetooth.target
intended to pull in any services needed for bluetooth linked under
bluetooth.target.wants.
Enable bluetooth.service so it gets linked under bluetooth.target.wants
and bluetoothd gets started when a user adds a bluetooth device to the
system.
To be clear, this isn't forcing bluetooth to be running all the time---
only when either of #1 or #2 are true.
Signed-off-by: Ash Charles <ashcharles@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
