The ruby rpms
d9051618e3
`checksec` output since v2.7.0 become more nuanced. Previously, the `FORTIFY` could become just `Yes` / `No`. Now it can have also `Partial` state, which better describe our situation. Currently if e.g. `Fortifiable=28` and `Fortified=11`, that means that the fortification is just partial and another 17 functions could be fortified. Also, check the numbers specifically, because this seems to be the interesting information. Unfortunatelly, the results differ between platforms. Last but not least, use `sed` to analyze the output, because this allows to always display the processed text. The trick comes from \[[1]\]. On top of this, use XML formatted output, which provides more context to reader. [1]: https://unix.stackexchange.com/questions/366/convince-grep-to-output-all-lines-not-just-those-with-matches Resolves: rhbz#2282953 |
||
|---|---|---|
| .gitignore | ||
| libruby.stp | ||
| macros.ruby | ||
| macros.rubygems | ||
| operating_system.rb | ||
| ruby-2.1.0-always-use-i386.patch | ||
| ruby-2.1.0-custom-rubygems-location.patch | ||
| ruby-2.1.0-Enable-configuration-of-archlibdir.patch | ||
| ruby-2.1.0-Prevent-duplicated-paths-when-empty-version-string-i.patch | ||
| ruby-2.3.0-ruby_version.patch | ||
| ruby-2.7.0-Initialize-ABRT-hook.patch | ||
| ruby-3.3.0-Disable-syntax-suggest-test-case.patch | ||
| ruby-3.3.0-Revert-Optimize-allocations-in-Hash-compare_by_identity.patch | ||
| ruby-3.4.0-fix-branch-protection-compilation-for-arm.patch | ||
| ruby-3.4.0-Fix-pointer-incompatiblity.patch | ||
| ruby-exercise.stp | ||
| ruby.rpmlintrc | ||
| ruby.spec | ||
| rubygems.attr | ||
| rubygems.con | ||
| rubygems.prov | ||
| rubygems.req | ||
| sources | ||
| test_abrt.rb | ||
| test_openssl_fips.rb | ||
| test_systemtap.rb | ||