freebsd-src icon indicating copy to clipboard operation
freebsd-src copied to clipboard

typo in contrib/bearssl/src/hash/ghash_pclmul.c

Open 108062138 opened this issue 2 years ago • 6 comments

Name: Po-Yu, Wu Email: [email protected] At contrib/bearssl/src/hash/ghash_pclmul.c line79: shitfting -> shifting

This is from the Advanced UNIX Programming Course (Fall’23) at NTHU.

108062138 avatar Dec 24 '23 14:12 108062138

I think BearSSL is directly pulled from its Git repository to FreeBSD. You should report it there, so later it will be synced here. See contrib.

rilysh avatar Dec 24 '23 18:12 rilysh

I agree with @rilysh: please submit this upstream and post a link here. If you need to know where, just ask...

bsdimp avatar Dec 24 '23 23:12 bsdimp

I agree with @rilysh: please submit this upstream and post a link here. If you need to know where, just ask...

Thx for your reply, there is one more thing I'm confused. After I contact BearSSL and notify the typo(according to rilysh), I need post a link. It is the link that confused me. Is it about BearSSL's update info?

108062138 avatar Dec 26 '23 18:12 108062138

@108062138 You can send direct patches (in email)

You can either send this patch: https://patch-diff.githubusercontent.com/raw/freebsd/freebsd-src/pull/952.diff Or a direct link where the typo is: https://www.bearssl.org/gitweb/?p=BearSSL;a=blob;f=src/hash/ghash_pclmul.c;h=a58e7dc02bebcfe855f384d937848d8189b25fc2;hb=HEAD#l79

With some additional context.

rilysh avatar Dec 26 '23 18:12 rilysh

The general answer about what we'd like to document it is 'whatever the upstream offers'. Some do it all by email, in which case just pointing to the thread in their email archives is fine. Others do it by pull request, and those usually have a URL you can share here (and if it is on github, then there's cross-repo tracking of the different issues). These links will help us followup on things in the future.

bsdimp avatar Dec 26 '23 19:12 bsdimp

The general answer about what we'd like to document it is 'whatever the upstream offers'. Some do it all by email, in which case just pointing to the thread in their email archives is fine. Others do it by pull request, and those usually have a URL you can share here (and if it is on github, then there's cross-repo tracking of the different issues). These links will help us followup on things in the future.

Thx for your detailed reply~~ I just send bearssl email to notify them those typo and currently wait for their feedback.

108062138 avatar Dec 28 '23 16:12 108062138

I'm going to close this, we'll get it with the next bearssl import and don't need to keep it open.

bsdimp avatar Apr 17 '24 18:04 bsdimp