Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix input termination for pgpParsePkts #325

Commits on Oct 2, 2024

  1. Fix input termination for pgpParsePkts

    The `pgpParsePkts` function needs the OpenPGP ASCII armored input to be
    null terminated. The librepo contains code that checks if the input is
    null-terminated. If it is not, the code creates a local null-terminated
    copy of the input.
    
    There was a bug in the code, so it may look for a terminating null
    several bytes behind the input buffer. And when a null was found behind
    the input buffer, the termination was not done. This caused
    the `pgpParsePkts` function to process several extra characters after
    the input buffer. These characters are generally random and sometimes
    cause the `pgpParsePkts` function to return an error.
    jrohel committed Oct 2, 2024
    Configuration menu
    Copy the full SHA
    06f979f View commit details
    Browse the repository at this point in the history