Jolla C and qcrypto

[fuchsmich]

As requested in the README:

$ find /lib/modules/ -name qcrypto.ko

returns nothing.

[Olf0]

Thank you!

The thing is, I expected a positive result from looking at a l500d kernel tree for SailfishOS somewhere here at Github.
Can you please provide the output of ssu s (as a user) sans device UID.

Maybe the access rights for the kernel module directories were tightened, hence can you please retry the find /lib/modules/ -name qcrypto.ko as root.
If positive, then it is also helpful to know if a /sbin/modprobe qcrypto succeeds (in addition to the already mentioned output of rpm -qf $(find /lib/modules/ -name qcrypto.ko) ).

[Olf0]

Or (desperate) does devel-su find /lib/modules/ -name "*crypt*" yield anything?

P.S.: This one should provide (at least) one hit, for ecryptfs.ko.

[Olf0]

Or (even more desperate) a devel-su find / -name "*crypt*.ko"?

P.S.: This should find ecryptfs.ko, and every hit might be displayed twice (via a bind mount), if AlienDalvik is running.

[fuchsmich]

[root@jollac nemo]# find / -name "*crypt*.ko"
find: /sys/kernel/slab/L2TP/IPv6: No such file or directory
find: /sys/kernel/slab/L2TP/IP: No such file or directory
/lib/modules/3.10.49+0.0.95/ecryptfs.ko

[Olf0]

Thank you, so the Jolla C must use the "regular edition" of crypto-sdcard.

Now I assume again, that only on the Jolla 1 SailfishOS provides the qcrypto.ko.

Background
Qualcomm's "Crypto Engine" (basically a cryptographic accelerator) was introduced to their ARMv7-A based (i.e., 32 bit) SoCs (regardless of the specific CPU core used) around 2010. The SoC in the J1 has v2 of that engine, the one in the l500d has v3. (Side note: This crypto-engine does not seem to be present in any Qualcomm ARMv8-A (64bit) SoC.)
This is why I assumed that the low-level software mechanisms are the same (and AFAICS they are under Android).