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

requests.go:42-42: decrypt requests #23

Closed
0pdd opened this issue Sep 16, 2017 · 2 comments
Closed

requests.go:42-42: decrypt requests #23

0pdd opened this issue Sep 16, 2017 · 2 comments
Labels
category/security importance/must

Comments

@0pdd
Copy link
Collaborator

0pdd commented Sep 16, 2017

The puzzle 7-633161db (from #7) in worker/requests.go (lines 42-42) has to be resolved: "decrypt requests"

The puzzle was created by Felix Neumann on 16-Sep-17.

Estimate: 0 minutes, role: IMP.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.
0pdd referenced this issue Sep 16, 2017
@fxnn
#7 worker: further implement request processing
cfe8a4e 
* for the sake of simplicity, let's drop the idea of implementing a
  queue for now and simply process each request as soon as we see it
* renamed files and types in worker package to provide a better naming,
  also being consistent with naming in drop package
* next step would be to write some processors
@fxnn
Copy link
Owner

fxnn commented Dec 30, 2017

Precondition: encryption, esp. #25

fxnn added a commit that referenced this issue Dec 30, 2017
@fxnn
fix #25, #23: setup key management and request encryption
ff5439c
@0pdd
Copy link
Collaborator Author

0pdd commented Dec 30, 2017

The puzzle 7-633161db has disappeared from the source code, that's why I closed this issue.

@0pdd 0pdd closed this as completed Dec 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
category/security importance/must
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fxnn @0pdd