Skip to content

CSRF directory needs to be writeable for creating the csrf-secret.php file #5194

Closed

Description

@thurban

Describe the bug

During the installation the installer tells you to make the CSRF path read-only after the installation finished. It does not tell where it is or provide an example for how to set the write permissions.
The installation completes regardless of the setting but it causes a lot of permission error logging in the cacti log.

Also the csrf-secret.php file can be access directly, exposing the secret to the web. It should be hidden and not returning the plain secret.

To Reproduce

Install a fresh Cacti

Expected behavior

Either show example commands or move the csfr-secret.php somewhere where it can be written/created.

Screenshots

grafik
grafik

Desktop (please complete the following information)

  • OS: [e.g. iOS]

  • Browser [e.g. chrome, safari]

  • Version [e.g. 22]

Smartphone (please complete the following information)

  • Device: [e.g. iPhone6]

  • OS: [e.g. iOS8.1]

  • Browser [e.g. stock browser, safari]

  • Version [e.g. 22]

Additional context

Add any other context about the problem here.

Activity

  1. added
    bugUndesired behaviour
    unverifiedSome days we don't have a clue
    on Jan 26, 2023
  2. TheWitness commented on Jan 26, 2023

    @TheWitness
    Member

    @netniV, assigned this to you. I think at least in the example we should show the vendor directory, without much explanation as a directory that only requires write for install. This is a one line change. We can do something glorious (aka different) in 1.3.

  3. added
    confirmedBug is confirm by dev team
    and removed
    unverifiedSome days we don't have a clue
    on Feb 5, 2023
  4. TheWitness commented on Feb 5, 2023

    @TheWitness
    Member

    Changing the assignment here since we have a little more time before release.

  5. added a commit that references this issue on Feb 5, 2023
  6. added this to the v1.2.24 milestone on Feb 5, 2023
  7. locked and limited conversation to collaborators on May 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugUndesired behaviourconfirmedBug is confirm by dev teamresolvedA fixed issue

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions