Based on Paul Fertser <fercerpav@gmail.com>'s guidance:
Change AUTORELEASE in rules.mk to:
```
AUTORELEASE = $(if $(DUMP),0,$(shell sed -i "s/\$$(AUTORELEASE)/$(call commitcount,1)/" $(CURDIR)/Makefile))
```
then update all affected packages by:
```
for i in $(git grep -l PKG_RELEASE:=.*AUTORELEASE | sed 's^.*/\([^/]*\)/Makefile^\1^';);
do
make package/$i/clean
done
```
Signed-off-by: Kuan-Yi Li <kyli@abysm.org>
Use OpenSSL instead of the internal crypto backend. Everything in
OpenWrt that links to libsrtp2 depends on OpenSSL anyway.
Upsides:
- the libsrtp2 package size shrinks a bit (for example from 35 to 24
KiB on ath79)
- allows to use more cipher suites
- may allow for hardware acceleration
Closes#763
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
- switch to $(AUTORELEASE)
- update upstream URL
- add ABI_VERSION
- drop patch that is included upstream
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Bump to upstream release 2.3.0. Move folder and change PKG_NAME so that
we don't have to deal with how github names the tar.gz archive.
Also, don't install the libsrtp2.so symlink anymore on target, as it is
not required and only used in staging.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
bgg729 already makes sure that the compiler emits position-independent
code. Adding $(FPIC) makes no difference. In addition the libsrtp build
system puts its own flag behind the CFLAGS, overriding whatever was set
before.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Plain git:// doesn't add security. Use https:// instead. See
https://gist.github.com/grawity/4392747.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Rosen Penev