Re: [Standards] XEP-0016, blocking incoming IQs - interpretation problem

[Bartłomiej Górny]

On 08/05/2020 14:34, Florian Schmaus wrote:

On 5/8/20 12:41 PM, Bartłomiej Górny wrote:

Hello

We have a question, how exactly should a privacy list behave if it is
set up to block all incoming IQs. Namely: should it block all incoming
iqs whatsoever (including iq responses to the user's iq requests sent to
the server, iq pushes from the server etc), or only iq stanzas sent by
other users (entities with non-empty localpart other then the user's own)?


 From xep16:

 -- blocks incoming IQ stanzas

so this means all IQ stanzas, independently of their type.



Thanks for answering. We are not wondering about types of iqs, though, 
but about senders. If we block iqs from an entity it is quite clear that 
it should block get, set etc. The question is basically, how to 
interpret example 44. Should a global block on iqs block stanzas from 
other users only, or from all entities - users, servers, my server, my 
server account?


BG




Whether or not if this is sensible is another question

Clients wishing to perform an IQ request could switch to a temporary
privacy list (or modifying the active list) prior sending the IQ request
which allows IQs from the remote entity for the time of the request.

- Florian



___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___



--


Code Sync & Erlang Solutions Conferences 



*
*

Code BEAM 
Lite ITA - Bologna: Rescheduled


Code BEAM STO - Stockholm: Rescheduled


ElixirConf EU - Warsaw: 7-8 October 2020

Code Mesh - London: 5-6 November 
2020


*
*

Erlang Solutions cares about your data and privacy; please find 
all details about the basis for communicating with you and the way we 
process your data in our Privacy Policy 
. You can update your 
email preferences or opt-out from receiving Marketing emails here 
.


___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

[Standards] XEP-0016, blocking incoming IQs - interpretation problem

[Bartłomiej Górny]

Hello

We have a question, how exactly should a privacy list behave if it is 
set up to block all incoming IQs. Namely: should it block all incoming 
iqs whatsoever (including iq responses to the user's iq requests sent to 
the server, iq pushes from the server etc), or only iq stanzas sent by 
other users (entities with non-empty localpart other then the user's own)?


Thanks in advance
Bartek Górny

--


Code Sync & Erlang Solutions Conferences 



*
*

Code BEAM 
Lite ITA - Bologna: Rescheduled


Code BEAM STO - Stockholm: Rescheduled


ElixirConf EU - Warsaw: 7-8 October 2020

Code Mesh - London: 5-6 November 
2020


*
*

Erlang Solutions cares about your data and privacy; please find 
all details about the basis for communicating with you and the way we 
process your data in our Privacy Policy 
. You can update your 
email preferences or opt-out from receiving Marketing emails here 
.


___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

Re: [Standards] XEP-0016, blocking incoming IQs - interpretation problem

[Florian Schmaus]

On 5/8/20 2:55 PM, Bartłomiej Górny wrote:
> On 08/05/2020 14:34, Florian Schmaus wrote:
>> On 5/8/20 12:41 PM, Bartłomiej Górny wrote:
>>> Hello
>>>
>>> We have a question, how exactly should a privacy list behave if it is
>>> set up to block all incoming IQs. Namely: should it block all incoming
>>> iqs whatsoever (including iq responses to the user's iq requests sent to
>>> the server, iq pushes from the server etc), or only iq stanzas sent by
>>> other users (entities with non-empty localpart other then the user's
>>> own)?
>>
>>  From xep16:
>>
>>  -- blocks incoming IQ stanzas
>>
>> so this means all IQ stanzas, independently of their type.
> 
> 
> Thanks for answering. We are not wondering about types of iqs, though,
> but about senders. If we block iqs from an entity it is quite clear that
> it should block get, set etc. The question is basically, how to
> interpret example 44. Should a global block on iqs block stanzas from
> other users only, or from all entities - users, servers, my server, my
> server account?

Ahh, yes, the dreaded example 44.

Strictly following the XEP would mean that you will not even get IQ
responses from any subsequent privacy-list related IQ request. Or any
other IQ from the service.

I personally think that servers implementing xep16 should *always* allow
stanzas from themself (not sure if this includes internal components
though, I think not). That is why I have created

https://issues.igniterealtime.org/browse/OF-724

6 years ago.

I'd love to get that clarification into xep16 too. But someone™ needs to
do it.

- Flroain




signature.asc
Description: OpenPGP digital signature
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

Re: [Standards] XEP-0016, blocking incoming IQs - interpretation problem

[Florian Schmaus]

On 5/8/20 12:41 PM, Bartłomiej Górny wrote:
> Hello
> 
> We have a question, how exactly should a privacy list behave if it is
> set up to block all incoming IQs. Namely: should it block all incoming
> iqs whatsoever (including iq responses to the user's iq requests sent to
> the server, iq pushes from the server etc), or only iq stanzas sent by
> other users (entities with non-empty localpart other then the user's own)?

From xep16:

 -- blocks incoming IQ stanzas

so this means all IQ stanzas, independently of their type.

Whether or not if this is sensible is another question.

Clients wishing to perform an IQ request could switch to a temporary
privacy list (or modifying the active list) prior sending the IQ request
which allows IQs from the remote entity for the time of the request.

- Florian




signature.asc
Description: OpenPGP digital signature
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___