Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
aports
aports
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 676
    • Issues 676
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 206
    • Merge Requests 206
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • alpine
  • aportsaports
  • Issues
  • #9505

Closed
Open
Opened Oct 03, 2018 by Nick Lalic@nicklalic

acf-openssl, /etc/ssl/openssl-ca-acf.cnf setting new_certs_dir not updating?

Hi,

I am trying to run acf/acf-openssl in a docker container. I’d like to place all user generated data into a docker volume. I attempted to do this by changing the $dir variable in openssl-ca-acf.cnf (in this case I changed it to /volume). This had the desired effect for most settings, except the new_certs_dir is still being written to /etc/ssl/cert. It appears as if the new_certs_dir setting is not being “picked up” in acf-openssl.

I’m using Docker for Mac. Starting with the Docker Alpine:3.8 container, the steps to reproduce the behavior from ash are:

<code class="shell">
apk update && apk upgrade
apk add alpine-conf acf-core act-alpine-baselayout acf-openssl. 
setup-acf
</code>

Finally, I edit the /etc/ssl/openssl-ca-acf.cnf file, changing dir:

<code class="shell">
# mkdir /volume if not mounted
apk add vim
vim /etc/ssl/openssl-ca-acf.cnf
=> dir = /volume
</code>

I then bring up ACF in Chrome at https://localhost. I generate a CA and a certificate with the CA.

Observed behavior:
The data for the generated certificate (password, key, .pfx file etc) are still placed in /etc/ssl/cert.

Expected behavior:
certificates created in /volume instead.

Is there something I am missing?

I am new to Alpine, so please let me know if there is any other information I can provide.

Thanks!

(from redmine: issue id 9505, created on 2018-10-03)

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: alpine/aports#9505