Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
look like there is something wrong about your SSL. Was it working before? If so, have you done something recently that could have caused this? Update or some change in config files? Be very careful with SSL, if you get rooted, it will most likely be the first thing that will broke.
In any case, I think reinstaling Open SSL package of your distro would probably fic this... but make sure the broke haven't been caused by an attack against your server.
Distribution: Debian -- If I can ever get it configured
Posts: 2
Rep:
Executable Stack problem
I'm in the middle of the same problem. But I found a probable answer by googling on the Debian site. A "recent" -- by Debian standards -- update to glibc causes this. It is because the critical library requires kernel support that it doesn't check for during installation.
For Debian, the solution is a kernel from 2.4.27/"Sarge" -- the "Woody" kernels don't support whatever the library needs to do. I suppose, alternatively, you can drop back to a glibc that predates this function. But dam' near everything uses that library, so downgrading it is a seriously risky step.
Now, if someone could point out a way to have a different glibc depending on the kernel (uname -r). I mess about a lot with symlinks for different kernels, but I'm not sure I want to risk a broken glibc again -- I'm just recovering from my last fiasco.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.