projects / platform / core / connectivity / ua-manager.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: d958252) | patch
Apply secure option
authorsaerome.kim <saerome.kim@samsung.com>
Fri, 8 Nov 2019 08:44:37 +0000 (17:44 +0900)
committersaerome.kim <saerome.kim@samsung.com>
Fri, 8 Nov 2019 10:55:21 +0000 (19:55 +0900)
commitf10fc8c15e15c8966733b580c51f67cce69a6e3e
treede696827cb886bd7da289846ae18f9614c748d57tree | snapshot
parentd958252d0db2cd890325f48ef5f6dd89f6b665a4commit | diff
Apply secure option

- Problem: There is no FORTIFY option.
- Cause: Unlike the SSP that catches the stack BOF, a protection technique is
  needed to catch the BOF that occurs in a general memory buffer.
- Solution: apply FORTIFY and stack-canar options.

Change-Id: I1c1d45f1edfb0e017bdd8a3a3c1f42469f324220
Signed-off-by: saerome.kim <saerome.kim@samsung.com>
ua-api/CMakeLists.txt diff | blob | history
ua-daemon/CMakeLists.txt diff | blob | history
Domain: Network & Connectivity / Common;