Skip to content

Conversation

@zapek
Copy link
Contributor

@zapek zapek commented Feb 7, 2026

During GXS syncing, the group's service string was transferred. This would possibly overwrite locally computed data.

During GXS syncing, the group's service string was transferred. This would possibly overwrite locally computed data.
@zapek
Copy link
Contributor Author

zapek commented Feb 7, 2026

AFAIK, GXS Identity uses service strings to store PGP validation and reputation scores. GXS Channels uses it to store if a channel has auto file download activated. Those locally computed data might get overwritten by a peer during syncing.

@csoler
Copy link
Contributor

csoler commented Feb 7, 2026

Good catch! A side effect of your PR is that the service string is not locally saved either. Isn't it a problem?

@zapek
Copy link
Contributor Author

zapek commented Feb 8, 2026

Well, I would need your confirmation there but I believe the serialise() and deserialise() part of rsgxsdata.cc only applies to GXS transfers. The actual saving of the group is done by the RS_SERIAL_PROCESS() macros in rsgxsifacetypes.h (and it does handle mServiceString).

@csoler
Copy link
Contributor

csoler commented Feb 8, 2026

Actually the saving is done in storeGroup().

@csoler csoler merged commit 837bdb7 into RetroShare:master Feb 8, 2026
1 check failed
@zapek zapek deleted the fix_service_string_overwrite branch February 8, 2026 20:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants