Skip to content

Avoid tmpnam() in nutconf #2295

@jimklimov

Description

@jimklimov

This method is deemed insecure and causes built-in (run-time and linker) warnings from nutstream.cpp::NutFile::tmpName() nowadays.

There are alternatives, but it seems they differ per platform: https://stackoverflow.com/questions/3299881/tmpnam-warning-saying-it-is-dangerous - so likely some detectors in configure.ac would be needed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    CIEntries related to continuous integration infrastructure (here CI = tools + scripts + recipes)nutconfNUT configuration library and toolportabilityWe want NUT to build and run everywhere possiblerefactor/fightwarnPR or issue proposal to improve code maintainability without functional changes, or to fix warnings

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions