Giter VIP home page Giter VIP logo

keyutils's Introduction

These tools are used to control the key management system built into the Linux
kernel.

To build and install the tools and manual pages, run:

	make
	make install

If your glibc does not contain definitions for the new error codes and system
calls, then try:

	make NO_GLIBC_KEYERR=1

The tools are licensed under the GPL and the utility library under the LGPL.
Copies of these are included in this tarball.

keyutils's People

Contributors

dhowells avatar mkerrisk avatar mjmartineau avatar ckastner avatar mathstuf avatar tyhicks avatar jstancek avatar jbastian avatar sm00th avatar davejiang avatar flameeyes avatar doughdemon avatar kkaarreell avatar vapier avatar smuellerdd avatar

Stargazers

 avatar Ivan Robles avatar  avatar

Watchers

Daria Phoebe Brashear avatar Jeffrey Altman avatar James Cloos avatar

keyutils's Issues

Reproducibility patch file concerns

Hi,

I am using this repository in a project of mine. I am using the commit 4723f0185d11b13df243ad3cd41fbddfed53b5b1. One of the aims of the project is to showcase reproducibility.

I have noticed that this repository gets marked as non-reproducible because of two reasons:

  1. There is a date stamp integrated inside of the makefile
  2. There is a unique buildid that gets generated

At the moment, I have the following patch file:

diff --git a/Makefile b/Makefile
index 33a451e..c426bab 100644
--- a/Makefile
+++ b/Makefile
@@ -108,7 +108,7 @@ all: keyctl request-key key.dns_resolver
 ###############################################################################
 #RPATH = -Wl,-rpath,$(LIBDIR)
 
-VCPPFLAGS	:= -DPKGBUILD="\"$(shell date -u +%F)\""
+VCPPFLAGS	:= -DPKGBUILD="\"2023-01-01\""
 VCPPFLAGS	+= -DPKGVERSION="\"keyutils-$(VERSION)\""
 VCPPFLAGS	+= -DAPIVERSION="\"libkeyutils-$(APIVERSION)\""
 
@@ -131,7 +131,7 @@ $(DEVELLIB): $(SONAME)
 $(SONAME): $(LIBNAME)
 	$(LNS) $< $@
 
-LIBVERS := -shared -Wl,-soname,$(SONAME) -Wl,--version-script,version.lds
+LIBVERS := -shared -Wl,-soname,$(SONAME) -Wl,--build-id=your_build_id
 
 $(LIBNAME): keyutils.os version.lds Makefile
 	$(CC) $(CFLAGS) -fPIC $(LDFLAGS) $(LIBVERS) -o $@ keyutils.os $(LIBLIBS)

This technically solves both problems. However, the concern and purpose of this question is: how do I fix the buildid that gets generated. I understand I haven't done it optimally, but this does get the job done and the functionality of the program is unaffected.

However, I would like advice on an optimal solution for the date-stamp and unique buildid.

Thank you

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.