Minor cleanup to Ghidra Server

This commit is contained in:
ghidra1 2019-09-06 17:28:50 -04:00
parent 309254d15f
commit e17797f4dc
2 changed files with 8 additions and 3 deletions

View File

@ -40,9 +40,14 @@ example_ad_ldap_auth {
// JPAM is not included in the Ghidra distro. See http://jpam.sourceforge.net/.
//
// Additionally:
// the libjpam.so native library needs to be copied to your Ghidra/Features/GhidraServer/os/linux64 directory.
// the JPAM-x.y.jar java library needs to be copied to your Ghidra/Features/GhidraServer/lib directory.
// The libjpam.so native library needs to be copied to your Ghidra/Features/GhidraServer/os/linux64 directory.
// The JPAM-x.y.jar java library needs to be copied to your Ghidra/Features/GhidraServer/lib directory,
// and the following entries need to be added to your server/server.conf file:
// wrapper.java.classpath.PAM=${ghidra_home}/Ghidra/Features/GhidraServer/lib/JPam-x.y.jar
// wrapper.java.classpath.PAM2=${ghidra_home}/Ghidra/Features/GhidraServer/data/yajsw-stable-12.12/lib/core/commons/commons-logging-1.1.jar
//
// NOTE: you may need to run GhidraServer as root when using PAM authentication, depending on your configuration.
//
example_jpam_auth {
net.sf.jpam.jaas.JpamLoginModule REQUIRED
// The serviceName parameter controls which PAM service Ghidra will try to authenticate against.