[Lacre test] - Launch silent lacre test #535
Labels
No Label
administration
Akkoma
Android
Bare metal
bug
Communication
Community
Cryptpad
Discussion
Documentation
duplicate
enhancement
etherpad
Feature request
Feedback
finances
Fixed
forgejo
fun_project
Goal 2024
help wanted
Howto
🤔️ Investigate
ios
jitsi
lacre
Lacre Test
ldap
Lemmy
LibreTranslate
low prio
Lufi
macos
Mail
Merch
monitoring
movim
needs_refine
New Auth
Nextcloud
nice to have
on hold
proposal
question
Ready
refined
Roundcube
searX
spam-protection
Staging Server
Themes
TOR
Urgent!
Website
windows
wontfix
xmpp
Yearly Report
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Disroot/Disroot-Project#535
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Since lacre works whether there are emails to encrypt or not (all emails pass thought lacre), to check whether there is some issue with it before people start using it, we want to launch lacre for few hours without any keys uploaded.
This will allow us to pick up on possible issues like enconding issue we have been dealing with the previous time.
Therefore we will launch Lacre for few hours to inspect logs and see if there is anything obvious.
PRs done and ready to deploy.
Deployed and tested for an hour. Once I consult with @pfm about logging, we will be able to run tests asap.
Had launched First tests on disroot.org.
So far we seen one exeption with weird header formatting from some emails originating from microsoft.
@pfm submitted workaround to the issue https://git.disroot.org/Disroot/gpg-lacre/src/tag/v0.2.1
Lacre tests are restarted 🤞.
For last 24 hours we are running lacre on disroot mail server. The edge cases we noticed before arent counding anymore but are delivered in clear text. This is the workaround which allows delivery upon errors.
We have been running lacre in the background for entire month. Several issues has been fixed. We are ready for proper beta tests as well as we have discussed and agreed to future improvement and development of the service.
So far so good! We are on the road to lacre on disroot!