How do you find it?

I only found this but I don't think it's the right one.

https://talk.maemo.org/showthread.php?p=1557768

You can also start by sharing a screenshot or picture of your current certificate state, after launching CERMASTR.

I don't know how to put an image in here, so I just put it in a google doc:
https://docs.google.com/document/d/1uVDpvFtzsHdXEEpmNFWRfH69vduk3czw0eV5Ravh-uU/edit?tab=t.0

I can see it now, thanks.

Hi!
I'm possibly necroing this post, idk if that's a thing here.

In any case, I have the same problem as before, and my certificate values are... similar, but still different enough for me to ask for help (>50% diff).

Here is a picture of my current cert:


A few lines aren't there, and a new `0C0` field appeared. The topmost line fully matches though.

Can I just follow the procedure like this or should I do something else?

I hope I'm not bothering anyone with unwanted extra work here...

Yeah one of mine had a similar state.
If you can just create a parent field then create the python field inside then you're good. It doesn't need to be at the top, apparently.

I seem to be affected by the corruption mentioned earlier - if I make a new field for python and set it it sets it to `50 00 00 01 FF FF FF FF [...]`. I am using the latest version of CERMASTR as far as I know (I downloaded it last week).

Apart from that, if I try to make a parent field, I cannot set it's size to match the size in the steps (04), it jumps from 02 to 06. Pressing - sets the value to FF, and if then pressed again, freezes the calculator.
Someone else allowed me to look at the cert on their calc, and trying to set the size of the parent field to their value (1B) also isn't possible, given it skips from 1A right to 1F.

Any idea on what to try next?

You might have to do it step by step, creating the new parent field at the bottom, save/flash and quit+reopen.
Then try creating the new python field below, with its value.
Then increase the parent field size by one.

It's a bit messy when the certificate is not in its "normal" state, but it's still possible to fix it little by little.

That did it!

Quick note (may be usefull for future users, idk): after making the 043 field and setting size to 01, pressed <right> until in the hex editor, entered P manually there. Then told it to flash without exiting the field. When reopening CERMASTR, the field now contains a lot of FF FF FF [etc], I ignored it and just set the parent field (033) size to 1B.
Then opening python works.

Thanks for the help!