Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

at_c: non-encrypted notifications cause a segfault #246

Open
JeremyTubongbanua opened this issue May 10, 2024 · 2 comments
Open

at_c: non-encrypted notifications cause a segfault #246

JeremyTubongbanua opened this issue May 10, 2024 · 2 comments
Assignees
@JeremyTubongbanua

Comments

@JeremyTubongbanua
Copy link
Member

When set shouldencrypt=false when sending a notification, it will send isEncrypted:false and send the value in plain text (unencrypted). This willc ause a segfault.

This ticket is dependent on atsign-foundation/at_server#1944
@JeremyTubongbanua JeremyTubongbanua self-assigned this May 13, 2024
@JeremyTubongbanua
Copy link
Member Author

JeremyTubongbanua commented May 13, 2024 •
edited
Loading

Not a high priority since only encrypted notifications are ever used in the C Daemon

@JeremyTubongbanua
Copy link
Member Author

Setting this to blocked because some work I believe is needed to be done on the atServer side of things - atsign-foundation/at_server#2050

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JeremyTubongbanua JeremyTubongbanua

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JeremyTubongbanua