Skip to content
This repository has been archived by the owner on Jan 3, 2023. It is now read-only.

Re-implement fetch-cve option for oscapd #13

Merged
merged 1 commit into from
Oct 15, 2015

Conversation

baude
Copy link
Contributor

@baude baude commented Oct 14, 2015

* Based on the agreement with Martin and DWalsh, we now
  have an option for oscapd as to whether to fetch the most
  recent cve input data.

* The singleton class previously used had to be refactored
  because of the daemonization and the need to change options
  each 'scan'.  Instead of using the singleton implementation,
  we now pass the applicationConfiguration class to other
  classes as an object.

* Made small correction to convert the byte onlycache to an
  int for equality checking.

    * Based on the agreement with Martin and DWalsh, we now
      have an option for oscapd as to whether to fetch the most
      recent cve input data.

    * The singleton class previously used had to be refactored
      because of the daemonization and the need to change options
      each 'scan'.  Instead of using the singleton implementation,
      we now pass the applicationConfiguration class to other
      classes as an object.

    * Made small correction to convert the byte onlycache to an
      int for equality checking.
@mpreisler
Copy link
Member

I really like that you removed the singleton, I wanted to do that but was postponing it.

Thanks!

@mpreisler mpreisler self-assigned this Oct 15, 2015
mpreisler added a commit that referenced this pull request Oct 15, 2015
Re-implement fetch-cve option for oscapd
@mpreisler mpreisler merged commit 78836ef into OpenSCAP:master Oct 15, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants