With displays like these, it’s either parallel or SPI. Try to find a chip in the kapton circuit, that is the actual display driver.
Try to find out the FPC pinout, there should be two pins for backlight, find out of there’s any GND, etc… my gut says this is some kind of SPI based controller, 24 pins is too little for a parallel one.
It’s not like this is an oopsie bug, this is a major vuln knowingly indroduced by the dev, and their response is somewhat shocking.
I recommend plenty of alpha/beta software to people, of course with the disclaimer that it’s not done yet, but sure, feel free to not trust me at all, stranger :)
For the record, I did not encounter major bugs in my ~1 month of usage.
I was a user, I even recommended it to people, but since the discovery of this issue I feel uneasy to continue using/recommending it. That dev response is appalling.
There’s SwiftFin, but it’s been a while from the last update (iOS app was updated recently though) and there’s a number of issues. It’s usable though (I’m using it).
The only alternative I know of that goes close to what FreeIPA does (minus the cert part) is kanidm. It does:
oauth2
ssh key distribution
RADIUS
PAM/SSSD
LDAP
I just noticed they have a beta for multimaster replication, which is nice.
I use it at home. Note, though, that it does not do any hand-holding, and all configuration is done through CLI. Also note, there are docs for the stable or dev branch and there sometimes are big differences between the two.
I mean, it is a bit rough, they’re not at 1.0 yet, also: are you looking at the stable or latest docs? That may be the reason the commands do not match with the docs.
With displays like these, it’s either parallel or SPI. Try to find a chip in the kapton circuit, that is the actual display driver.
Try to find out the FPC pinout, there should be two pins for backlight, find out of there’s any GND, etc… my gut says this is some kind of SPI based controller, 24 pins is too little for a parallel one.