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

collected maintenance changes #46

Merged
merged 4 commits into from
Jul 20, 2018
Merged

Conversation

LeSpocky
Copy link
Collaborator

These are collected changes, which should go in before releasing v1.2.0:

  • Fix the API for the md5() function. This was basically broken in v1.1 and should be removed later. See remove md5 #15 for details.
  • Add a function cgi_version() for convenience. Even if nobody uses it directly, it puts a version string into the binary one could extract with strings
  • Fix a possible segfault in a test, never segfaulted on my machine, but just in case.
  • Move header files to a separate directory. This does not change the location after installation, the header files are still installed where they were before. But it makes using the project as a submodule in a super project easier. Also the header files are easier to find in the source tree now.

LeSpocky added 4 commits July 19, 2018 09:10
Quote from issue rafaelsteil#15:

> libcgi contains an implementation of the md5 hash function, however
> its not used inside the library itself and the status regarding
> license or potential security issues (despite the weekness of md5
> itself) is not clear. If a user needs md5 he or she could get it from
> a specialized library.

Although md5 is deprecated (rafaelsteil#15) we can not simply remove the code from
the API. Do that later.

The HAVE_MD5 macro is useless, that was a relict from the old autotools
build and actually meant »build with md5«, so we can simply drop the
build time generated file and that macro.

Fixes: 0643151
Signed-off-by: Alexander Dahl <[email protected]>
Straight forward string output of the current library version.

Signed-off-by: Alexander Dahl <[email protected]>
When compiling with RelWithDebInfo gcc warned about out of bounds array
access. The line removed now tried to ensure the string is
null-terminated, but _after_ the actual array. The for loop initializing
the array however uses integer overflow and str[255] will contain the
necessary zero byte. Otherwise the strlen() check would fail anyway.

While at it set two compile definitions needed for this test exutable.

Signed-off-by: Alexander Dahl <[email protected]>
This way the include paths inside the project are similar to the ones a
user would use, and building examples with CMake from inside this
projects will be possible, if that is desired in the future.

Signed-off-by: Alexander Dahl <[email protected]>
@LeSpocky LeSpocky added this to the v1.2.0 milestone Jul 19, 2018
@LeSpocky LeSpocky merged commit 6ba2fe2 into rafaelsteil:master Jul 20, 2018
@LeSpocky LeSpocky deleted the maintenance branch July 20, 2018 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant