grsecurity patch failed to decipher disk encryption
Posted: Tue Jul 09, 2013 6:37 pmI hope someone is listening. Well, I seem to be going from bad to really bad. First time I compiled the kernal after applying the patch, I found, when booting into the new kernel, that a couple of major programs were broken, badly. My strategy changed this time around and I compiled the kernel before I installed any major program. Although the compilation appeared to go rather well, when I then tried booting into the new kernel, it could not decipher my disk encryption, failing to recognize my passphrase. Do others have these sorts of difficulty with this patch as well?
I have no clue as to how to fix such an issue or what might have caused it. My only guess would be that one of the options made during "make menuconfig" was incompatible with my encryption, but that would just be a hunch. Can someone suggest an alternative notion or recommendation? I am using standard dmcrypt, no lvm, no truecrypt, no magic wand. Does it occur to anyone that lacking any particular one of the configuration options for the kernel would render the encryption support defunct? If not, does there seem to be a better question I ought to be asking at this point? Frankly, I don't believe that I have asked for much in the way of support, no hand-holding, no kiddie-gloves, not even any pointing out of the obvious. Am I expecting too much from the gresec team, impatiently? At this rate I would not be able to meet my self-appointed deadline for completion of this project, and I am wondering now whether I ought to consider settling for an alternative security program? That would not be my preference, to be sure.
There is nothing terribly complicated about my system, really nothing. I feel a bit frustrated, puzzled and, well, disappointed in that this procedure seems to lack a certain amount of empathy with my condition. Moreover, I do not see ANY pointers in the documentation concerning what steps I might take to progress merely to the point of having a fully functional kernel, much less how to administrate it afterwards, which is what I would expect to be the harder part of this whole process.
I have no clue as to how to fix such an issue or what might have caused it. My only guess would be that one of the options made during "make menuconfig" was incompatible with my encryption, but that would just be a hunch. Can someone suggest an alternative notion or recommendation? I am using standard dmcrypt, no lvm, no truecrypt, no magic wand. Does it occur to anyone that lacking any particular one of the configuration options for the kernel would render the encryption support defunct? If not, does there seem to be a better question I ought to be asking at this point? Frankly, I don't believe that I have asked for much in the way of support, no hand-holding, no kiddie-gloves, not even any pointing out of the obvious. Am I expecting too much from the gresec team, impatiently? At this rate I would not be able to meet my self-appointed deadline for completion of this project, and I am wondering now whether I ought to consider settling for an alternative security program? That would not be my preference, to be sure.
There is nothing terribly complicated about my system, really nothing. I feel a bit frustrated, puzzled and, well, disappointed in that this procedure seems to lack a certain amount of empathy with my condition. Moreover, I do not see ANY pointers in the documentation concerning what steps I might take to progress merely to the point of having a fully functional kernel, much less how to administrate it afterwards, which is what I would expect to be the harder part of this whole process.
You are my hero, today. Thank you for responding to me.