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.

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

Fix and reenable Secrets-Encryption #1541

Open
6543 opened this issue Jan 14, 2023 · 6 comments
Open

Fix and reenable Secrets-Encryption #1541

6543 opened this issue Jan 14, 2023 · 6 comments
Labels
bug Something isn't working
Milestone

Comments

@6543
Copy link
Member

6543 commented Jan 14, 2023

... By default, Woodpecker does not encrypt secrets in its database. You can enable encryption using simple AES key or more advanced Google TINK encryption...

but right now we just get an error on start

rev #1475
cc @antomy-gc

@6543 6543 added the bug Something isn't working label Jan 14, 2023
@6543 6543 added this to the 1.0.0 milestone Jan 14, 2023
@smainz
Copy link
Contributor

smainz commented Jan 15, 2023

Looks like atm I am not able to start the server for development (master branch):

I added

###
WOODPECKER_ENCRYPTION_KEY=a-key
WOODPECKER_ENCRYPTION_DISABLE=true

to the .env file and in the logs I get:

{"time":"2023-01-15T17:35:41+01:00","message":"LogLevel = info"}
{"level":"warn","time":"2023-01-15T17:35:41+01:00","message":"no sqlite3 file found, will create one at 'woodpecker.sqlite'"}
{"level":"fatal","error":"failed initializing encryption service: failed initializing encryption clients: failed initializing encryption clients: attempt to init encrypted storage more than once","time":"2023-01-15T17:35:41+01:00","message":"could not create encryption service"}

Starting the server with

###
WOODPECKER_ENCRYPTION_KEY=123456789012345678901234567890123456789012

works for the first time:

{"time":"2023-01-15T17:43:36+01:00","message":"LogLevel = info"}
{"level":"warn","time":"2023-01-15T17:43:36+01:00","message":"no sqlite3 file found, will create one at 'woodpecker.sqlite'"}
{"level":"info","time":"2023-01-15T17:43:36+01:00","message":"initialized encryption on registered clients"}
{"level":"warn","time":"2023-01-15T17:43:36+01:00","message":"Encrypting all secrets in database"}
{"level":"warn","time":"2023-01-15T17:43:36+01:00","message":"All secrets are encrypted"}
{"level":"info","time":"2023-01-15T17:43:36+01:00","message":"enabled encryption on registered services"}
{"level":"info","time":"2023-01-15T17:43:36+01:00","message":"registered new encryption key"}
{"level":"warn","time":"2023-01-15T17:43:36+01:00","message":"encryption enabled"}
{"level":"info","time":"2023-01-15T17:43:36+01:00","message":"Starting Woodpecker server with version 'dev'"}

restarting it gives me:

{"level":"info","time":"2023-01-15T17:44:05+01:00","message":"initialized encryption on registered clients"}
{"level":"fatal","error":"failed initializing encryption service: failed validating encryption key: encryption key is invalid","time":"2023-01-15T17:44:05+01:00","message":"could not create encryption service"}

an I have to delete the sqlite DB

Can anyone please post a hint on how to configure AES encryption or disable it?

@6543
Copy link
Member Author

6543 commented Jan 15, 2023

#1549 will make next work again ...

@smainz
Copy link
Contributor

smainz commented Jan 15, 2023

Thanks!

@6543 6543 changed the title Secrets encryption can not be disabled Fix and reenable Secrets-Encryption May 2, 2023
@6543 6543 modified the milestones: 1.0.0, 1.1.0 Jun 2, 2023
@securitym0nkey
Copy link

Maybe it would be a good idea to have the documentation state that encryption is currently not supported. Took me a while to find this issue and realize it.

@pat-s pat-s modified the milestones: 2.0.0, 2.x.x Oct 13, 2023
@wollud1969
Copy link

Has the encryption of secret in between been fixed? I'm using the container image tagged with v2.0.0-rc.0-alpine and it appears to me, that it is still not working. At least, a secret I've added is stored in plain text in the database.

@qwerty287
Copy link
Contributor

No, this is still broken. See #2300 for progress

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants