Labels Milestones

New Issue

Message handling #1

Closed

opened 6 months ago by gernot · 6 comments

gernot commented 6 months ago

Owner

Notes from meeting

• I need to call encrypt_message() Encryption works
• I only need to send sync attachments
• I should use the asn1-message

### Notes from meeting * ~~I need to call `encrypt_message()`~~ Encryption works * I only need to send sync attachments * I should use the asn1-message

gernot commented 5 months ago

Poster

Owner

Not sure about asn1, but atm the message exceeds mtu quite easily.

Not sure about asn1, but atm the message exceeds mtu quite easily.

gernot self-assigned this 5 months ago

gernot commented 5 months ago

Poster

Owner

How does encrypt_message deal with sync beacons?

How does encrypt_message deal with sync beacons?

gernot commented 4 months ago

Poster

Owner

Ok, updated policy after today's meeting:

• take everything as-is, no extra encryption, send all attachments as-is as extra messages
• so I guess that also means that I only populate the message struct on receiving, but don't decrypt anything.
• ignore anything that exceeds mtu with a fitting tsc

New question to be discussed next week: How does the engine know it needs to hand me a message with PGP_inline_EA encryption format?

Ok, updated policy after today's meeting: - [x] take everything as-is, no extra encryption, send all attachments as-is as extra messages - [x] so I guess that also means that I only populate the `message` struct on receiving, but don't decrypt anything. - [x] ignore anything that exceeds mtu with a fitting tsc New question to be discussed next week: How does the engine know it needs to hand me a message with `PGP_inline_EA` encryption format?

gernot added the

requirement

label 4 months ago

gernot started working 4 months ago

gernot referenced this issue from a commit 4 months ago

remove encryption and decryption

gernot closed this issue 4 months ago

gernot stopped working 4 months ago

6 hours 16 minutes

gernot reopened this issue 4 months ago

gernot commented 4 months ago

Poster

Owner

I forgot some encoding stuff…

I forgot some encoding stuff…

gernot commented 3 months ago

Poster

Owner

So, now I understand why I should originally encrypt myself. Not beacons, though.

So, now I understand why I should originally encrypt myself. Not beacons, though.

gernot commented 2 weeks ago

Poster

Owner

I'm still not sure how to handle sync Beacons, but otherwise, I think I do fulfill the original requirements now - encrypted asn1-message.

I'm still not sure how to handle sync Beacons, but otherwise, I think I do fulfill the original requirements now - encrypted asn1-message.

gernot closed this issue 2 hours ago

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

master

identities

threads

archive/gitea1

archive/gitea5

archive/globals

archive/identities

archive/no-network

archive/nonblocking

archive/send_on_linux

archive/unencrypted_transport

archive/unicast

encrypted_transport

Labels

Apply labels

Clear labels   

bug

Something is not working   

duplicate

This issue or pull request already exists   

enhancement

New feature   

help wanted

Need some help   

invalid

Something is wrong   

question

More information is needed   

requirement

Not really a bug, but a feature that is absolutely required   

wontfix

This won't be fixed

No Label

bug

duplicate

enhancement

help wanted

invalid

question

requirement

wontfix

Milestone

Set milestone

Clear milestone

No items

No Milestone

Projects

Set Project

Clear projects

No project

Assignees

Assign users

Clear assignees

No Assignees

gernot

1 Participants

Notifications

Subscribe

Total Time Spent: 6 hours 16 minutes

gernot

6 hours 16 minutes

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gernot/pEpTransportUDP#1

Write Preview

Loading…

Cancel

Save

There is no content yet.