mirror of
https://github.com/nextcloud/twofactor_gateway.git
synced 2026-04-25 09:05:55 +03:00
[GH-ISSUE #46] Threema Gateway support #17
Labels
No labels
0. to triage
1. to develop
3. to review
blocked
bug
discussion
duplicate
enhancement
enhancement
gateway:signal
gateway:signal
gateway:signal
gateway:sms
gateway:telegram
hacktoberfest
help wanted
invalid
needs info
php
pull-request
question
technical debt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/twofactor_gateway-nextcloud#17
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rugk on GitHub (Apr 11, 2018).
Original GitHub issue: https://github.com/nextcloud/twofactor_gateway/issues/46
It would be great if you could – in addition to Telegram – also support Threema.
In contrast to all other methods here (AFAIK), it is at least end-to-end-encrypted. 😃
For more information, see https://gateway.threema.ch/.
@ChristophWurst commented on GitHub (Apr 11, 2018):
Pull requests for a Threema integration are very welcome. I don't use it right now and I'd also favor FLOSS over a proprietary messenger.
Such gateways are great, but usually messages get encrypted at the gateways, allowing it to read all the sensitive information. That's not end-to-end encrypted 😉
@rugk commented on GitHub (Apr 11, 2018):
Threema offers both. Their SDK actually does real e2e crypto. In contrast to Telegram, BTW, but you can forget their crypto anyway. But let's not get off-topic here… 😃
@simonspa commented on GitHub (Aug 22, 2018):
Looking at the Telegram gateway implementation here, and comparing with the SDK snippets on the Threema Gateway website, this looks fairly simple (compare section "Send a Text Message to a Threema-ID (End-To-End Mode)" on the PHP SDK page)
However, I don't fully understand the mechanisms of retrieving information about the user. Would the ID (and thus the public key) be stored in the user profile somehow? How could this be retrieved then?
@rugk commented on GitHub (Aug 22, 2018):
Of course, the user somehow has to provide the Threema ID. This may be done when settingupthe 2fa method, like with TOTP, or, as you said, in the user's profile.
@rugk commented on GitHub (Nov 20, 2018):
BTW the hardest part may be just that libsodium is required for the server admin to install. 😄
@WhiteBahamut commented on GitHub (Nov 4, 2020):
Not sure if the Threema GW needs to be supported, but Threema just described their approach to multi-device capabilities. Maybe Talk can "just" be another Threema Device :)
https://threema.ch/en/blog
Use Threema quite a lot and it would be awsome to have it integrated into Talk, so I can mainly use Talk
@rugk commented on GitHub (Nov 4, 2020):
@WhiteBahamut Mind in which repo you are commenting. This repo is https://github.com/nextcloud/twofactor_gateway, i.e. this is about integrating Threema as an 2FA provider – not as anything related to "Talk".