savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-12-06T16:07:11Zhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1033Webview bubble (2 bubbles appear, one for the preview, the other for the link)2021-12-06T16:07:11ZAltonsWebview bubble (2 bubbles appear, one for the preview, the other for the link)## Describe your environment
Please specify the following:
- Ring version: 20210924-01
- Device model: Samsung galaxy core prime
- Android version: 5.0.1 + edit(by @mcallet): common to all android version
- What build you are ...## Describe your environment
Please specify the following:
- Ring version: 20210924-01
- Device model: Samsung galaxy core prime
- Android version: 5.0.1 + edit(by @mcallet): common to all android version
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Open Jami
2. Receive a message with a link, the webview bubbles will appear in the conversation
- Actual result: 2 bubbles appear for one link (unlike the "smooth" experience of jami-qt desktop client.
- Expected result: If we choose to use 2 bubbles, these should be better integrated.
## Additional information
![image](/uploads/d4265bfee3d7996d28bc0439ffae4865/image.png)
![image](/uploads/fc14927d3437c48145f86055ff90721e/image.png)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1030Conversation: scrolling block sent file2022-03-02T21:48:25ZMaxime CalletConversation: scrolling block sent file## Details:
- Ring version: `any`
- Device model: `Samsung T2`
- Android version: `7.0`
- What build you are using: `jami.net | F-droid | Play Store`
## Steps to reproduce:
- Can you reproduce the bug: `at will`
- Steps:
1. I...## Details:
- Ring version: `any`
- Device model: `Samsung T2`
- Android version: `7.0`
- What build you are using: `jami.net | F-droid | Play Store`
## Steps to reproduce:
- Can you reproduce the bug: `at will`
- Steps:
1. In a conversation with sent files
2. Scroll down until you reach a video you sent
3. Then scroll up/down above and below the file preview
4. The preview is now white and can't be accessed
## Actual result:
![Screenshot_20211109-173024](/uploads/1bad59c5b8d42b2fe75e27f9abc538a5/Screenshot_20211109-173024.png)
## Expected result:
The preview should be visible and the file accessible
## Additional informationhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1023Do not reset account informations when linking it from another device2023-06-01T13:15:12ZMaxime CalletDo not reset account informations when linking it from another deviceThis sequence is not useful, user will retrieve his data, thus do not need to reset informations
![Screenshot_20211026_144223_cx.ring_edit_97742123916855](/uploads/5753a464d1bb903bbd1182af26cd27cd/Screenshot_20211026_144223_cx.ring_edit...This sequence is not useful, user will retrieve his data, thus do not need to reset informations
![Screenshot_20211026_144223_cx.ring_edit_97742123916855](/uploads/5753a464d1bb903bbd1182af26cd27cd/Screenshot_20211026_144223_cx.ring_edit_97742123916855.jpg)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1022Changing ringtone turns it to mute until app reset/reinstall2021-10-20T20:22:02Zarkanoid87Changing ringtone turns it to mute until app reset/reinstallI had ringtone working until I changed it to another one from the "Jami Tones" list. I do hear them in preview, but Jami doesn't ring anymore on received call.
I've tried changing multiple times, force stop the app (and service) and rest...I had ringtone working until I changed it to another one from the "Jami Tones" list. I do hear them in preview, but Jami doesn't ring anymore on received call.
I've tried changing multiple times, force stop the app (and service) and restart the phone, but only delete data/reinstall made it ring again.
* Jami version: Maloya - 20211004-01 (Play Store)
* Device model: Samsung Note 10+
* Android version: 11
How to reproduce:
- install Jami
- change ringtone
- receive a callhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/649test/meson.build is outdated2022-03-29T12:28:37ZBruno Paganitest/meson.build is outdatedSince I’ve discovered you now provide meson for building, I’m switching Arch packages to it but I’ve encountered an issue:
```
jami-daemon/test/meson.build:59:0: ERROR: File unitTest/channel/testChannel.cpp does not exist.
```
The file s...Since I’ve discovered you now provide meson for building, I’m switching Arch packages to it but I’ve encountered an issue:
```
jami-daemon/test/meson.build:59:0: ERROR: File unitTest/channel/testChannel.cpp does not exist.
```
The file seems to be gone a while ago, but `test/meson.build` wasn’t updated accordingly. For now, I will just keep tests disabled (they were already, but I thought redoing the package would be a good opportunity to enable them).https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1018Implement (automatic) update check so we could distribute APKs on dl.jami.net2023-06-01T17:42:41ZAmin BandaliImplement (automatic) update check so we could distribute APKs on dl.jami.netThe app should check for new APKs from dl.jami.net periodically, so that users who installed the app from the APKs could be notified of and easily download newer APKs.The app should check for new APKs from dl.jami.net periodically, so that users who installed the app from the APKs could be notified of and easily download newer APKs.Amin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/566URL preview width too small2021-10-12T15:51:57ZlinsuiURL preview width too small## Describe your environment
Please specify the following:
- OS: Ubuntu 21.04
- Jami version: 202110012002
- What build you are using: jami.net
## Steps to reproduce
Note: Better the scenario is, better we will be able to reproduce a...## Describe your environment
Please specify the following:
- OS: Ubuntu 21.04
- Jami version: 202110012002
- What build you are using: jami.net
## Steps to reproduce
Note: Better the scenario is, better we will be able to reproduce and debug.
- Can you reproduce the bug: [at will | occasionally | not at all]
- Steps:
1. recieve a URL
...
- Actual result: When the URL is previewed, the width of the message box will become less than 30% of the chat window.
- Expected result: The previewed URL box should be displayed as other massage.
## Additional information
Screenshots/videos/logs/etc
For retrieving logs, cf [this page](https://git.jami.net/savoirfairelinux/ring-project/wikis/tutorials/Bug-report-guide#logs).https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/640Preference: refuse call when account is busy2021-10-07T14:33:25ZAline Gondim SantosPreference: refuse call when account is busyAline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1323(Feature request) Cache2021-11-22T15:54:49ZhardBSDk(Feature request) CacheImplement a screen for cached media with:
- Cleanup option (with selectable items, such as images, videos, stickers, GIFs).
- Storage usage
- Set where to store cache and saved media (internal/SD card)
![126973468-72fec569-dd59-4485-ae...Implement a screen for cached media with:
- Cleanup option (with selectable items, such as images, videos, stickers, GIFs).
- Storage usage
- Set where to store cache and saved media (internal/SD card)
![126973468-72fec569-dd59-4485-ae2b-9a0668d12a14](/uploads/2e9318c83e2d4a434a774db00e51f11f/126973468-72fec569-dd59-4485-ae2b-9a0668d12a14.png)https://git.jami.net/savoirfairelinux/jami-project/-/issues/1315(Feature request) Context-less audio player2023-01-13T16:41:46ZhardBSDk(Feature request) Context-less audio playerAn internal audio player (like Telegram) where all the audio files from a conversation are put in a playlist with playback options and keeps playing outside of the chat screen (even out of the app).
Code suggestion:
https://github.com...An internal audio player (like Telegram) where all the audio files from a conversation are put in a playlist with playback options and keeps playing outside of the chat screen (even out of the app).
Code suggestion:
https://github.com/DoubleSymmetry/react-native-track-player
https://github.com/jeancsanchez/JcPlayer
https://github.com/yusufcakmak/ExoPlayerSample
https://github.com/HamidrezaAmz/MagicalExoPlayer
![126931017-18ffaee5-c483-422b-94d4-0dfa3b930ec5](/uploads/ccce943abb1fbb6618c8304d5f2305f5/126931017-18ffaee5-c483-422b-94d4-0dfa3b930ec5.jpg)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1012(Feature request) Cache2021-11-25T16:58:44ZhardBSDk(Feature request) Cachehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1323https://git.jami.net/savoirfairelinux/jami-project/-/issues/1323https://git.jami.net/savoirfairelinux/jami-packaging/-/issues/108snap: ibus-pinyin not working correctly with client-qt snap2021-10-04T14:28:26ZAmin Bandalisnap: ibus-pinyin not working correctly with client-qt snapThe ibus-pinyin input method does not work properly with the `jami` client-qt snap.
I've done some investigating, and I'm not sure about the exact cause of the issue. The client-qt snap, much like the client-gnome snap, creates a `deskt...The ibus-pinyin input method does not work properly with the `jami` client-qt snap.
I've done some investigating, and I'm not sure about the exact cause of the issue. The client-qt snap, much like the client-gnome snap, creates a `desktop-launch` script based on snapcraft-desktop-helpers's desktop export, which exports the relevant ibus socket path:
https://github.com/ubuntu/snapcraft-desktop-helpers/blob/ec861254c2a1d2447b2c589446e6cdf04c75c260/common/desktop-exports#L451
https://git.jami.net/savoirfairelinux/jami-project/-/blob/835f5ae66c5ccd97277a6bf8a228b516a79d8b29/packaging/rules/snap/jami/snapcraft.yaml#L187
Ideas and/or help with further investigating and fixing this issue are welcome. :slight_smile:https://git.jami.net/savoirfairelinux/jami-project/-/issues/1312Broken dbus interface2022-01-09T16:55:38ZalzxBroken dbus interfacehello there
I use Jami everyday, as VoIP client on Debian (still on Buster, previous stable version).
In time I even wrote some bash crontab scripts for automating stuff (reliably stopping vlc if there is an incoming call, answering a c...hello there
I use Jami everyday, as VoIP client on Debian (still on Buster, previous stable version).
In time I even wrote some bash crontab scripts for automating stuff (reliably stopping vlc if there is an incoming call, answering a call with a global KDE shortcut, etc). They use `dbus-monitor` and `qdbus`, it's awesome.<br>
**Unfortunately with `20210929` and later versions, the needed dbus interface is broken. I had to revert to `20210916`** to make my scripts work again.
Examples:
- this command
```
dbus-monitor --profile --address "$(tr '\0' '\n' < /proc/$(ps -Ao %p%c | sed '/ksmserver/!d; s/ *\([0-9]*\) *.*/\1/g')/environ | grep DBUS_SESSION_BUS_ADDRESS | cut -d"=" -f2-)" "type='signal',sender='cx.ring.Ring',path='/cx/ring/Ring/CallManager',interface='cx.ring.Ring.CallManager'"
```
monitors the arrival of the signal `incomingCallWithMedia` in a crontab job of mine. Basically, when Jami rings as a phone. Now nothing is returned.
- this command
```
qdbus --bus "$(tr '\0' '\n' < /proc/$(ps -Ao %p%c | sed '/ksmserver/!d; s/ *\([0-9]*\) *.*/\1/g')/environ | grep DBUS_SESSION_BUS_ADDRESS | cut -d"=" -f2-)" --literal cx.ring.Ring /cx/ring/Ring/CallManager cx.ring.Ring.CallManager.accept $(qdbus --bus "$(tr '\0' '\n' < /proc/$(ps -Ao %p%c | sed '/ksmserver/!d; s/ *\([0-9]*\) *.*/\1/g')/environ | grep DBUS_SESSION_BUS_ADDRESS | cut -d"=" -f2-)" --literal cx.ring.Ring /cx/ring/Ring/CallManager cx.ring.Ring.CallManager.getCallList | sed "s/{/{\"number\":/g" | jq -r '.number')
```
answers the current incoming call on a bash script, useful for a global shortcut on the keyboard. Now it does nothing.
- after getting the current account string, e.g. `2**************4` , via the (still working) one-liner
```
jamiidstring="$(qdbus --bus "$(tr '\0' '\n' < /proc/$(ps -Ao %p%c | sed '/ksmserver/!d; s/ *\([0-9]*\) *.*/\1/g')/environ | grep DBUS_SESSION_BUS_ADDRESS | cut -d"=" -f2-)" cx.ring.Ring /cx/ring/Ring/ConfigurationManager cx.ring.Ring.ConfigurationManager.getAccountList)"
```
I can tell if there is a problem connecting to my Asterisk server via the commands
```
qdbus --bus "$(tr '\0' '\n' < /proc/$(ps -Ao %p%c | sed '/ksmserver/!d; s/ *\([0-9]*\) *.*/\1/g')/environ | grep DBUS_SESSION_BUS_ADDRESS | cut -d"=" -f2-)" --literal cx.ring.Ring /cx/ring/Ring/ConfigurationManager cx.ring.Ring.ConfigurationManager.getVolatileAccountDetails $jamiidstring | sed "s/\(\[\|\]\)//g;s/Argument: a{ss} //g;s/ = / : /g" | jq '."Account.registrationCode"'
```
and
```
qdbus --bus "$(tr '\0' '\n' < /proc/$(ps -Ao %p%c | sed '/ksmserver/!d; s/ *\([0-9]*\) *.*/\1/g')/environ | grep DBUS_SESSION_BUS_ADDRESS | cut -d"=" -f2-)" --literal cx.ring.Ring /cx/ring/Ring/ConfigurationManager cx.ring.Ring.ConfigurationManager.getVolatileAccountDetails $jamiidstring | sed "s/\(\[\|\]\)//g;s/Argument: a{ss} //g;s/ = / : /g" | jq '."Account.registrationStatus"' | grep -P "\"REGISTERED"
```
In normal conditions, they return `"200"` and `"REGISTERED"`, now `"0"` and `"UNREGISTERED"` or `"ERROR_GENERIC"`. But I can still make and receive calls without problems.
As a **workaround**, I've installed the previous working version, mentioned above, with
```
mkdir -p /tmp/jamitmp; cd /tmp/jamitmp
cp /var/cache/apt/archives/jami*20210916*.deb .
sudo apt-get remove jami jami-qt jami-libclient jami-daemon
sudo dpkg -i *.deb
sudo apt-mark hold jami jami-qt jami-libclient jami-daemon
cd -;
```
But I won't be able to upgrade to future Jami packages until the dbus interface is fixed.<br>
As a temporary solution is provided, this isn't a high priority bug, but there is clearly some bad regression in the code somewhere.<br>
I'd like to add that these code lines are part of my own personal scripts so normally other humans don't see them otherwise they won't call anymore, which defeats the porpouse of automating Jami-related actions. I'm sorry if they or I appear disturbing in nature.<br>
Thank you for reading, I hope this can be fixed.<br>
Have a nice day Jami devs.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/147SIP Account Registered, but No Audio.2022-12-06T05:34:21ZDiagonSIP Account Registered, but No Audio. iOS v.14.7.1
Jami v.3.20
iPhone SE (Gen.1)
SIP account:
<uname>
<password>
SIP Server: callcentric.com
Port: 5060
Proxy: callcentric.com
Account Status:
Enable Account (enabled)
Auto Registe... iOS v.14.7.1
Jami v.3.20
iPhone SE (Gen.1)
SIP account:
<uname>
<password>
SIP Server: callcentric.com
Port: 5060
Proxy: callcentric.com
Account Status:
Enable Account (enabled)
Auto Register After Expiration. (enabled)
My account is listed as "registered" when I check via callcentric's web interface, but when I call *123 or *86 for voicemail, there is no sound. The seconds timer is running. The speaker icon and the microphone icons do not respond. The only thing I can do is get the keypad or hang up.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/999Incoming call is displayed to user after it has immediately failed (for a few...2023-10-29T19:53:06ZElysIncoming call is displayed to user after it has immediately failed (for a few times) / or you hear the call ringing without viewing any notificationUpdate: You can get the call without any noticiation but you'll hear the ringing forever: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/999#note_45879
Update: https://git.jami.net/savoirfairelinux/jami-client-androi...Update: You can get the call without any noticiation but you'll hear the ringing forever: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/999#note_45879
Update: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/999#note_44908
Always reproduced!
---
using newest version of Jami Android 20221107-01 and Jami 202211101600 Windows 10
I was able to reproduce again (sameuseraccount (Android) -\> sameuseraccount (Windows 10)).
Reproduced if two devices use **different networks AND** if two devices use the **same WLAN**
I think if you make a call useraccount 1 -\> useraccount 2 even if the green dot of your own contact in the contact list on Windows 10 is not visible the Android version will still "remember" the call and as soon as the green dot is visible (on Windows 10) the call will succeed.
EDIT: **Maybe you have to make a call successfully before (Android -\> Windows 10) and then JUST exit Windows 10 to reproduce.**
EDIT: I think I now know why and how it fails?
1. Make a call before you can view the green dot of your contact (?)
2. Make a call shortly before you can view the green dot of your contact (?) / or as soon as you would see the green dot
3. The other peer should receive the call after ten seconds (but you'll never know)?
Sometimes you have to exit Jami (just) on the smartphone a couple of times (over 20 times?) to reproduce?
Just reproduced a couple of times again:
**DISABLE "run in background"**
Steps to reproduce (You actually just have to exit ONE device; NOT BOTH, but I think you have to enable TURN, even if you use the same network) (See: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/999#note_38603)
---
EDIT: I was also able to reproduce **Android -\> Windows 10** (**sameuseraccount -\> sameuseraccount**); different network
(The Windows 10 user and the Android user have themselves already in the contact list)
Steps to reproduce:
1. Android: Open Jami and keep Jami running (more than 30 seconds)
2. Now the Windows 10 user opens Jami
3. As soon as the Windows 10 user opens Jami, (BEFORE the green dot of the Android user is visible on Windows 10) the Android user makes one call (Android -\> Windows 10), quickly a second call and maybe you also need a third call - they will all immediately fail
4. Now wait for a few seconds or even longer (nobody does anything; meanwhile the Windows 10 views the green dot of the Android user)
5. The Windows 10 user will receive a call (but the Android user will never notice)
I think you can't reproduce if the green dot is not gone- for example if just the Windows 10 user exits Jami but as soon as he opens Jami again the green dot is already there? In that case I wasn't able to reproduce I think ...
---
**Android \<-\> Android**
1. Open Jami and quickly make a first call (maybe even before I can see the green dot ?? (Can't tell because of issue https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/994) - it will immediately fail
2. Now after a few seconds (or even just one second) make the second call - it will immediately fail
3. Now wait
4. Now the Android tablet will receive a call after 10 seconds or more (but the smartphone user will never be able to view the call)
I had a few possibilities:
- Sometimes you don't reproduce?
- Sometimes the other device just gets one call (2 calls failed)
- Sometimes the other device gets both two calls (2 calls failed)
- Sometimes you need to make a third call (after a few seconds) and the other device will receive the third call AND the second call
---
Option B:
Another option how to reproduce this issue:
EDIT: I think I was even able to reproduce even if you make a call after you can view the green dot of the Android contact but BEFORE the green dot of your own account refreshes again.
1. Just open Jami on Android (never exit; keep Jami running at least 30 seconds; Maybe you've already closed Jami on Windows 10)
2. Now the Windows 10 user opens Jami
3. Make a call Android -\> Windows 10 (before the Windows 10 user can view the green dot of the Android contact): It will immediately fail
4. Make a second call Android -\> Windows 10 (before the Windows 10 user can view the green dot of the Android contact): It will try to connect; However (just) the Android user now stops the call ("connecting" \[although this time it might would work\])
5. Now the Android user makes another call - it will immediately fail (again)
6. Maybe the Android user makes again another call - immediately fail (Sometimes it it will show "connecting" again and the call might successfully work)
7. Maybe all peers need to wait a few seconds
8. Now just the Windows 10 user will receive a call - the Android user will never noticehttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/998"Start Jami on startup" and "Run in background" do not work like expected2021-09-29T18:45:50Zvstoykovbg"Start Jami on startup" and "Run in background" do not work like expected## Steps to reproduce
- Steps:
1. Turn off "Start Jami on startup" and "Run in background"
2. Reboot phone
3. Do not open Jami manually
4. Send message from another device
- Actual result: The message is received.
- Expected re...## Steps to reproduce
- Steps:
1. Turn off "Start Jami on startup" and "Run in background"
2. Reboot phone
3. Do not open Jami manually
4. Send message from another device
- Actual result: The message is received.
- Expected result: The message is not received.
I am expecting Jami to listen for messages only when it's running in the background or it's open.
Also the existence of the two options is confusing:
1. Does Jami listen to messages when "Start Jami on startup" is off and "Run in background" is on (and the app is not manually started)?
2. Does Jami listen to messages when "Start Jami on startup" is on and "Run in background" is off (and the app is not manually started)?
Jami version: Maloya - 20210924-01
Android version: 9
![Screenshot_20210929-203330](/uploads/99cbc71559a584906ec28a35d984ded1/Screenshot_20210929-203330.jpg)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/543Windows beta installer needs user to click Ignore to finish2022-09-07T14:35:20ZovariWindows beta installer needs user to click Ignore to finishWhen installing Jami beta for Windows, the person said that Windows had a dialog which stated something like "Can't update file as it is in use." with the options `Retry`, `Ignore` and `Cancel`.
`Retry` didn't work so they pressed `Igno...When installing Jami beta for Windows, the person said that Windows had a dialog which stated something like "Can't update file as it is in use." with the options `Retry`, `Ignore` and `Cancel`.
`Retry` didn't work so they pressed `Ignore`. Once `Ignore` was pressed, Jami installed; however, this doesn't seem very wise.
We don't have any devices with Windows operating systems; hence, we couldn't reproduce their situation.
1. Are you aware of any programs that should be disabled closed when installing Jami? For example, Windows Defender?
When Jami was installed on there computer Windows Defender caused some problems, and the stated that they allowed the Jami program.
When we made a call, they couldn't hear us and we couldn't hear them.
In their Jami program, they clicked `Open settings`, `Audio/Video` tab, and they said the volume meter for the microphone didn't move and there was no option in the `Microphone` drop-down.
2. Is there a setting in Windows to allow microphones and speakers for programs?
Thank you for your assistance.
Windows 10<br>
[Download Jami beta](https://dl.jami.net/windows/beta/jami.beta.x64.msi) from [Download Jami for Windows](https://jami.net/download-jami-windows/)Andreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/996Revoking Device: Password Field Does Not Accept Numbers2022-02-11T09:20:42ZMartin MayerRevoking Device: Password Field Does Not Accept NumbersHi all,
I just tried to revoke devices from my Android. However, when asked for the password,
I can only enter letters, not numbers. This silently fails.
----
To reproduce
* Try to revoke a secondary account
* Enter numbers, when ...Hi all,
I just tried to revoke devices from my Android. However, when asked for the password,
I can only enter letters, not numbers. This silently fails.
----
To reproduce
* Try to revoke a secondary account
* Enter numbers, when asked for the password
* Without hitting enter, dismiss the dialpad (back button)
* Check what you've entered. Numbers are mission
---
Version : 2021_05_21 from F-Droid.
----
Additional observations:
* Entering the required password pops up the dialpad
* The dialpad hides the password entry field
* Hence it is not obvious that I could not enter numerbs, just letters.
* Only dismissing the dialpad revealed the issue.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1307Option to use the Curve448 identity key pair and 224 bits encryption, or NIST...2023-11-20T14:26:02ZMarek ĽachOption to use the Curve448 identity key pair and 224 bits encryption, or NIST P-384 encryption in Jami's spec/clientsCurrently, Jami only officially supports _RSA encryption. To future prove-it, since RSA is already quite old, an update to the Jami specs (and then the clients) allowing also for the use of `elliptic Curve448 at 224 bits` encryption (for...Currently, Jami only officially supports _RSA encryption. To future prove-it, since RSA is already quite old, an update to the Jami specs (and then the clients) allowing also for the use of `elliptic Curve448 at 224 bits` encryption (for Python available through [eccsnacks](https://github.com/nnathan/eccsnacks)), would be welcome to future-proof its security.
Another potentially viable option for an update of the encryption standard, could be the `Riandael NIST P-384` encryption, which's usually 192bit (available for Python through https://pycryptodome.readthedocs.io/en/latest/index.html).
Thank you for considering,https://git.jami.net/savoirfairelinux/jami-project/-/issues/1305Update version of installed git (on Windows)2021-09-17T17:22:56ZAmin BandaliUpdate version of installed git (on Windows)Per https://git.jami.net/savoirfairelinux/jami-project/-/issues/1290#note_30286, the version of git currently installed (presumably by `scripts/install-deps-windows.ps1`) on Windows is too old (2.10.2), and should be bumped up (e.g. to 2...Per https://git.jami.net/savoirfairelinux/jami-project/-/issues/1290#note_30286, the version of git currently installed (presumably by `scripts/install-deps-windows.ps1`) on Windows is too old (2.10.2), and should be bumped up (e.g. to 2.33.0, the current latest release) if there are no blockers.Andreas TraczykMing Rui ZhangAndreas Traczyk