Skip to content

How to handle OS-specific issues in a gem or ruby engine #186

Open
@reedloden

Description

@reedloden

We need a way to track operating system specific issues affecting a gem or ruby engine.

Here's one example:

While it affects cross-platform code, seems to only be exploitable on mingw32

Separately, looks like at least one Ruby developer disputes that this a security issue, so there's that to deal with as well.

Perhaps add an os field to the YAML format?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions