1 |
Yes you were absolutely right. |
2 |
|
3 |
On 161025-14:46-0400, Fernando Rodriguez wrote: |
4 |
> On Tue, Oct 25, 2016 at 07:38:01PM +0200, Miroslav Rovis wrote: |
5 |
> > Sorry about noticing your reply only now. |
6 |
> > |
7 |
> > Namely, thinking that people over at hardened ML would tell more about |
8 |
> > it, I indirectly initiated a thread over at hardened ML: |
9 |
> > https://archives.gentoo.org/gentoo-hardened/message/09bbf3bfe59a938f11ac044e891db77e |
10 |
> > |
11 |
> > Will surely check it! And am CC'ing hardened about this patch at the |
12 |
> > hardened ML. Maybe they patch and forward the 4.4.8-r1 to 4.4.8-r2 . |
13 |
> > --- |
14 |
> > Only now looked at the patch. |
15 |
> > |
16 |
> > No, you don't get it. And I'm not CC'ing this to hardened ML. |
17 |
Sorry about that. I was not getting it. |
18 |
After all if a patch isn't meant to patch something it only fails :-) . |
19 |
|
20 |
> > |
21 |
> > You can't just run the patch for a vanilla kernel onto a |
22 |
> > grsecurity-patched kernel. Look up the hardened-sources, and how they |
23 |
> > are patched, and what the mm.h and the gup.c in question (there are a |
24 |
> > few of so named files in various directories) look in the |
25 |
> > hardened-sources, and how they look in the vanilla-sources... |
26 |
> |
27 |
> fernan@navi /usr/src/linux-4.4.8-hardened-r1 $ sudo patch -p1 < /home/fernan/dirtycow.patch |
28 |
> patching file include/linux/mm.h |
29 |
> Hunk #1 succeeded at 2131 (offset 19 lines). |
30 |
> patching file mm/gup.c |
31 |
> Hunk #3 succeeded at 357 (offset -5 lines). |
32 |
> |
33 |
|
34 |
|
35 |
It did work here too: |
36 |
|
37 |
# patch -p1 < /home/miro/dirtycow.patch |
38 |
patching file include/linux/mm.h |
39 |
Hunk #1 succeeded at 2131 (offset 19 lines). |
40 |
patching file mm/gup.c |
41 |
Hunk #3 succeeded at 357 (offset -5 lines). |
42 |
# |
43 |
|
44 |
where: |
45 |
|
46 |
# pwd |
47 |
/usr/src/linux |
48 |
# ls -l ../linux |
49 |
lrwxrwxrwx 1 root root 23 2016-10-23 02:37 ../linux -> linux-4.4.8-hardened-r1 |
50 |
# |
51 |
> It works so I guess you can. Never say you can't do something before |
52 |
> trying cause then you look like an idiot. |
53 |
> |
54 |
> And the patch says which are the files in question! |
55 |
> |
56 |
> > |
57 |
> > If I'm not mistaken, and I did check it. No, I'm not mistaken, you just |
58 |
> > sent me the Linus's patch. |
59 |
> |
60 |
> Yes you are mistaken, cause if you've tried it you wouldb't be asking |
61 |
> the question. And yes, that is Linus patch. |
62 |
Right! |
63 |
|
64 |
... |
65 |
> > > |
66 |
> > > Did you tried it? |
67 |
> > > The patch attached comes straight from the git repo, just run: |
68 |
> > > |
69 |
> > > # cd /usr/src/linux |
70 |
> > > # patch -p1 < path/to/patch |
71 |
> > > |
72 |
> > > It'll likely work. |
73 |
> > > |
74 |
And it did, as above... |
75 |
|
76 |
> > |
77 |
> > Thanks for trying to help! Regards! |
78 |
Wrong on my part! |
79 |
|
80 |
Thanks for teaching me! And to teach an obstinate misunderstanding old |
81 |
man takes a little nerve. |
82 |
|
83 |
Regards! |
84 |
-- |
85 |
Miroslav Rovis |
86 |
Zagreb, Croatia |
87 |
http://www.CroatiaFidelis.hr |