소스 검색

Use stricter regex in bridges' registration.yaml

I've been thinking of doing before, but haven't.

Now that the Whatsapp bridge does it (since 4797469383),
it makes sense to do it for all other bridges as well.
(Except for the IRC bridge - that one manages most of registration.yaml by itself)
pull/208/head
Slavi Pantaleev 7 년 전
부모
커밋
37c8b96d06
2개의 변경된 파일3개의 추가작업 그리고 3개의 파일을 삭제
  1. +1
    -1
      roles/matrix-bridge-mautrix-facebook/defaults/main.yml
  2. +2
    -2
      roles/matrix-bridge-mautrix-telegram/defaults/main.yml

+ 1
- 1
roles/matrix-bridge-mautrix-facebook/defaults/main.yml 파일 보기

@@ -171,7 +171,7 @@ matrix_mautrix_facebook_registration_yaml: |
namespaces:
users:
- exclusive: true
regex: '@facebook_.+:{{ matrix_mautrix_facebook_homeserver_domain|regex_escape }}'
regex: '^@facebook_.+:{{ matrix_mautrix_facebook_homeserver_domain|regex_escape }}$'
url: {{ matrix_mautrix_facebook_appservice_address }}
sender_localpart: facebookbot
rate_limited: false


+ 2
- 2
roles/matrix-bridge-mautrix-telegram/defaults/main.yml 파일 보기

@@ -367,10 +367,10 @@ matrix_mautrix_telegram_registration_yaml: |
namespaces:
users:
- exclusive: true
regex: '@telegram_.+:{{ matrix_mautrix_telegram_homeserver_domain|regex_escape }}'
regex: '^@telegram_.+:{{ matrix_mautrix_telegram_homeserver_domain|regex_escape }}$'
aliases:
- exclusive: true
regex: '#telegram_.+:{{ matrix_mautrix_telegram_homeserver_domain|regex_escape }}'
regex: '^#telegram_.+:{{ matrix_mautrix_telegram_homeserver_domain|regex_escape }}$'
url: {{ matrix_mautrix_telegram_appservice_address }}
sender_localpart: telegrambot
rate_limited: false


불러오는 중...
취소
저장