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

Update FeatureUtility command to include new verify option #6649

Closed
jjiwooLim opened this issue May 23, 2023 · 17 comments · Fixed by #6975 or #7338
Closed

Update FeatureUtility command to include new verify option #6649

jjiwooLim opened this issue May 23, 2023 · 17 comments · Fixed by #6975 or #7338
Assignees
Labels
23.0.0.10 peer reviewed technical reviewed An SME reviewed and approved the documentation from a technical perspective.
Milestone

Comments

@jjiwooLim
Copy link

jjiwooLim commented May 23, 2023

Epic: OpenLiberty/open-liberty#17220

Option Description
--verify = verify_option Specifies how features should be verified. Supported values are enforce,skip,all, and warn. If this option isn't specified, a default value of enforce is used.

- enforce: Verifies the signatures of all Liberty features except for user features.
- skip: Skips verification altogether and does not download any feature signatures.
- all: Verifies both Liberty features and user features.
- warn: Same as "all", but it will not terminate installation in the event that verification fails.
Environment variable Corresponding properties Description
FEATURE_VERIFY feature.verify Same as setting --verify option for installFeature and installServerFeatures command.
  • Add new subject header "Verify user features"

You can verify your user features by providing your public key ID and key URL. Instructions on generating a key pair, signing the user feature and distributing your key can be found here.

#Provide long key ID (64 bit) format
myKey.keyid=0xBD9FD5BE9E68CA00

#Provide full URL of your key
myKey.keyurl=https://keyserver.ubuntu.com/pks/lookup?op=get&options=mr&search=0xBD9FD5BE9E68CA00

#It can also be local file 
# myKey.keyurl=/pubkey.asc
@dmuelle dmuelle added this to the 23.0.0.6 milestone May 24, 2023
@ramkumar-k-9286 ramkumar-k-9286 self-assigned this May 25, 2023
ramkumar-k-9286 added a commit that referenced this issue May 26, 2023
 Update FeatureUtility command-new verify option-1

#6649
@dmuelle dmuelle added technical reviewed An SME reviewed and approved the documentation from a technical perspective. and removed Developer reviewed labels May 30, 2023
@dmuelle
Copy link
Member

dmuelle commented May 30, 2023

Hi Ram, just a few minor suggestions

  • i think it should be more clear that verify_option is an example variable that is replaced with one of the four values It should render in italics like other variable examples on this page
  • If this option is not specified, a default value encode is used.---> If this option is not specified, the default value is encode .
  • for warn, does failure result in a warning message to the console? The name suggests this but the description doesn't say
  • in the table on this page, replace this description with a description of what it actually does: "Same as setting --verify option for installFeature and installServerFeatures command."
  • under "verify use features" separate the code comments from the examples, and rewrite the last description to be more concrete: "It can also be local file"

ramkumar-k-9286 added a commit that referenced this issue May 31, 2023
Update FeatureUtility command-new verify option-2

#6649
@jjiwooLim
Copy link
Author

jjiwooLim commented May 31, 2023

Hi @ramkumar-k-9286 ,

I reviewed again after reading David's comment.

  • - verify_option is still not rendered as italics in both installFeature and installServerFeatures page.

  • - All 3 pages have slightly different descriptions for enforce, skip, all, and warn. Should we be consistent? I think the descriptions on featureUtility-command page is the most descriptive ones.

  • - for warn it does result in a warning message to the console. We should mention it.
    eg) "A verification failure does not immediately end the installation process, but it will result in a warning message. "

  • - under "verify use features", it might be worth mentioning the supported protocols for key URL.
    "Supported protocols are HTTP, HTTPS, and file."

  • I forgot that we introduced a new exit code for the FeatureUtility installFeature and installServerFeatures commands. Exit code 37 is added.

| Code | Explanation |
| 37 | 37 indicates that the feature signature verification failed. |

ramkumar-k-9286 added a commit that referenced this issue Jun 1, 2023
Update FeatureUtility command-new verify option-3

#6649
@jjiwooLim
Copy link
Author

lgtm!

@dmuelle
Copy link
Member

dmuelle commented Jun 2, 2023

LGTM, thanks

@dmuelle dmuelle modified the milestones: 23.0.0.6, 23.0.0.7 Jun 15, 2023
@dmuelle
Copy link
Member

dmuelle commented Jul 14, 2023

Epic moved to 23.0.0.8

@dmuelle dmuelle added 23.0.0.8 and removed 23.0.0.7 labels Jul 14, 2023
@dmuelle dmuelle removed this from the 23.0.0.7 milestone Jul 18, 2023
@dmuelle dmuelle added this to the 23.0.0.8 milestone Jul 18, 2023
@dmuelle dmuelle added 23.0.0.9 and removed 23.0.0.8 labels Aug 10, 2023
@dmuelle dmuelle modified the milestones: 23.0.0.8, 23.0.0.9 Aug 10, 2023
@dmuelle
Copy link
Member

dmuelle commented Sep 7, 2023

LGTM, send to staging when you have a chance

@jjiwooLim
Copy link
Author

@ramkumar-k-9286 @dmuelle Sorry this is moved to 23.0.0.10.

@dmuelle
Copy link
Member

dmuelle commented Sep 7, 2023

Thanks @jjiwooLim - in that case @ramkumar-k-9286 , we can just leave it as is in draft until the feature is ready to release.

@jjiwooLim
Copy link
Author

jjiwooLim commented Oct 12, 2023

Typo found: --verify = encode should be enforce

Specifies how features must be verified. how features should be verified during a process or installation. Supported values are enforce, skip, all, and warn. If this option is not specified, the default value is enforce.

enforce: Verifies the signatures of all Liberty features except for user features. It checks the integrity and authenticity of the features that are provided by the Liberty framework.

ramkumar-k-9286 added a commit that referenced this issue Oct 13, 2023
FeatureUtility-encode-to-enforce

#6649
@ramkumar-k-9286
Copy link
Contributor

ramkumar-k-9286 commented Oct 13, 2023

@jjiwooLim
Copy link
Author

@jjiwooLim jjiwooLim reopened this May 14, 2024
@dmuelle
Copy link
Member

dmuelle commented May 14, 2024

Hi @jjiwooLim - that information was moved to https://openliberty.io/docs/latest/reference/command/featureUtility-commands.html#_modifications_for_featureutility_commands

The link you found was an artifact that needs to be deleted. Apparently the page was removed from the TOC but the file was not deleted. I will delete it in the next doc release to ensure it can't be found by accident. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
23.0.0.10 peer reviewed technical reviewed An SME reviewed and approved the documentation from a technical perspective.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants