Nevar pievienot vairāk kā 25 tēmas Tēmai ir jāsākas ar burtu vai ciparu, tā var saturēt domu zīmes ('-') un var būt līdz 35 simboliem gara.
 
 
 
Felix PK 9d1349d38f
Merge pull request #10 from MISP/only-core-features
pirms 1 gada
.idea cleanup pirms 1 gada
app remove leftovers of expandablecardview pirms 1 gada
gradle/wrapper cleanup pirms 1 gada
poster Upload poster englisch pirms 2 gadiem
screenshots improve readme pirms 1 gada
.gitignore .gitignore fix pirms 1 gada
README.md remove leftovers of expandablecardview pirms 1 gada
build.gradle add material preference switch to detail view pirms 1 gada
gradle.properties done convert to androidx pirms 1 gada
gradlew .gitignore fix pirms 1 gada
gradlew.bat .gitignore fix pirms 1 gada
settings.gradle Completely ported to IntelliJ Idea pirms 2 gadiem

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