We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The example lemma for injective authentication (https://github.com/tamarin-prover/manual/blame/59525bd2c117da7acf21e58412ea209d7bc02522/src/007_property-specification.md#L783) uses upper case "A" and "B" as the two agents, but all the other authentication lemmas use the lower case "a" and "b". This becomes super confusing because the description specifically mentions that "a"/"b" are the agents, and "A"/"B" are the roles of those agents, which (as far as I understand) is not the intention.
I'm happy to make this change myself, I'd just like a vague confirmation that it wasn't the intention to be referring to the role in the lemma.
The text was updated successfully, but these errors were encountered:
This is indeed the intention, and a pull request reflecting this change would be very welcome.
Sorry, something went wrong.
No branches or pull requests
The example lemma for injective authentication (https://github.com/tamarin-prover/manual/blame/59525bd2c117da7acf21e58412ea209d7bc02522/src/007_property-specification.md#L783) uses upper case "A" and "B" as the two agents, but all the other authentication lemmas use the lower case "a" and "b". This becomes super confusing because the description specifically mentions that "a"/"b" are the agents, and "A"/"B" are the roles of those agents, which (as far as I understand) is not the intention.
I'm happy to make this change myself, I'd just like a vague confirmation that it wasn't the intention to be referring to the role in the lemma.
The text was updated successfully, but these errors were encountered: