Displaying 4 results from an estimated 4 matches for "sig_verifi".
Did you mean:
sig_verify
2025 Apr 29
1
Multiple allowed signer files in `ssh-keygen -Y verify`
On Wed, 23 Apr 2025, Wiktor Kwapisiewicz via openssh-unix-dev wrote:
> Hello,
>
> I'm currently evaluating using `ssh-keygen -Y verify` to check OS artifacts
> (e.g. packages) and I noticed that the `-f allowed_signers_file` option can be
> passed only once. A side remark: technically it can be passed multiple times
> without a warning but the last invocation overrides all
2025 Apr 23
1
Multiple allowed signer files in `ssh-keygen -Y verify`
Hello,
I'm currently evaluating using `ssh-keygen -Y verify` to check OS
artifacts (e.g. packages) and I noticed that the `-f
allowed_signers_file` option can be passed only once. A side remark:
technically it can be passed multiple times without a warning but the
last invocation overrides all previous ones. Tested using:
$ ssh-keygen -Y verify -f allowed_signers -f /dev/null -n file -s
2015 Oct 15
3
Package integrity check via SHA256 or OpenPGP possible?
Dear list,
I'm using R in a corporate environment and was interested how R checks integrity of packages during an installation.
I saw (and verified my suspicion in the code[1]) that the verification purely relies on MD5.
>From an IT security perspective, this can be improved.
My question is: Is is possible to force R to verify integrity via SHA256 or even OpenPGP signatures?
If not are
2015 Oct 15
0
Package integrity check via SHA256 or OpenPGP possible?
On Thu, Oct 15, 2015 at 9:11 AM, Philip Gilli?en <guerda at freenet.de> wrote:
> I'm using R in a corporate environment...
That's irrelevant.
> is possible to force R to verify integrity via SHA256 or even OpenPGP signatures? If not are there any plans to support better hashes than MD5? As the source code looks, an extension to support other (optional) hash values would be