You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While the installation of the certificate works and the certificate file is present in system/etc/security/cacerts it shows no effect and is not trusted. This means that without the certificate pinning bypass, no traffic can be collected.
The text was updated successfully, but these errors were encountered:
The problem seems to be connected to the file permissions. httptoolkit, where we found the tempfs workaround we are currently using, updates the file permissions and SELinux permissions of the cert folder.
When checking the permissions of our certificate, I noticed that we don’t even set any of the file permissions correctly:
My guess this is a regression from #94, because before we pushed the file as root instead of via su -c, which should have at least set the owner correctly.
While the installation of the certificate works and the certificate file is present in
system/etc/security/cacerts
it shows no effect and is not trusted. This means that without the certificate pinning bypass, no traffic can be collected.The text was updated successfully, but these errors were encountered: