| 1 |
On 03/12/12 17:58, Javier Juan Martínez Cabezón wrote: |
| 2 |
> |
| 3 |
> This is the patch. |
| 4 |
> |
| 5 |
> linuxnopax is kernel 3.4.1 with rsbac patch implemented and PaX broken |
| 6 |
> when fail patching (excluded rejections and orig files), linux 3.4.1 is |
| 7 |
> handheld solved rejections patched PaX and rsbac. |
| 8 |
> |
| 9 |
> Surely I broken things and maybe one 5 years child would do a better job |
| 10 |
> than me, can you tell me your opinion? are there broken things? |
| 11 |
> |
| 12 |
> |
| 13 |
> |
| 14 |
> |
| 15 |
> |
| 16 |
> On 01/12/12 21:37, Anthony G. Basile wrote: |
| 17 |
>> On 11/22/2012 12:49 PM, Javier Juan Martínez Cabezón wrote: |
| 18 |
>>> |
| 19 |
>>> |
| 20 |
>>> Hi all, I saw that in the last ebuild (3.4.1), PaX is in |
| 21 |
>>> UNIPATCH_EXCLUDE. What have you Planned about this?. |
| 22 |
>>> |
| 23 |
>>> I also knew the existence of a base rsbac_policy based hardened gentoo |
| 24 |
>>> subproject? is there anything written about it? |
| 25 |
>>> |
| 26 |
>>> Thanks for all. |
| 27 |
>>> |
| 28 |
>> |
| 29 |
>> When last I tried to apply the pax patches on top of rsbac, they did not |
| 30 |
>> go. People kept saying the did, but they did not without hacking. If |
| 31 |
>> you want to provide me with an rsbac patchset and pax patchset that are |
| 32 |
>> compat I will try again. |
| 33 |
>> |
| 34 |
>> |
| 35 |
> |
| 36 |
|
| 37 |
I have just compiled in my computer without incidents but... |
| 38 |
WARNING: modpost: Found 11411 section mismatch(es). |
| 39 |
I just only modify 6 source code files, just a record to have 11411 |
| 40 |
mismatches. |
| 41 |
|
| 42 |
Probably my "patch" finally makes my kernel start making coffee instead |
| 43 |
protecting memory or implementing MAC.... I will see. |
Archives