Skip to content
Snippets Groups Projects
Select Git revision
  • windows_ci
  • master default
  • cert_pk_id
  • proxy_push_result
  • cnode_put_id
  • update-windows-build
  • proxy
  • resubscribe_on_token_change
  • actions
  • client_mode
  • llhttp
  • search_node_add
  • crypto_aes_gcm_argon2
  • ios_notifications
  • log_fmt
  • v2asio
  • fix-msvc
  • message_split
  • meson
  • build_unify
  • v3.4.0
  • v3.3.1
  • v3.3.1rc1
  • v3.3.1rc2
  • v3.3.0
  • v3.2.0
  • v3.1.11
  • v3.1.10
  • v3.1.9
  • v3.1.8.2
  • v3.1.8.1
  • v3.1.8
  • v3.1.7
  • v3.1.6
  • v3.1.5
  • v3.1.4
  • v3.1.3
  • v3.1.2
  • v3.1
  • v3.0.1
40 results

opendht

  • Clone with SSH
  • Clone with HTTPS
  • Sébastien Blin's avatar
    Sébastien Blin authored
    Accounts can see their certificates expire. When it's the case, a
    migration is needed. However, several regressions can happen, because
    this behaviour can be tricky to test correctly. In this patch, a
    test is added to validate that the migration is done whenever the
    certificate expires.
    
    + OpenDHT needs to be bumped in order to be able to change the validity
    period of a certificate.
    + In ArchiveAccountManager, a method is added to change the validity
    of a certificate in the chain.
    + This patch also fixes a crash when a migration occurs directly on
    the archive (info_ was null causing a segfault).
    + Finally, cleanup some signatures unused in JamiAccount.
    
    GitLab: #684 (this is some preparative work)
    Change-Id: I901bc67fd63ce2ab26ded64662f8333d3a0eed50
    d1bc9390
    History
    Name Last commit Last update