Linux executable is throwing a tantrum.
My situation is that I cannot execute (what appears to be) a valid program. The platform is Ubuntu 20.04, on Hyper-V (Windows 10 bld 1903). I have installed Kerberos, seemingly by-the-book: root:root owner, 755 file permissions. The klinit object is binary, execution is attempted with both "klist" and "/.klist", results is "no such file or directory". Access is attempted from the default directory.
The installation script for Windows from the same source runs without error.
Any insight is appreciated.
2020-06-18_13-33-15.png
The installation script for Windows from the same source runs without error.
Any insight is appreciated.
2020-06-18_13-33-15.png
ASKER
Hi Arnold, klist returns "bash: /usr/local/krb5/bin/klist: No such file or directory"l
ldd klist is interesting, "not a dynamic executable"
I don't follow your last paragraph, my bad. If this were successful then kinit would prompt me for my principal name, domain, password, and Yubikey code, returning a ticket. With the ticket I can ssh/putty into a remote server with GSSAPI credentials.
Your reply prompted me to start searching for the string "cannot execute binary file". One site, https://www.unix.com/red-hat/247751-cannot-execute-binary-file.html, led me to recheck that the machine is (uname) is x86_64. As I recall, the binaries came from a 32-bit source. I'm thinking to remove the krb5 directories and to reinstall from the 64-bit source.
ldd klist is interesting, "not a dynamic executable"
I don't follow your last paragraph, my bad. If this were successful then kinit would prompt me for my principal name, domain, password, and Yubikey code, returning a ticket. With the ticket I can ssh/putty into a remote server with GSSAPI credentials.
Your reply prompted me to start searching for the string "cannot execute binary file". One site, https://www.unix.com/red-hat/247751-cannot-execute-binary-file.html, led me to recheck that the machine is (uname) is x86_64. As I recall, the binaries came from a 32-bit source. I'm thinking to remove the krb5 directories and to reinstall from the 64-bit source.
Did you install Kerberos from the Ubuntu install kit, or from the source kit?
If it was built from the source kit then it's very likely that it won't work at all, because it builds into directories other than the places that the Ubuntu executables expect them.
If it was built from the source kit then it's very likely that it won't work at all, because it builds into directories other than the places that the Ubuntu executables expect them.
Since you said, "The installation script for Windows from the same source runs without error."
Likely the problem is you used an "installation script", which will almost surely fail.
You should have installed one of these Ubuntu Focal packages, to have klinit available...
Suggestion: Remove whatever you installed. Install one of the 2x packages above. Retest.
Likely the problem is you used an "installation script", which will almost surely fail.
You should have installed one of these Ubuntu Focal packages, to have klinit available...
net17 # klinit
Command 'klinit' not found, did you mean:
command 'kinit' from deb heimdal-clients (7.7.0+dfsg-1ubuntu1)
command 'kinit' from deb krb5-user (1.17-6ubuntu4)
Try: apt install <deb name>Suggestion: Remove whatever you installed. Install one of the 2x packages above. Retest.
Is SELinux in enforcing mode?... Then programs may not be allowed to access various protected resources.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ldd klist what happens?
/.kilst means at the root folder find a file .klist
ldd is a way to make sure all libraries that the application may rely on are installed.
file klist will tell you whether it is a binary or a script file
klinit should be kinit.
Did you configure the authentication to tie into the AD?
usually kerbeerous is setup after the system is joined to the domain net join ads ...
or use the GUI tools to do the same.