Engine selection looks too much at name of file

Bug #1870924 reported by Peter Haahr Taankvist
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
TAPAAL
Confirmed
Low
Unassigned

Bug Description

When selecting engine it will check that the name corresponds to the engine e.g. when choosing verifytapn the name must be verifytapn64.

If you rename verifytapn64 to something else it will not recognize it. However, if you then rename verifypn64 to verifytapn64 and select the now renamed verifypn64 as your verifytapn it will recognize that it is verifypn and not verifytapn. So it seems like we do not need this name check.

Changed in tapaal:
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
Kenneth Yrke Jørgensen (yrke) wrote :

In the ideal world we would sign the executables and check the signature before trying to run it, the current implementations could be considered a security issue. But that's also why the filename check exists, so we don't call a random executable. (Although it does not solve the security issue, it prevents accidental running a wrong file)

Revision history for this message
Jiri Srba (srba) wrote :

Yes, I agree on this with Kenneth. Normally the user should not be concerned with this, as it is setup automatically.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.