Commit 34e1e88c authored by hark's avatar hark
Browse files

bla

parent 6fdbe091
......@@ -14,7 +14,12 @@ possible ways to get the message to the pager:
- own transmitter
- iridium paging system
- udp packets via sattelite with a not encrypted dvb-ip downlink
- encoded in color changin lights (this thing with the twitter lights)
- on fm broadcast station (as fsk)
- soundsystem
how we do it now:
- with an arduino + radiohead library and OOK via a pin
some things on ECC:
......@@ -33,3 +38,4 @@ TODO:
- fix the serial input of the arduino-tx so you can send messages to it
- make a program to generate keypairs and upload them to the pager
- displaying the received messages in a proper way
- message counters (to know how many you missed)
......@@ -313,21 +313,7 @@ pl_print_keylist(struct pl_ctx *ctx) {
printf("the list of loaded keys: \n ");
for(list = ctx->keypairs; list != NULL; list = list->next) {
printf("address in list: %u \n", list->id );
/*
if (ctx->msg->address == list->id)
{
DBG("Found address in list!");
// set keypair to use
ctx->kp = list->kp;
}
else
{
DBG("address not found in list, message probably not for us");
return 1;
}
}
*/
}
}
}
......@@ -43,13 +43,33 @@ extern "C"
#include "packets.h"
/*
* List of all the available keypairs
* Should we use same list for only pubkeys?
*/
typedef struct list_kp {
uint32_t id;
struct pl_keypair *kp;
struct list_kp *next;
// things maybe:
// - nickname
// - message counter
} list_kp;
/*
* the inbox
*/
typedef struct list_inbox {
int status; // 1 unread 2 read
struct pl_pagermessage *msg;
struct list_inbox *prev;
struct list_inbox *next;
} list_inbox;
/*
* pagerlib context for sending or receiving messages
......@@ -68,7 +88,7 @@ struct pl_ctx
struct pl_keypair *kp;
// keypair list (all available keypairs)
struct list_kp *keypairs;
// struct pl_keypair *to, *from;
// place to store messages to be sent or received
struct pl_pagermessage *msg;
uint8_t receiver_compressed_point[ECC_COMPRESSED_SIZE];
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment