Package Details: ftkimager 3.1.1-3

Git Clone URL: https://aur.archlinux.org/ftkimager.git (read-only, click to copy)
Package Base: ftkimager
Description: Closed source binary CLI forensic imaging software by Access Data
Upstream URL: https://www.exterro.com/ftk-product-downloads/fedora-and-red-hat-version-x64-3-1-1
Licenses: Commercial
Submitter: daschu117
Maintainer: jskier
Last Packager: jskier
Votes: 9
Popularity: 0.020907
First Submitted: 2010-12-16 00:41 (UTC)
Last Updated: 2023-05-01 14:16 (UTC)

Latest Comments

« First ‹ Previous 1 2

daschu117 commented on 2011-02-24 02:46 (UTC)

Here's a bin32-ftkimager. Hope it helps. http://aur.archlinux.org/packages.php?ID=46838

ptchinster commented on 2011-02-24 02:20 (UTC)

"Actually, I think that the correct way to handle 64bit would be a bin32-ftkimager package since this is a 32bit binary and nothing is going to change that." Agreed

daschu117 commented on 2011-02-24 02:01 (UTC)

Actually, I think that the correct way to handle 64bit would be a bin32-ftkimager package since this is a 32bit binary and nothing is going to change that.

daschu117 commented on 2011-02-24 01:51 (UTC)

Simply changing that isn't sufficient. Because its a 32bit binary, it needs a different dependency from a different repository to function at all. On top of that, the PKGBUILD currently creates an extra openssl symlink, which it shouldn't because in the end, the openssl package should manage its own symlinks. The PKGBUILD is currently broken in that regard because it does something that it shouldn't have a right to do. I didn't feel like updating it to work for 64bit because that would just continue the brokenness. If I update the PKGBUILD for 64bit, I'll make the dependencies correct, but I don't think that the package should be making the symlink if the first place, so I won't go through the trouble of doing nasty things. I'd leave it as a note in the .install file. The other option is to use the Debian version of ftkimager, but that requires openssl 0.9.8, which is another AUR package. All that being said, I'm welcome to any suggestions you might have as to how to make this package work properly without being dirty.

ptchinster commented on 2011-02-24 01:42 (UTC)

"To get this to work on x86_64, you'll need to multilib/lib32-openssl, then add a symlink so that the library name that ftk expects can be found: ln -s /usr/lib32/libcrypto.so.1.0.0 /usr/lib32/libcrypto.so.10 " ^^^This is why we have PKGBUILDS with an architecture variable.

daschu117 commented on 2011-02-24 01:41 (UTC)

FTK Imager 2.9.0 is the latest version for linux command line and is NOT out of date. 3.0 is Windows only. To get this to work on x86_64, you'll need to multilib/lib32-openssl, then add a symlink so that the library name that ftk expects can be found: ln -s /usr/lib32/libcrypto.so.1.0.0 /usr/lib32/libcrypto.so.10

ptchinster commented on 2011-02-22 20:29 (UTC)

(on a 64 bit system) [ptchinster@shewolf ~]$ /usr/bin/ftkimager /usr/bin/ftkimager: error while loading shared libraries: libcrypto.so.10: cannot open shared object file: No such file or directory

« First ‹ Previous 1 2