Use MAJOR:MINOR versioning scheme for the gui protocol

[marmarek]

Reported by joanna on 12 Jul 2012 13:11 UTC
MAJOR number should be increased when (and only when) the change of the
GUI protocol requires rebuild of all the gui agents and the gui daemon.

MINOR number should be increased when the change of the GUI protocol
requires only gui daemon and select agents rebuild.

It should be very rare situation when we would need to increase the MAJOR number.

A gui daemon, seeing that it talks with a gui agent of wrong MAJOR number, should display a message to the user informing about the need to upgrade the agent. This should, however, not be required for proper operation with a gui agent with a smaller MINOR number (and the same MAJOR), as the guid.

Of course, guid should always be rebuild to have the highest MINOR number, as otherwise it would refuse to talk with an agent that has a newer MINOR than the guid.

This doesn't present any security risk, because the guid always treats messages from gui agents as untrusted.

Migrated-From: https://wiki.qubes-os.org/ticket/621

[marmarek]

Modified by marmarek on 12 Jul 2012 14:49 UTC

[marmarek]

Modified by marmarek on 12 Jul 2012 14:49 UTC

[marmarek]

Comment by marmarek on 12 Jul 2012 23:51 UTC
http://git.qubes-os.org/gitweb/?p=marmarek/gui.git;a=commit;h=a13fade685dda9942ffd54351d8f2081003dc9af

[marmarek]

Comment by marmarek on 12 Jul 2012 23:51 UTC
http://git.qubes-os.org/gitweb/?p=marmarek/gui.git;a=commit;h=a13fade685dda9942ffd54351d8f2081003dc9af