Accepting request 629573 from home:jengelh:branches:security:forensics
- Compact description for size. Wrap it, too. OBS-URL: https://build.opensuse.org/request/show/629573 OBS-URL: https://build.opensuse.org/package/show/security:forensics/artifacts?expand=0&rev=6
This commit is contained in:
committed by
Git OBS Bridge
parent
6763a4ab44
commit
372971170d
@@ -1,3 +1,8 @@
|
||||
-------------------------------------------------------------------
|
||||
Thu Aug 16 12:28:18 UTC 2018 - jengelh@inai.de
|
||||
|
||||
- Compact description for size. Wrap it, too.
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Tue Aug 14 13:28:07 UTC 2018 - rpm@fthiessen.de
|
||||
|
||||
|
@@ -31,20 +31,17 @@ Source2: %{name}.keyring
|
||||
BuildArch: noarch
|
||||
|
||||
%description
|
||||
A free, community-sourced, machine-readable knowledge base of forensic artifacts that the world
|
||||
can use both as an information source and within other tools.
|
||||
A community-sourced, machine-readable knowledge base of forensic
|
||||
artifacts that can be used both as an information source and within
|
||||
other tools.
|
||||
|
||||
If you'd like to use the artifacts in your own tools, all you need to be able to do is read YAML.
|
||||
That's it. No other dependencies. The python code in this project is just used to validate all the
|
||||
artifacts to make sure they follow the spec.
|
||||
Using artifacts in tools just requires reading YAML. (The Python code
|
||||
in the project is merely used to validate that the artifacts follow
|
||||
the specification.)
|
||||
|
||||
The ForensicArtifacts.com artifact repository was forked from the GRR project artifact collection
|
||||
into a stand-alone repository that is not tool-specific. The GRR developers will migrate to using
|
||||
this repository and make contributions here. In addition the ForensicArtifact team will begin
|
||||
backfilling artifacts in the new format from the ForensicArtifacts.com website.
|
||||
|
||||
For some background on the artifacts system and how we expect it to be used see this blackhat
|
||||
presentation and youtube video from the GRR team.
|
||||
For some background on the artifacts system and how its developers
|
||||
expect it to be used, see the BlackHat presentation and Youtube video
|
||||
from the GRR team.
|
||||
|
||||
%package validator
|
||||
Summary: Digital Forensics Artifact Repository Validator
|
||||
@@ -53,8 +50,10 @@ BuildRequires: python-setuptools
|
||||
Requires: artifacts
|
||||
|
||||
%description validator
|
||||
Python modules and app to validate the artifact data. It is possible some apps directly call these python modules
|
||||
but by design they should work directly with the YAML files themselves and not use these python modules.
|
||||
Python modules and program to validate the artifact data. It is
|
||||
possible for programs to directly call these Python modules, but, by
|
||||
design, said programs should work directly with the YAML files
|
||||
themselves and not use these Python modules.
|
||||
|
||||
%prep
|
||||
%setup -q -n artifacts-%{timestamp}
|
||||
|
Reference in New Issue
Block a user