Gajim wrongly sends senders=both in Jingle FT session-accept
When Gajim receives an inbound jingle file transfer like
<iq id='iq1' type='set' to=paul@example.com/res>
<jingle xmlns='urn:xmpp:jingle:1' action='session-initiate' initiator=anna@example.com/res' sid='abc123'>
<content creator='initiator' name='a-file-offer' senders='initiator'>
[description]
[transport]
</content>
</jingle>
</iq>
it answers with
<iq id='iq2' type='set' to=anna@example.com/res>
<jingle xmlns='urn:xmpp:jingle:1' action='session-accept' initiator=anna@example.com/res' sid='abc123'>
<content creator='initiator' name='a-file-offer' senders='both'>
[description]
[transport]
</content>
</jingle>
</iq>
The relevant bit is that Gajim wrongly switches senders='initiator'
to senders='both'
. The value should remain senders='initiator'
. In this context, senders='both'
doesn't make sense and just changing senders
also isn't allowed at that point. This causes issues with clients that verify that the "senders" field is the one they expect.