Sometimes you don't get to observe random numbers as 32 bit integers. Sometimes they may be used to create a string such as random passwords for reset functionality. In this case, we'd like to be able to support some kind of user-supplied "mangling" function, perhaps in python script form that captures the process by which the program takes in a random number and creates something out of it. Untwister would then use this function internally to convert its computed random numbers into the format that the observed values are in.
How exactly this would work is not clear to me right now, but that's the idea.
State inference mode may not be possible with this, unless there's a strict 1:1 mapping for the mangling function and not a lossy process.
Sometimes you don't get to observe random numbers as 32 bit integers. Sometimes they may be used to create a string such as random passwords for reset functionality. In this case, we'd like to be able to support some kind of user-supplied "mangling" function, perhaps in python script form that captures the process by which the program takes in a random number and creates something out of it. Untwister would then use this function internally to convert its computed random numbers into the format that the observed values are in.
How exactly this would work is not clear to me right now, but that's the idea.
State inference mode may not be possible with this, unless there's a strict 1:1 mapping for the mangling function and not a lossy process.