Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

contrib: Fix test-security-check fail in Ubuntu 18.04 #13764

Merged
merged 1 commit into from
Jul 30, 2018
Merged

contrib: Fix test-security-check fail in Ubuntu 18.04 #13764

merged 1 commit into from
Jul 30, 2018

Conversation

ken2812221
Copy link
Contributor

  • Fix test-security-check fail in Ubuntu 18.04. Those flags are enabled by default, so we must specify -no to make the executable does 'not' have those attributes.
  • Drop HIGH_ENTROPY_VA. After update our gitian system to Bionic, the compiler should support HIGH_ENTROPY_VA

@laanwj
Copy link
Member

laanwj commented Jul 30, 2018

Looks good to me, thank you!

Good to see that HIGH_ENTROPY_VA is now actually enabled, I think this means #8248 can be closed.

utACK 1e60713

@laanwj laanwj merged commit 1e60713 into bitcoin:master Jul 30, 2018
laanwj added a commit that referenced this pull request Jul 30, 2018
1e60713 contrib: Fix test-security-check fail in Ubuntu 18.04 (Chun Kuan Lee)

Pull request description:

  - Fix test-security-check fail in Ubuntu 18.04. Those flags are enabled by default, so we must specify `-no` to make the executable does 'not' have those attributes.
  - Drop HIGH_ENTROPY_VA. After update our gitian system to Bionic, the compiler should support HIGH_ENTROPY_VA

Tree-SHA512: 78c1f2aae1253ddd52faa1af569b7151a503a217c7ccbe21b8004d8910c45d8a27ff04695eacbdadd7192d2c91c0d59941ca20c651dd2d5052b9999163a11ae4
@ken2812221 ken2812221 deleted the check-security branch July 30, 2018 14:15
deadalnix pushed a commit to Bitcoin-ABC/bitcoin-abc that referenced this pull request Mar 31, 2020
Summary:
```
 - Fix test-security-check fail in Ubuntu 18.04. Those flags are enabled
by default, so we must specify -no to make the executable does 'not'
have those attributes.
 - Drop HIGH_ENTROPY_VA. After update our gitian system to Bionic, the
compiler should support HIGH_ENTROPY_VA
```

Backport of core [[bitcoin/bitcoin#13764 | PR13764]].

Depends on D5609.

Test Plan:
Tested on Ubuntu 18.04 and Debian 10:
  cd contrib/devtools
  ./test-security-check.py

  cmake -GNinja .. \
    -DCMAKE_TOOLCHAIN_FILE=../cmake/platforms/Win32.cmake
    -DBUILD_BITCOIN_SEEDER=OFF
  ninja security-check

  cmake -GNinja .. \
    -DCMAKE_TOOLCHAIN_FILE=../cmake/platforms/Win64.cmake
    -DBUILD_BITCOIN_SEEDER=OFF
  ninja security-check

Reviewers: #bitcoin_abc, jasonbcox

Reviewed By: #bitcoin_abc, jasonbcox

Differential Revision: https://reviews.bitcoinabc.org/D5610
laanwj added a commit that referenced this pull request May 14, 2020
eacedfb scripts: add additional type annotations to security-check.py (fanquake)
83d063e scripts: add run_command to security-check.py (fanquake)
13f606b scripts: remove NONFATAL from security-check.py (fanquake)
061acf6 scripts: no-longer check for 32 bit windows in security-check.py (fanquake)

Pull request description:

  * Remove 32-bit Windows checks.
  * Remove NONFATAL checking. Added in #8249, however unused since #13764.
  * Add `run_command` to de-duplicate all of the subprocess calls. Mentioned in #18713.
  * Add additional type annotations.
  * Print stderr when there is an issue running a command.

ACKs for top commit:
  laanwj:
    ACK eacedfb

Tree-SHA512: 69a7ccfdf346ee202b3e8f940634c5daed1d2b5a5d15ac9800252866ba3284ec66e391a66a0b341f5a4e5e8482fe1b614d4671e8e766112ff059405081184a85
PastaPastaPasta pushed a commit to PastaPastaPasta/dash that referenced this pull request Jul 29, 2020
…18.04

1e60713 contrib: Fix test-security-check fail in Ubuntu 18.04 (Chun Kuan Lee)

Pull request description:

  - Fix test-security-check fail in Ubuntu 18.04. Those flags are enabled by default, so we must specify `-no` to make the executable does 'not' have those attributes.
  - Drop HIGH_ENTROPY_VA. After update our gitian system to Bionic, the compiler should support HIGH_ENTROPY_VA

Tree-SHA512: 78c1f2aae1253ddd52faa1af569b7151a503a217c7ccbe21b8004d8910c45d8a27ff04695eacbdadd7192d2c91c0d59941ca20c651dd2d5052b9999163a11ae4
PastaPastaPasta pushed a commit to PastaPastaPasta/dash that referenced this pull request Jul 29, 2020
…18.04

1e60713 contrib: Fix test-security-check fail in Ubuntu 18.04 (Chun Kuan Lee)

Pull request description:

  - Fix test-security-check fail in Ubuntu 18.04. Those flags are enabled by default, so we must specify `-no` to make the executable does 'not' have those attributes.
  - Drop HIGH_ENTROPY_VA. After update our gitian system to Bionic, the compiler should support HIGH_ENTROPY_VA

Tree-SHA512: 78c1f2aae1253ddd52faa1af569b7151a503a217c7ccbe21b8004d8910c45d8a27ff04695eacbdadd7192d2c91c0d59941ca20c651dd2d5052b9999163a11ae4
ftrader pushed a commit to bitcoin-cash-node/bitcoin-cash-node that referenced this pull request Aug 17, 2020
Summary:
```
 - Fix test-security-check fail in Ubuntu 18.04. Those flags are enabled
by default, so we must specify -no to make the executable does 'not'
have those attributes.
 - Drop HIGH_ENTROPY_VA. After update our gitian system to Bionic, the
compiler should support HIGH_ENTROPY_VA
```

Backport of core [[bitcoin/bitcoin#13764 | PR13764]].

Depends on D5609.

Test Plan:
Tested on Ubuntu 18.04 and Debian 10:
  cd contrib/devtools
  ./test-security-check.py

  cmake -GNinja .. \
    -DCMAKE_TOOLCHAIN_FILE=../cmake/platforms/Win32.cmake
    -DBUILD_BITCOIN_SEEDER=OFF
  ninja security-check

  cmake -GNinja .. \
    -DCMAKE_TOOLCHAIN_FILE=../cmake/platforms/Win64.cmake
    -DBUILD_BITCOIN_SEEDER=OFF
  ninja security-check

Reviewers: #bitcoin_abc, jasonbcox

Reviewed By: #bitcoin_abc, jasonbcox

Differential Revision: https://reviews.bitcoinabc.org/D5610
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants