Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
1 result

Frequently-Asked-Questions.md

Blame
    • Code owners
    Assign users and groups as approvers for specific file changes. Learn more.
    Frequently-Asked-Questions.md 22.73 KiB

    Jami FAQ

    Basics

    Account management

    Audio / video

    Advanced

    This page aims to gather as many resources as possible (technical or not) and condense them to create concise documentation. Then, this can then be integrated into a tutorial or a help page on the website or in the clients.

    Resources :

    Basics

    What is Jami?

    Jami is an innovative communication system. It doesn't work like other solutions since its designed to protect user's freedom.

    The Jami network is distributed, hence, you may be invited to perform some actions that are considered bad practices on centralized or decentralized systems, but that are totally acceptable with Jami.

    • Jami is fundamentally different from other communication tools
    • Jami protects the privacy of its users
    • A Jami account is stored on the device, it must be saved

    It misses a feature!

    Not all features are implemented in all clients yet. Check list at: https://git.jami.net/savoirfairelinux/ring-project/wikis/features/All-features-by-client Contributions to this document are greatly appreciated!

    If you can't wait to have this feature, you can try another client.

    Jami just crashed / have a bug. What can I do?

    There's a orange / red exclamation side by my avatar. What does it mean?

    It's because your account is not connected to the DHT. Verify your internet connection or try to relaunch the application. If you use the push notifications, try to disable this option (and re-enable it).

    Where are the configuration files located

    Jami saves its configuration (account, certificates, history) at different locations depending the platform.

    • GNU/Linux: global configuration is under ~/.config/jami/dring.yml and Accounts files are under ~/.local/share/jami/. Finally some cache can be stored in ~/.cache/jami
    • OSX: The full configuration is under ~/Library/Application Support/Jami if installed via https://jami.net. Via the appstore it's ~/Library/Containers/com.savoirfairelinux.ring.macos/Data/Library/Application Support/jami
    • Android: The full configuration is under /data/data/cx.ring (may require root privileges)
    • Windows: global configuration is under %AppData%/Local/jami/dring.yml and Account files are under %AppData%/Local/jami/. Finally, some caches are in %USERPROFILE%/.cache/jami

    Account management

    What is a Jami account?

    Jami is not like a lot of communication software. It's not based on any central server and your account is only stored on your device. When you want to use Jami with your account, you don't have to use a classical login/password authentification.

    When you create a new Jami account, you don't have to provide private informations like a mail or a phone number. But this is the informations you can provide (all optionals):

    1. An avatar
    2. A display name, it's the name client will display on your contact entry with the avatar. It can contains special character.
    3. A username, this is a unique identifier and can be the direct translation of your JamiID. This identifier is stored on a server (ns.jami.net by default). Cf https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Name-Server-Protocol for more details on how you can use your own name server.
    4. A password. This password is used to protect the account archive in your device.

    So, after this step, the client will generate an archive (protected by the password you gave). This archive will contains your account's keys. And a JamiID is now created (a 40 chars length string. Technically, this ID is the fingerprint of your public key. And that's it, you have a Jami account.

    No password?

    With Jami, you are not forced to have a password on your account. Don't worry, it's a decentralized system, consequences are not the same than on other systems.

    With a centralized system, you use your password to authenticate on a public server. Someone who knows your password can usurp your identity.

    With Jami, your account is stored in a folder on your device. The password is only used to protect you from someone who have a physical access to your device by encrypting the account's archive (and don't let anyone access your private key)

    If your device is encrypted, you may not want/need to use a password.

    No username?

    For a while, Jami had no username management system. Instead, we had to use Infohashs. They are quite difficult to use for most people (ie : 3d1112ab2bb089370c0744a44bbbb0786418d40b). To mitigate the issue, we created a system that associate your Infohashs to a username of your choice that will be much more easier to remember. We recommand you to create a username: Jami will be friendlier.

    The technology we used to associate a username to a Infohashs, Ethereum blockchain, is also distributed, but it doesn't allow to modify or delete the association between a username and a InfoHash.

    You can still create an account without a username if you wish. Please note that if you choose this option, it is still possible to register a username later.

    How can I back-up my account?

    There is two ways to back-up your account:

    1. Link another device to your account, so your account will be in two devices. You can find this option in the account's settings page.
    2. Copy the account's archive on a USB flashdrive or any another place. This file can be found in the paths given in the previous question. In the linux client, you can export this archive from the client in the account's settings page.

    See https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Ring-configuration-path

    The content of the export.gz is explained here: https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/2.1.-Manage-Accounts#how-it-works-from-scratch but it's basically a gunzipped Json (AES encrypted if a password is set)

    How can I retrieve my username without my keys?

    It depends. If you used ns.jami.net, you can't. There is no way to prove it's your username without your key (and there is no way to change your current username). If it's another name server, it depends if it's possible to change the username linked. See this page for more details: https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Name-Server-Protocol

    I forgot my password, what can I do?

    Nothing. Because we don't have access to your datas, we can't have an option like "I forget my password". You are the only one in charge of your datas, so take care. If you are scared to forget a password, please use a password manager.

    What is the PIN when I want to link my account to another device

    When you choose to "link your device with another account", you have to enter the password of your account on your first device and a PIN. This PIN is generated by the first device, when you click on "Link this account to another device" (Generally in Settings -> Accounts -> Choose your account -> Link this account to another device), the account will be sent on the DHT during 5 minutes and a PIN is generated at this moment. This is the PIN you need to enter on the other device.

    How to delete my account?

    Accounts without Infohash

    A Jami account only exists on linked devices with this account. So, you only have to delete this account in app on all these devices and your account will not exists anymore. Or to uninstall Jami. If you delete the account's archive, your account will no longer exists. If you uninstall Jami, your data will be deleted too. And nobody will be able to retrieve your account. Never ever.

    • GNU/Linux

    In the settings page, go to Accounts, choose your account and click on the Delete button in the GUI. Another way is to remove configuration files

    • Android

    In the hamburger menu, choose Manage accounts, choose the account to delete and click on the trash icon.

    Note for accounts with a username

    The technology that handle usernames is also distributed. So, it depends the nameservice you choose to make the translation between a nickname and your Jami ID. By default, a username is registered on ns.jami.net where you can't modify the Jami ID associated to this username. So, if you delete or if you lost your account you will not be able to retrieve this username, ever. Nobody will be able to recreate an account with the same username.

    NOTE: If your account has a username, this username will not be deleted. For example, if you use the username pseudo on the name server ns.jami.net, when you will delete your Jami account and you create a new account, you will not be able to retrieve this username, because ns.jami.net can't prove it's your username.

    If you do not want to lose your account, please back-up files related to this one.

    What happens when I bind my account to a new device?

    When you start the binding procedure, the folder containing your account information is simply put on the Jami network for a few minutes. It is protected by a password Jami gives you.

    My contact is not seeing my avatar

    Due to technical limitations of distributed technologies, avatars are only transfered to your contacts when a call (audio or video) is established.

    Audio / video

    How to configure echo cancellation?

    Go to settings -> media -> and set change your audio manager. We recommend using Pulse audio.

    Video is laggy

    Use a lower definition. Go to settings -> media -> and change resolution. You can also try auto mode by clicking the HQ button during a call.

    I can't see myself

    End call and check that you have selected the right video device. Go to settings -> media -> and change device.

    Check that you can effectively see yourself in the right panel of settings -> media. You can double check that your device is working by installing the cheese application.

    Others can't ear me

    End call and try changing audio driver or audio input device.

    I have no sound

    End call and try changing audio driver or audio output device.

    Advanced

    What data passes through my machine when I participate in the Jami network?

    All these data are encrypted. There is:

    • ICE descriptors of other Jami users. ICE is a protocol that help establishing communication between two computers
    • certain text messages
    • as indicated above, accounts currently being linked to a new device

    Audio/video streams and some text messages pass through the VOIP protocol. Text messages can be sent either via VOIP or DHT (the distributed network) depending on whether a VOIP communication channel is already open or not.

    Why am I able to communicate with myself?

    Many users use Jami to transfer data from one machine to another.

    Should I enable push notifications?

    Push notifications allow Jami to operate in a way more adapted to the context of mobility (energy consumption, data...). However, for the moment, notifications go through Google's servers, via the Firebase service. Only one identifier is transferred and it is unusable for anyone who does not have access to your account.

    What is DHT proxy?

    The DHT proxy is a server that registers on the DHT for you and relays your information to you. Thus, it is the server that will be active on the DHT and will participate in the network, and no longer the target device. Multiple devices can register on the same DHT proxy.

    How the username registration service work?

    The usernames are registered on an Ethereum blockchain. By default, it's ns.jami.net that is used, but if you are a developper, you can create your own system. Hence, nothing forces you to implement it with a blockchain. You can check results at http://ns.jami.net/name/test, where "test" is a username for which we are looking for a matching Infohashs.

    How can I change the timeout for a call?

    In the dring.yml file, you can change your ringingTimeout (in seconds)

    How to back up and reimport conversations and accounts

    Note: This is only for client based on LRC (desktop ones)

    First you will need to export all your accounts (For GNU/Linux: Settings => Account => Export account). Then you will need to copy the database (in ~/.local/share/jami for example).

    Then on the new device, when you will open Jami for the first time, you have to re-import your accounts via the archive previously saved. This will re-import your settings and contacts (with empty conversations). Then close the client and replace the database with the one previously saved. That's all!

    How secure are you?

    ** We use TLS/SRTP to secure connection and communications over the network.**

    We implement SRTP over SIP using recommendations written in following RFCs:

    Typically 2 kind of sockets are negotiated. One for the control socket, the other for the media sockets

    Typical control session will use the following cipher suite: (TLS1.3)-(ECDHE-SECP384R1)-(RSA-PSS-RSAE-SHA384)-(AES-256-GCM) (TLS_ECDHE_RSA_AES_256_GCM_SHA384)

    DTLS (fallback) supported: "SECURE192:-KX-ALL:+ANON-ECDH:+ANON-DH:+SECURE192:-VERS-TLS-ALL:+VERS-DTLS-ALL:-RSA:%SERVER_PRECEDENCE:%SAFE_RENEGOTIATION" TLS: "SECURE192:-KX-ALL:+ANON-ECDH:+ANON-DH:+SECURE192:-RSA:-GROUP-FFDHE4096:-GROUP-FFDHE6144:-GROUP-FFDHE8192:+GROUP-X25519:%SERVER_PRECEDENCE:%SAFE_RENEGOTIATION"

    Supported crypto suite for the media session are:

    • AES_CM_128_HMAC_SHA1_80 / SRTP_AES128_CM_HMAC_SHA1_80
    • AES_CM_128_HMAC_SHA1_32 / SRTP_AES128_CM_HMAC_SHA1_32

    When do public IPs get exposed?

    We can describe 3 main connectivity scenarios. A classic configuration (1.), behind a VPN (2.), via Tor (3.). As Jami is a p2p app, I think you understand that (2.) or (3.) is a bit mandatory to avoid IP leaking.

    Moreover, even if it's my answer, you can choose to not trust my answer and check the code, or use wireshark or other tools. Generally, I (and the other devs I think) are using the first scenario (sometimes the second one), and we surely can't test all the network we want, so if you discover a bug, please open a issue.

    Anyway, in these 3 scenarios, there is 3 main actions:

    Classic config

    • Send a message

    The Jami application is running a DHT (https://opendht.net) node on your device. So every operations on the DHT will use your ips. This is why Jami has the option to use a dhtproxy (eg dhtproxy.jami.net), this will avoid to use your node, but will use another node on the network (which will see your ip). Note that your message is not sent directly to the other device. In fact your message is sent on some nodes of the DHT and your contact will retrieve the message on this node. So, your contact don't see your IP at this step, but the node who get the message will (or they will see the IP of the proxy).

    • Send a file

    As described in the docs, you will send a message with all the IP you know that your peer can contact in an encrypted packet. So, if your peer send you a file or you send a file, your addresses will appear in the ICE message.

    • Calls

    Same as above, the IP is present in the ICE.

    Behind a VPN

    • Send a message

    The IP of your VPN will be used by the DHT node. If you want a proof, you can compile dhtnode and run the 'la' command to get your public detected address. This is what I got:

    ./tools/dhtnode -b bootstrap.jami.net
Bootstrap: bootstrap.jami.net:4222
OpenDHT node be58fdc9f782269bfc0bbfc21a60bca5f02cb881 running on port 54299
 (type 'h' or 'help' for a list of possible commands)

>> la
Reported public addresses:
IPs OF MY VPN

    So, if you don't use a proxy, your VPN addresses will be used for using the DHT. If you use a dhtproxy, the dhtproxy will see your VPN addresses

    • Send a file

    Same as above, the ICE will contains:

    • addresses from your LAN
    • public address of your VPN
    • TURN address if TURN is enabled
    • Do a call

    Same as above, your public address is replaced by your VPN address. You can see it in the logs from daemon. See https://git.jami.net/savoirfairelinux/ring-project/wikis/tutorials/Bug-report-guide#logs

    Tor

    • Send a message

    Tor basically doesn't supports UDP. This means that you can't use your DHT node locally, you MUST use a DHTProxy. That proxy will see the Exit node.

    • Send a file

    I prefer a proof that any description. So, I did a file transfer with Jami + TOR. This is what I see in the logs for the remote:

    [1574218330.556|10688|p2p.cpp           :241  ] [Account:93a03f519f394143] add remote ICE candidate: Hc0a8c801 1 TCP 2130706431 192.168.200.1 33293 typ host tcptype passive
[1574218330.556|10688|p2p.cpp           :241  ] [Account:93a03f519f394143] add remote ICE candidate: Hc0a8c801 1 TCP 2130706431 192.168.200.1 9 typ host tcptype active
[1574218330.556|10688|p2p.cpp           :241  ] [Account:93a03f519f394143] add remote ICE candidate: Hc0a80103 1 TCP 2130706431 192.168.1.3 33293 typ host tcptype passive
[1574218330.556|10688|p2p.cpp           :241  ] [Account:93a03f519f394143] add remote ICE candidate: Hc0a80103 1 TCP 2130706431 192.168.1.3 9 typ host tcptype active
[1574218330.556|10688|p2p.cpp           :241  ] [Account:93a03f519f394143] add remote ICE candidate: R33fe279d 1 TCP 16777215 51.254.39.157 27427 typ relay tcptype passive
[1574218330.556|10688|p2p.cpp           :241  ] [Account:93a03f519f394143] add remote ICE candidate: Sc0a8c801 1 TCP 1694498815 185.220.101.24 33293 typ srflx tcptype passive

    The first ones are some 192.168.x.x so we don't care. 51.254.39.157 is the TURN address in France (my device is in the Canada). 185.220.101.24 is the Tor exit node:

    inetnum:        185.220.101.0 - 185.220.101.127
netname:        MK-TOR-EXIT
    • Do a call

    This will not work (actually, you can create the SIP control connection because it's a TCP connection), but medias are negotiated in UDP, so this will fail.

    What ports does Jami use?

    Jami works as a server and gets new ports for each connections (randomly binded). These are the ranges that can be used for each component:

    • dht: UDP [4000, 8888]
    • audio: UDP [16384-32766]
    • video: UDP [49152-65534]
    • SIP Control: UDP/TCP randomly binded

    So for ufw, we recommend to run: sudo ufw default allow outgoing

    For now, you can't specify a specific range to configure ports used by Jami. The inbound traffic can be controlled without issue, Jami should work and can use a TURN server if needed.

    If you run your own proxy or nameserver:

    • dhtproxy, nameserver: TCP [80-100], 443

    If you run your own TURN server:

    • TURN/STUN: TCP+UDP 3478, 5349

    How can I configure the codecs even more?

    Codecs can be configured via a file. In the configurations files, you can create a file called encoder.json like this:

    {
    "libx264": {
        "profile": 100,
        "level": 42,
        "crf": 20,
        "preset": "ultrafast"
    },
    "h264_vaapi": {
        "low_power": 1
    },
    "libopus": {
        "application": "voip"
    }
}

    or:

    {
    "libopus": {
        "bit_rate": 128000
    }
}

    This file is located in the same directory of dring.yml (https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Ring-configuration-path)

    The best way to check which options are supported is through the command "ffmpeg -h encoder=[encoder_name]" where encoder_name can be whichever of libx264, libvpx, mpeg4, h263, libopus, libspeex, g722, pcm_alaw, pcm_mulaw (FFmpeg names for all of Jami's supported encoders).