Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
malscan
malscan
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Requirements
    • Requirements
    • List
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Malscan
  • malscanmalscan
  • Issues
  • #12

Closed
Open
Opened Oct 06, 2016 by Josh Grancell@jgrancellOwner

Possible Config Set Bug

There appears to be a bug in the way that the -s (config set) option is working, that may allow for unsafe sed of the config file.

Somehow I managed to change NOTIFICATION_ADDRESSES in the config file to NOTIFICATION_ADDRESS (missing the plural).

Assignee
Assign to
1.7.0 Release
Milestone
1.7.0 Release (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: malscan/malscan#12