view docker/backend-dev/session.conf @ 4231:e11b13418ba6

plugin XEP-0353, XEP-0234, jingle: WebRTC data channel signaling implementation: Implement XEP-0343: Signaling WebRTC Data Channels in Jingle. The current version of the XEP (0.3.1) has no implementation and contains some flaws. After discussing this on xsf@, Daniel (from Conversations) mentioned that they had a sprint with Larma (from Dino) to work on another version and provided me with this link: https://gist.github.com/iNPUTmice/6c56f3e948cca517c5fb129016d99e74 . I have used it for my implementation. This implementation reuses work done on Jingle A/V call (notably XEP-0176 and XEP-0167 plugins), with adaptations. When used, XEP-0234 will not handle the file itself as it normally does. This is because WebRTC has several implementations (browser for web interface, GStreamer for others), and file/data must be handled directly by the frontend. This is particularly important for web frontends, as the file is not sent from the backend but from the end-user's browser device. Among the changes, there are: - XEP-0343 implementation. - `file_send` bridge method now use serialised dict as output. - New `BaseTransportHandler.is_usable` method which get content data and returns a boolean (default to `True`) to tell if this transport can actually be used in this context (when we are initiator). Used in webRTC case to see if call data are available. - Support of `application` media type, and everything necessary to handle data channels. - Better confirmation message, with file name, size and description when available. - When file is accepted in preflight, it is specified in following `action_new` signal for actual file transfer. This way, frontend can avoid the display or 2 confirmation messages. - XEP-0166: when not specified, default `content` name is now its index number instead of a UUID. This follows the behaviour of browsers. - XEP-0353: better handling of events such as call taken by another device. - various other updates. rel 441
author Goffi <goffi@goffi.org>
date Sat, 06 Apr 2024 12:57:23 +0200
parents fd3fe346a14a
children
line wrap: on
line source

<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-Bus Bus Configuration 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
	<type>session</type>
	<keep_umask/>
	<listen>unix:path=/home/libervia/.local/share/dbus_socket</listen>
	<listen>tcp:host=localhost,bind=*,port=55555,family=ipv4</listen>
	<auth>ANONYMOUS</auth>
	<allow_anonymous/>
	<standard_session_servicedirs />
	<policy context="default">
		<allow send_destination="*" eavesdrop="true"/>
		<allow eavesdrop="true"/>
		<allow own="*"/>
	</policy>
	<include if_selinux_enabled="yes" selinux_root_relative="yes">contexts/dbus_contexts</include>
	<limit name="max_incoming_bytes">1000000000</limit>
	<limit name="max_incoming_unix_fds">250000000</limit>
	<limit name="max_outgoing_bytes">1000000000</limit>
	<limit name="max_outgoing_unix_fds">250000000</limit>
	<limit name="max_message_size">1000000000</limit>
	<limit name="service_start_timeout">120000</limit>
	<limit name="auth_timeout">240000</limit>
	<limit name="pending_fd_timeout">150000</limit>
	<limit name="max_completed_connections">100000</limit>
	<limit name="max_incomplete_connections">10000</limit>
	<limit name="max_connections_per_user">100000</limit>
	<limit name="max_pending_service_starts">10000</limit>
	<limit name="max_names_per_connection">50000</limit>
	<limit name="max_match_rules_per_connection">50000</limit>
	<limit name="max_replies_per_connection">50000</limit>
</busconfig>