search for: _source_filedigest_algorithm

Displaying 7 results from an estimated 7 matches for "_source_filedigest_algorithm".

2016 Jan 20
2
signing RPM packages with SHA256
...e .. try 8 instead. So: >>> >>> rpm --define '_binary_filedigest_algorithm 8' >>> >>> or in .rpmmacros: >>> >>> _binary_filedigest_algorithm 8 >>> >> >> There is another one as well: >> >> --define "_source_filedigest_algorithm 8" >> >> --define "_binary_filedigest_algorithm 8" >> >> >> Defining it in the .rpmmacros would be best .. I think otherwise you >> would need to define it in youe rpmbild line AND your rpm signature line. >> >> Are you building your rp...
2016 Jan 20
2
signing RPM packages with SHA256
...e> > > ===== > > if some some reason it does not like the SAH256 value .. try 8 instead. So: > > rpm --define '_binary_filedigest_algorithm 8' > > or in .rpmmacros: > > _binary_filedigest_algorithm 8 > There is another one as well: --define "_source_filedigest_algorithm 8" --define "_binary_filedigest_algorithm 8" Defining it in the .rpmmacros would be best .. I think otherwise you would need to define it in youe rpmbild line AND your rpm signature line. Are you building your rpms in mock or from rpmbuild on the command line? If I do this on my...
2016 Jan 20
1
signing RPM packages with SHA256
...me reason it does not like the SAH256 value .. try 8 instead. So: >> >> rpm --define '_binary_filedigest_algorithm 8' >> >> or in .rpmmacros: >> >> _binary_filedigest_algorithm 8 >> > > There is another one as well: > > --define "_source_filedigest_algorithm 8" > > --define "_binary_filedigest_algorithm 8" > > > Defining it in the .rpmmacros would be best .. I think otherwise you > would need to define it in youe rpmbild line AND your rpm signature line. > > Are you building your rpms in mock or from rpmbuild...
2016 Jan 20
0
signing RPM packages with SHA256
...t;>>> rpm --define '_binary_filedigest_algorithm 8' >>>> >>>> or in .rpmmacros: >>>> >>>> _binary_filedigest_algorithm 8 >>>> >>> >>> There is another one as well: >>> >>> --define "_source_filedigest_algorithm 8" >>> >>> --define "_binary_filedigest_algorithm 8" >>> >>> >>> Defining it in the .rpmmacros would be best .. I think otherwise you >>> would need to define it in youe rpmbild line AND your rpm signature line. >>> >&...
2016 Jan 21
2
signing RPM packages with SHA256
...nary_filedigest_algorithm 8' >>>>> >>>>> or in .rpmmacros: >>>>> >>>>> _binary_filedigest_algorithm 8 >>>>> >>>> >>>> There is another one as well: >>>> >>>> --define "_source_filedigest_algorithm 8" >>>> >>>> --define "_binary_filedigest_algorithm 8" >>>> >>>> >>>> Defining it in the .rpmmacros would be best .. I think otherwise you >>>> would need to define it in youe rpmbild line AND your rpm signature...
2016 Jan 20
2
signing RPM packages with SHA256
hi, I noticed that RPM packages I sign use SHA1 Signature : RSA/SHA1, Fri 08 Jan 2016 10:50:58 AM PST, Key ID ad3b591d147abf59 Signatures from CentOS 7 use SHA256 Signature : RSA/SHA256, Wed 06 Jan 2016 08:54:58 AM PST, Key ID 24c6a8a7f4a80eb5 I'm trying to find where / how to use sha256 when I sign packages but I am not having much luck. Closest I have found is this :
2016 Jan 21
0
signing RPM packages with SHA256
...://fedoraproject.org/wiki/RPM_file_format_changes_to_support_SHA-256 >>>>>>> This thread has been a whole bunch of confusion. What you're trying to do requires that you add one line to your .rpmmacros file: %_gpg_digest_algo sha256 The _binary_filedigest_algorithm and _source_filedigest_algorithm don't affect the signature, they affect the file digest. That is, they set the checksum by which files will be verified by rpm -V. You can see the digest of each file using "rpm -qp --dump". >> I'm still not getting it to work - I am trying outside of mock. As far as I...