本文介绍了Linux功能(setcap)似乎禁用了LD_LIBRARY_PATH的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！
问题描述
我使用LD_LIBRARY_PATH为应用程序设置某个用户库的路径.但是如果我在此应用程序上设置功能
I use LD_LIBRARY_PATH to set the path of a certain user library for an application. But if I set capabilities on this application
sudo setcap CAP_NET_BIND_SERVICE=eip myapplication
然后LD_LIBRARY_PATH似乎被忽略了.当我启动该程序时，Linux抱怨它找不到某个共享库.
then LD_LIBRARY_PATH seems to be ignored. When I launch the program, Linux complains that it cannot find a certain shared library.
我猜想有某种保护措施可以防止具有扩展权限的应用程序被劫持.有解决方法吗?
I guess that there's some kind of protection kicking in, to prevent applications with extended rights from being hijacked. Is there a workaround?
推荐答案
是的，出于安全原因已将其禁用.
Yes, it's disabled for security reasons.
这篇关于Linux功能(setcap)似乎禁用了LD_LIBRARY_PATH的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！