Hello community,
here is the log from the commit of package artifacts for openSUSE:Factory
checked in at 2018-08-27 13:48:21
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/artifacts (Old)
and /work/SRC/openSUSE:Factory/.artifacts.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "artifacts"
Mon Aug 27 13:48:21 2018 rev:2 rq:629647 version:20180628
Changes:
--------
--- /work/SRC/openSUSE:Factory/artifacts/artifacts.changes 2015-05-19
23:36:24.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.artifacts.new/artifacts.changes 2018-08-27
13:48:40.120493176 +0200
@@ -1,0 +2,21 @@
+Thu Aug 16 12:28:18 UTC 2018 - jeng...@inai.de
+
+- Compact description for size. Wrap it, too.
+
+-------------------------------------------------------------------
+Tue Aug 14 13:28:07 UTC 2018 - r...@fthiessen.de
+
+- Fixed invalid source file (mismatching hash)
+- Added GPG source verification
+
+-------------------------------------------------------------------
+Thu Aug 9 16:58:41 UTC 2018 - r...@fthiessen.de
+
+- Cleaned up spec file
+ * Use license macro
+ * Dropped defattr as it is not required anymore, recent rpms
+ add a default defattr line if none is present in the rpm files
+ section
+- Update to 20180628
+
+-------------------------------------------------------------------
Old:
----
artifacts-20150409.tar.gz
New:
----
artifacts-20180628.tar.gz
artifacts-20180628.tar.gz.asc
artifacts.keyring
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ artifacts.spec ++++++
--- /var/tmp/diff_new_pack.nBNtiq/_old 2018-08-27 13:48:40.792494133 +0200
+++ /var/tmp/diff_new_pack.nBNtiq/_new 2018-08-27 13:48:40.792494133 +0200
@@ -1,7 +1,7 @@
#
# spec file for package artifacts
#
-# Copyright (c) 2015 SUSE LINUX GmbH, Nuernberg, Germany.
+# Copyright (c) 2018 SUSE LINUX GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
@@ -16,26 +16,32 @@
#
-%define timestamp 20150409
+%define timestamp 20180628
Name: artifacts
Version: %{timestamp}
Release: 0
Summary: Digital Forensics Artifact Repository
License: Apache-2.0
Group: Productivity/Security
-Url: https://github.com/ForensicArtifacts/artifacts/wiki
-Source:
https://github.com/ForensicArtifacts/artifacts/releases/download/%timestamp/artifacts-%timestamp.tar.gz
-BuildRoot: %{_tmppath}/%{name}-%{version}-build
+URL: https://github.com/ForensicArtifacts/artifacts/wiki
+Source0:
https://github.com/ForensicArtifacts/artifacts/releases/download/%{timestamp}/artifacts-%{timestamp}.tar.gz
+Source1:
https://github.com/ForensicArtifacts/artifacts/releases/download/%{timestamp}/artifacts-%{timestamp}.tar.gz.asc
+# Key 0xD9625E5D7AD0177E by Joachim Metz https://github.com/joachimmetz
+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.
-
-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.
-
-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.
+A community-sourced, machine-readable knowledge base of forensic
+artifacts that can be used both as an information source and within
+other tools.
+
+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.)
+
+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
@@ -44,8 +50,10 @@
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}
@@ -57,15 +65,15 @@
python setup.py install --root=%{buildroot} --prefix=%{_prefix}
%files
-%defattr(-,root,root)
-%doc ACKNOWLEDGEMENTS AUTHORS LICENSE README
-/usr/share/artifacts
+%license LICENSE
+%doc ACKNOWLEDGEMENTS AUTHORS README
+%{_datadir}/artifacts
%files validator
-%defattr(-,root,root)
-%doc ACKNOWLEDGEMENTS AUTHORS LICENSE README
+%license LICENSE
%{python_sitelib}/artifacts-%{timestamp}-py2.7.egg-info
%{python_sitelib}/artifacts
-/usr/bin/validator.py
+%{_bindir}/validator.py
+%{_bindir}/stats.py
%changelog
++++++ artifacts-20150409.tar.gz -> artifacts-20180628.tar.gz ++++++
++++ 12420 lines of diff (skipped)
