Você não pode selecionar mais de 25 tópicos Os tópicos devem começar com uma letra ou um número, podem incluir traços ('-') e podem ter até 35 caracteres.
 
 
 
Felix PK 9d1349d38f
Merge pull request #10 from MISP/only-core-features
1 ano atrás
.idea cleanup 1 ano atrás
app remove leftovers of expandablecardview 1 ano atrás
gradle/wrapper cleanup 1 ano atrás
poster Upload poster englisch 2 anos atrás
screenshots improve readme 1 ano atrás
.gitignore .gitignore fix 1 ano atrás
README.md remove leftovers of expandablecardview 1 ano atrás
build.gradle add material preference switch to detail view 1 ano atrás
gradle.properties done convert to androidx 1 ano atrás
gradlew .gitignore fix 1 ano atrás
gradlew.bat .gitignore fix 1 ano atrás
settings.gradle Completely ported to IntelliJ Idea 2 anos atrás

README.md

MISPbump

Simple and secure synchronisation of MISP instances

What is MISPbump?

With MISPbump admins can easily synchronize MISP instances by exchanging relevant information via encrypted QR codes.

Note that only use case 1 from the documentation is supported.

How does MISPbump work?

MISP admins log in by providing the base URL of their instance and their authkey.

After a successfull login the admin’s profile and the linked organisation information will be downloaded.

In the main screen you can start a synchronisation process by pressing the dedicated button.

The synchronisation process consists of 3 steps:

  1. Key Exchange
    To provide a secure chanel for data exchange, the first step is to generate a shared secret with Diffie–Hellman key exchange (Elliptic Curve).

    Public keys are exchanged via QR code.

  2. Synchronisation Information Exchange
    Contains the following information:

    • Own Organisation: Name, UUID, description, nationality, sector, type and contacts
    • Own User: Email
    • Own MISP instance: base URL
    • Generated: sync user authkey, sync user password
      (your partner will create a sync user with these credentials for you)

    The synchronisation information is encrypted with AES using the shared secret (from step 1).

    The synchronisation process information will be saved securely on the device.

  3. Upload information to own MISP instance
    Uploading the information to the MISP instance is accomplished with MISP’s REST API.

    Uploading consists of the following steps:

    1. Create organisation
    2. Create sync user & add to organisation
    3. Create sync server & populate with information above

After that the two MISP instances are able to share Events based on their permissions.

Dependencies