restructure
22
README.md
|
@ -1,33 +1,33 @@
|
|||
|
||||

|
||||
|
||||
# MISPBump
|
||||
|
||||
With MISPBump it is easy to share events on your MISP instance with other instances. Instead of generating organisations, sync-users and sync-servers you scan only two QR-Codes and the job is done.
|
||||
With MISPBump it is easy to synchronise events on different MISP instances. Instead of generating organisations, sync-users and sync-servers you only have to scan two QR-Codes and you are ready for syncing.
|
||||
|
||||
# Security
|
||||
|
||||
A key agreement is realized with Diffie Hellman (Elliptic Curve 256 Bit), sensible data is encrypted with AES.
|
||||
|
||||
(how are credentials stored in app, keystore?)
|
||||
|
||||
TODO: how are credentials stored in app, keystore?
|
||||
|
||||
|
||||
# How does it work?
|
||||
|
||||
1. Main screen (no changes)
|
||||
|
||||
1. Gather your organisation information from your MISP instance
|
||||

|
||||

|
||||
|
||||
1. Scan your partners generated public key and at the same time share yours
|
||||

|
||||

|
||||
|
||||
2. Validate the public key you scanned
|
||||

|
||||

|
||||
|
||||
3. After another scan the information you need to synchronise is securely transmitted to your phone
|
||||

|
||||

|
||||
|
||||
4. Upload the information to your own MISP instance
|
||||

|
||||

|
||||
|
||||
5. That's it! You are ready to share events across your instances
|
||||

|
||||

|
||||
|
|
Before Width: | Height: | Size: 68 KiB After Width: | Height: | Size: 68 KiB |
Before Width: | Height: | Size: 343 KiB After Width: | Height: | Size: 343 KiB |
Before Width: | Height: | Size: 380 KiB After Width: | Height: | Size: 380 KiB |
Before Width: | Height: | Size: 1.6 MiB After Width: | Height: | Size: 1.6 MiB |
Before Width: | Height: | Size: 109 KiB After Width: | Height: | Size: 109 KiB |
Before Width: | Height: | Size: 86 KiB After Width: | Height: | Size: 86 KiB |
After Width: | Height: | Size: 9.0 KiB |