Accepted sleuthkit 4.6.0-1 (source) into unstable

[Hilko Bengen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 31 Mar 2018 19:15:06 +0200
Source: sleuthkit
Binary: sleuthkit libtsk13 libtsk-dev
Architecture: source
Version: 4.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools <team+pkg-secur...@tracker.debian.org>
Changed-By: Hilko Bengen <ben...@debian.org>
Description:
 libtsk-dev - library for forensics analysis (development files)
 libtsk13   - library for forensics analysis on volume and filesystem data
 sleuthkit  - tools for forensics analysis on volume and filesystem data
Changes:
 sleuthkit (4.6.0-1) unstable; urgency=medium
 .
   * Team upload
   [ Raphaël Hertzog ]
   * Update team maintainer address to Debian Security Tools
 <team+pkg-secur...@tracker.debian.org>
   * Update Vcs-Git and Vcs-Browser for the move to salsa.debian.org
 .
   [ Hilko Bengen ]
   * New upstream version 4.6.0
   * Bump Standards-Version
   * Drop CVE-* patches that have been integrated upstream
   * Update .symbols file
Checksums-Sha1:
 efe426dde3c314ad583c136e2e6aa170e9bc1f68 2110 sleuthkit_4.6.0-1.dsc
 3a77931cb8fc67b2b419bd77e39b18d7db426521 9109116 sleuthkit_4.6.0.orig.tar.gz
 cb93ba3583b64d754ea59174f001a86920706ce6 36596 sleuthkit_4.6.0-1.debian.tar.xz
 57343c17e07e34bc87efcd94bdd5ca4d675952d2 6920 
sleuthkit_4.6.0-1_source.buildinfo
Checksums-Sha256:
 d51c0e900eac6988d51024b06957ce33f4f88a21ff9ebaa755bd389f79b7b780 2110 
sleuthkit_4.6.0-1.dsc
 ad3e26958234c9e866dfbfb751bcd6ed300ff76446dc6767a6f9083df4bf4974 9109116 
sleuthkit_4.6.0.orig.tar.gz
 7674b681b6cc8006512cecf866ba8a440a64183a34b0875c084b2bc5de9bd04d 36596 
sleuthkit_4.6.0-1.debian.tar.xz
 a2f12643d270193c5fe1c7cdb04a24ea4b22fd670b9d832e283f78e076f628cb 6920 
sleuthkit_4.6.0-1_source.buildinfo
Files:
 95851e0527324b0178f304250cd03a12 2110 admin optional sleuthkit_4.6.0-1.dsc
 b94388c5f9de8a9f017619f4855f4401 9109116 admin optional 
sleuthkit_4.6.0.orig.tar.gz
 4fc7614bde96e9d3c5d843fc193ce0bf 36596 admin optional 
sleuthkit_4.6.0-1.debian.tar.xz
 aa64274fc709d9416d71d40434dea77d 6920 admin optional 
sleuthkit_4.6.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAlq/xbwACgkQdbcQY1wh
On5xog/9He9gsjH3FHEHrDzNrge5JOAkawxR3Ak3IgzL3XIkmFlwCrwdbIw6RQCp
ILL9L2iMVMM6aSqrXPrpaaxNDq/BxST7YBvMbiGmJ20KKU0cXDlYYxaJ8j8Yx4JA
VrgaXuzD5F5iHWSCZHMG1dNM3VyMvlH/IUAcz5bMimBqVBoIU2Gb6UxFQOTeBuo+
s7MWmL5H4+l+vf2KXa7aeHshArGSAdTDtUfEdLwFK45E1IxIL8mbWhbHTQkrpC7a
M+2lRMq2U2FsHanYHNbbPEfNh1udLENssTl1dEGongfuPPceYdj9RUa4CSC6RB2K
81E+MnER7SOjWhEQAHiEbas1fDMabCbWKRoJiCwPsaoZxthcfy91Ik0Ye4UdE9Y6
r8BGC0obOI1lF+DfDKvXMwLkA5QiykTtn3hmyPPducT4Z1cO1JiYs6Fjak44EZa9
4/+HPEu+Go0poBS7BD8EmC9hWLMR7IE0eMyKwqm/J95tUm9QJy2crDZcX3mvXyH8
rHnkFGcxp20RWbtpJoJzZ5zo74dI9zwWrBtdngIpSMxPVMGZlCLVh67znorNeg4/
O2eLfa2EbTLVnMA0lWfP8rdFqkPB7LP+XTTbIk8QNdx05XswoZNUfIkCBldQftqq
+9ppHMhM8Ndd1YGFBj725pdqe4+7as75uEPO9Ryr4Tc0jtsRTt4=
=ZsmA
-END PGP SIGNATURE-


___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

sleuthkit 4.4.2-3 MIGRATED to testing

[Debian testing watch]

FYI: The status of the sleuthkit source package
in Debian's testing distribution has changed.

  Previous version: 4.4.2-1
  Current version:  4.4.2-3

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#873726: marked as done (sleuthkit: CVE-2017-13755)

[Debian Bug Tracking System]

Your message dated Tue, 19 Sep 2017 00:05:25 +
with message-id <e1du62x-000dvt...@fasolo.debian.org>
and subject line Bug#873726: fixed in sleuthkit 4.4.2-2
has caused the Debian Bug report #873726,
regarding sleuthkit: CVE-2017-13755
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
873726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sleuthkit
Version: 4.4.2-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/sleuthkit/sleuthkit/issues/913

Hi,

the following vulnerability was published for sleuthkit.

CVE-2017-13755[0]:
| In The Sleuth Kit (TSK) 4.4.2, opening a crafted ISO 9660 image
| triggers an out-of-bounds read in iso9660_proc_dir() in
| tsk/fs/iso9660_dent.c in libtskfs.a, as demonstrated by fls.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-13755
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13755
[1] https://github.com/sleuthkit/sleuthkit/issues/913

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: sleuthkit
Source-Version: 4.4.2-2

We believe that the bug you reported is fixed in the latest version of
sleuthkit, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 873...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho <eribe...@debian.org> (supplier of updated sleuthkit 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 18 Sep 2017 19:46:37 -0300
Source: sleuthkit
Binary: sleuthkit libtsk13 libtsk-dev
Architecture: source
Version: 4.4.2-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Forensics <forensics-devel@lists.alioth.debian.org>
Changed-By: Joao Eriberto Mota Filho <eribe...@debian.org>
Description:
 libtsk-dev - library for forensics analysis (development files)
 libtsk13   - library for forensics analysis on volume and filesystem data
 sleuthkit  - tools for forensics analysis on volume and filesystem data
Closes: 873724 873725 873726
Changes:
 sleuthkit (4.4.2-2) experimental; urgency=medium
 .
   * Added new patches to solve CVE's:
   - 70_fix-CVE-2017-13760.patch, for CVE-2017-13760. (Closes: #873724)
   - 80_fix-CVE-2017-13756.patch, for CVE-2017-13756. (Closes: #873725)
   - 90_fix-CVE-2017-13755.patch, for CVE-2017-13755. (Closes: #873726)
Checksums-Sha1:
 a799ebe51f633f33f6a2aa7dd4bb93d4d00a8f0c 2108 sleuthkit_4.4.2-2.dsc
 5e1da7ead409dbd922b316dbfb04aa12f2675228 37100 sleuthkit_4.4.2-2.debian.tar.xz
 6c3d6d61a50865e2bd328279e0200948e1bf6288 5918 
sleuthkit_4.4.2-2_source.buildinfo
Checksums-Sha256:
 67af112f79ee8579455c198794ef467b857d4e0d1696d6fd5e387de5ba03bdc9 2108 
sleuthkit_4.4.2-2.dsc
 ab92446dcc40dbc20a4e7ef0cf9f015f5ca320f13f9228ea9e030f308c1638a5 37100 
sleuthkit_4.4.2-2.debian.tar.xz
 c8cc8a9e311cd980d59e0b1ac2d9142d6ce53ff6c6888eae6cfdd0607597cee8 5918 
sleuthkit_4.4.2-2_source.buildinfo
Files:
 f9ee6abaaefcefb6f24758fcf5cec9c4 2108 admin optional sleuthkit_4.4.2-2.dsc
 96a1d214f8ff7b28dede840464143e6e 37100 admin optional 
sleuthkit_4.4.2-2.debian.tar.xz
 0c5d454ab3da088c313bbfd6778cd604 5918 admin optional 
sleuthkit_4.4.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlnAWRUACgkQ3mO5xwTr
6e9xYA//XqfpZWHNrox27VaM//HRnsfgVvoD6fi/cwLkRQxhJOvAALUQOSa2ImRP
uiejXxHRXx57900o2/K4ZfC0tLQ0vU0LWEuAkw3DIFLOkCUhA31BBSWyCFmUzdHa
qMEMtOVcgdMBjL34HBLQo8I1AhJMvi+kji7sDRbH401k4hdl1orZKljYhWkc24kB
OyyXgdkrK7RIkppmxzvBRiXzR+X4595uQJ0f4Hoh2DyS1rvEf70aWj36LgWIbrYF
X+lvYpiDAXEDKRdg7R20334VY5ibUXko9BdXwlIT+1ugTZC4WmhiYI5kJwXeF7kB
sRVryiJzx9vw6svV2n0Wm5iXGDYClGYY1jVGfBZlXnxF0OpZcVsVnvOYaGwd5iKD
k0E/m8ZRu9OEUtiJ0ZhgmcOrTAaC3Jq/JRScYrHDOCfLRwl86yVIAoveZYV2eD3i
T9oqVhBAf8bbMIgdoShHpmGChYNGoaP1hiqg7HtjjyB1983v9u1ZaAs6wTncpRDB
0whKf0HH0bB6EkeUsjxIU3MJYIMJIDdM4tYNzADT/fsUgTYNA

Bug#873725: marked as done (sleuthkit: CVE-2017-13756)

[Debian Bug Tracking System]

Your message dated Tue, 19 Sep 2017 00:05:25 +
with message-id <e1du62x-000dvl...@fasolo.debian.org>
and subject line Bug#873725: fixed in sleuthkit 4.4.2-2
has caused the Debian Bug report #873725,
regarding sleuthkit: CVE-2017-13756
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
873725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sleuthkit
Version: 4.4.2-1
Severity: important
Tags: upstream security
Forwarded: https://github.com/sleuthkit/sleuthkit/issues/914

Hi,

the following vulnerability was published for sleuthkit.

CVE-2017-13756[0]:
| In The Sleuth Kit (TSK) 4.4.2, opening a crafted disk image triggers
| infinite recursion in dos_load_ext_table() in tsk/vs/dos.c in
| libtskvs.a, as demonstrated by mmls.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-13756
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13756
[1] https://github.com/sleuthkit/sleuthkit/issues/914

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: sleuthkit
Source-Version: 4.4.2-2

We believe that the bug you reported is fixed in the latest version of
sleuthkit, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 873...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho <eribe...@debian.org> (supplier of updated sleuthkit 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 18 Sep 2017 19:46:37 -0300
Source: sleuthkit
Binary: sleuthkit libtsk13 libtsk-dev
Architecture: source
Version: 4.4.2-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Forensics <forensics-devel@lists.alioth.debian.org>
Changed-By: Joao Eriberto Mota Filho <eribe...@debian.org>
Description:
 libtsk-dev - library for forensics analysis (development files)
 libtsk13   - library for forensics analysis on volume and filesystem data
 sleuthkit  - tools for forensics analysis on volume and filesystem data
Closes: 873724 873725 873726
Changes:
 sleuthkit (4.4.2-2) experimental; urgency=medium
 .
   * Added new patches to solve CVE's:
   - 70_fix-CVE-2017-13760.patch, for CVE-2017-13760. (Closes: #873724)
   - 80_fix-CVE-2017-13756.patch, for CVE-2017-13756. (Closes: #873725)
   - 90_fix-CVE-2017-13755.patch, for CVE-2017-13755. (Closes: #873726)
Checksums-Sha1:
 a799ebe51f633f33f6a2aa7dd4bb93d4d00a8f0c 2108 sleuthkit_4.4.2-2.dsc
 5e1da7ead409dbd922b316dbfb04aa12f2675228 37100 sleuthkit_4.4.2-2.debian.tar.xz
 6c3d6d61a50865e2bd328279e0200948e1bf6288 5918 
sleuthkit_4.4.2-2_source.buildinfo
Checksums-Sha256:
 67af112f79ee8579455c198794ef467b857d4e0d1696d6fd5e387de5ba03bdc9 2108 
sleuthkit_4.4.2-2.dsc
 ab92446dcc40dbc20a4e7ef0cf9f015f5ca320f13f9228ea9e030f308c1638a5 37100 
sleuthkit_4.4.2-2.debian.tar.xz
 c8cc8a9e311cd980d59e0b1ac2d9142d6ce53ff6c6888eae6cfdd0607597cee8 5918 
sleuthkit_4.4.2-2_source.buildinfo
Files:
 f9ee6abaaefcefb6f24758fcf5cec9c4 2108 admin optional sleuthkit_4.4.2-2.dsc
 96a1d214f8ff7b28dede840464143e6e 37100 admin optional 
sleuthkit_4.4.2-2.debian.tar.xz
 0c5d454ab3da088c313bbfd6778cd604 5918 admin optional 
sleuthkit_4.4.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlnAWRUACgkQ3mO5xwTr
6e9xYA//XqfpZWHNrox27VaM//HRnsfgVvoD6fi/cwLkRQxhJOvAALUQOSa2ImRP
uiejXxHRXx57900o2/K4ZfC0tLQ0vU0LWEuAkw3DIFLOkCUhA31BBSWyCFmUzdHa
qMEMtOVcgdMBjL34HBLQo8I1AhJMvi+kji7sDRbH401k4hdl1orZKljYhWkc24kB
OyyXgdkrK7RIkppmxzvBRiXzR+X4595uQJ0f4Hoh2DyS1rvEf70aWj36LgWIbrYF
X+lvYpiDAXEDKRdg7R20334VY5ibUXko9BdXwlIT+1ugTZC4WmhiYI5kJwXeF7kB
sRVryiJzx9vw6svV2n0Wm5iXGDYClGYY1jVGfBZlXnxF0OpZcVsVnvOYaGwd5iKD
k0E/m8ZRu9OEUtiJ0ZhgmcOrTAaC3Jq/JRScYrHDOCfLRwl86yVIAoveZYV2eD3i
T9oqVhBAf8bbMIgdoShHpmGChYNGoaP1hiqg7HtjjyB1983v9u1ZaAs6wTncpRDB
0whKf0HH0bB6EkeUsjxIU3MJYIMJIDdM4tYNzADT/fsUgTYNA

Bug#873724: marked as done (sleuthkit: CVE-2017-13760)

[Debian Bug Tracking System]

Your message dated Tue, 19 Sep 2017 00:05:25 +
with message-id <e1du62x-000dvf...@fasolo.debian.org>
and subject line Bug#873724: fixed in sleuthkit 4.4.2-2
has caused the Debian Bug report #873724,
regarding sleuthkit: CVE-2017-13760
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
873724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873724
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sleuthkit
Version: 4.4.2-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/sleuthkit/sleuthkit/issues/906

Hi,

the following vulnerability was published for sleuthkit.

CVE-2017-13760[0]:
| In The Sleuth Kit (TSK) 4.4.2, fls hangs on a corrupt exfat image in
| tsk_img_read() in tsk/img/img_io.c in libtskimg.a.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-13760
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13760
[1] https://github.com/sleuthkit/sleuthkit/issues/906

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: sleuthkit
Source-Version: 4.4.2-2

We believe that the bug you reported is fixed in the latest version of
sleuthkit, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 873...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho <eribe...@debian.org> (supplier of updated sleuthkit 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 18 Sep 2017 19:46:37 -0300
Source: sleuthkit
Binary: sleuthkit libtsk13 libtsk-dev
Architecture: source
Version: 4.4.2-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Forensics <forensics-devel@lists.alioth.debian.org>
Changed-By: Joao Eriberto Mota Filho <eribe...@debian.org>
Description:
 libtsk-dev - library for forensics analysis (development files)
 libtsk13   - library for forensics analysis on volume and filesystem data
 sleuthkit  - tools for forensics analysis on volume and filesystem data
Closes: 873724 873725 873726
Changes:
 sleuthkit (4.4.2-2) experimental; urgency=medium
 .
   * Added new patches to solve CVE's:
   - 70_fix-CVE-2017-13760.patch, for CVE-2017-13760. (Closes: #873724)
   - 80_fix-CVE-2017-13756.patch, for CVE-2017-13756. (Closes: #873725)
   - 90_fix-CVE-2017-13755.patch, for CVE-2017-13755. (Closes: #873726)
Checksums-Sha1:
 a799ebe51f633f33f6a2aa7dd4bb93d4d00a8f0c 2108 sleuthkit_4.4.2-2.dsc
 5e1da7ead409dbd922b316dbfb04aa12f2675228 37100 sleuthkit_4.4.2-2.debian.tar.xz
 6c3d6d61a50865e2bd328279e0200948e1bf6288 5918 
sleuthkit_4.4.2-2_source.buildinfo
Checksums-Sha256:
 67af112f79ee8579455c198794ef467b857d4e0d1696d6fd5e387de5ba03bdc9 2108 
sleuthkit_4.4.2-2.dsc
 ab92446dcc40dbc20a4e7ef0cf9f015f5ca320f13f9228ea9e030f308c1638a5 37100 
sleuthkit_4.4.2-2.debian.tar.xz
 c8cc8a9e311cd980d59e0b1ac2d9142d6ce53ff6c6888eae6cfdd0607597cee8 5918 
sleuthkit_4.4.2-2_source.buildinfo
Files:
 f9ee6abaaefcefb6f24758fcf5cec9c4 2108 admin optional sleuthkit_4.4.2-2.dsc
 96a1d214f8ff7b28dede840464143e6e 37100 admin optional 
sleuthkit_4.4.2-2.debian.tar.xz
 0c5d454ab3da088c313bbfd6778cd604 5918 admin optional 
sleuthkit_4.4.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlnAWRUACgkQ3mO5xwTr
6e9xYA//XqfpZWHNrox27VaM//HRnsfgVvoD6fi/cwLkRQxhJOvAALUQOSa2ImRP
uiejXxHRXx57900o2/K4ZfC0tLQ0vU0LWEuAkw3DIFLOkCUhA31BBSWyCFmUzdHa
qMEMtOVcgdMBjL34HBLQo8I1AhJMvi+kji7sDRbH401k4hdl1orZKljYhWkc24kB
OyyXgdkrK7RIkppmxzvBRiXzR+X4595uQJ0f4Hoh2DyS1rvEf70aWj36LgWIbrYF
X+lvYpiDAXEDKRdg7R20334VY5ibUXko9BdXwlIT+1ugTZC4WmhiYI5kJwXeF7kB
sRVryiJzx9vw6svV2n0Wm5iXGDYClGYY1jVGfBZlXnxF0OpZcVsVnvOYaGwd5iKD
k0E/m8ZRu9OEUtiJ0ZhgmcOrTAaC3Jq/JRScYrHDOCfLRwl86yVIAoveZYV2eD3i
T9oqVhBAf8bbMIgdoShHpmGChYNGoaP1hiqg7HtjjyB1983v9u1ZaAs6wTncpRDB
0whKf0HH0bB6EkeUsjxIU3MJYIMJIDdM4tYNzADT/fsUgTYNAOOmDWHkm8cfeaqR
JChn+F4msZD9/TdHcKeQfM3vJtgjuG7SV5VOiRS

sleuthkit is marked for autoremoval from testing

[Debian testing autoremoval watch]

sleuthkit 4.4.2-1 is marked for autoremoval from testing on 2017-10-10

It is affected by these RC bugs:
873374: libtsk13: libtsk13 4.4.2-1 crash in the dfvfs test suite


___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#873726: sleuthkit: CVE-2017-13755

[Salvatore Bonaccorso]

Source: sleuthkit
Version: 4.4.2-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/sleuthkit/sleuthkit/issues/913

Hi,

the following vulnerability was published for sleuthkit.

CVE-2017-13755[0]:
| In The Sleuth Kit (TSK) 4.4.2, opening a crafted ISO 9660 image
| triggers an out-of-bounds read in iso9660_proc_dir() in
| tsk/fs/iso9660_dent.c in libtskfs.a, as demonstrated by fls.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-13755
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13755
[1] https://github.com/sleuthkit/sleuthkit/issues/913

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#873725: sleuthkit: CVE-2017-13756

[Salvatore Bonaccorso]

Source: sleuthkit
Version: 4.4.2-1
Severity: important
Tags: upstream security
Forwarded: https://github.com/sleuthkit/sleuthkit/issues/914

Hi,

the following vulnerability was published for sleuthkit.

CVE-2017-13756[0]:
| In The Sleuth Kit (TSK) 4.4.2, opening a crafted disk image triggers
| infinite recursion in dos_load_ext_table() in tsk/vs/dos.c in
| libtskvs.a, as demonstrated by mmls.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-13756
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13756
[1] https://github.com/sleuthkit/sleuthkit/issues/914

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#873724: sleuthkit: CVE-2017-13760

[Salvatore Bonaccorso]

Source: sleuthkit
Version: 4.4.2-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/sleuthkit/sleuthkit/issues/906

Hi,

the following vulnerability was published for sleuthkit.

CVE-2017-13760[0]:
| In The Sleuth Kit (TSK) 4.4.2, fls hangs on a corrupt exfat image in
| tsk_img_read() in tsk/img/img_io.c in libtskimg.a.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-13760
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13760
[1] https://github.com/sleuthkit/sleuthkit/issues/906

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

sleuthkit 4.4.2-1 MIGRATED to testing

[Debian testing watch]

FYI: The status of the sleuthkit source package
in Debian's testing distribution has changed.

  Previous version: 4.4.0-6
  Current version:  4.4.2-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

sleuthkit 4.4.0-6 MIGRATED to testing

[Debian testing watch]

FYI: The status of the sleuthkit source package
in Debian's testing distribution has changed.

  Previous version: 4.4.0-5
  Current version:  4.4.0-6

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#853663: marked as done (sleuthkit: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Tue, 08 Aug 2017 22:36:23 +
with message-id <e1dfd6t-0007mx...@fasolo.debian.org>
and subject line Bug#853663: fixed in sleuthkit 4.4.0-6
has caused the Debian Bug report #853663,
regarding sleuthkit: ftbfs with GCC-7
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
853663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sleuthkit
Version: 4.4.0-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/sleuthkit_4.4.0-2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
+ _ZTVSt13bad_exception@Base 4.4.0
+ _ZTVSt9bad_alloc@Base 4.4.0
+ _ZTVSt9exception@Base 4.4.0
+ _ZTVSt9type_info@Base 4.4.0
+ _ZdlPv@Base 4.4.0
+ _ZdlPvm@Base 4.4.0
+ _ZlsRSoRK4Guid@Base 4.4.0
+ _Znwm@Base 4.4.0
  __cxa_allocate_dependent_exception@Base 4.2.0
  __cxa_allocate_exception@Base 4.2.0
  __cxa_begin_catch@Base 4.2.0
@@ -131,6 +300,7 @@
  __cxa_get_exception_ptr@Base 4.2.0
  __cxa_get_globals@Base 4.2.0
  __cxa_get_globals_fast@Base 4.2.0
+ __cxa_init_primary_exception@Base 4.4.0
  __cxa_pure_virtual@Base 4.2.0
  __cxa_rethrow@Base 4.2.0
  __cxa_throw@Base 4.2.0
@@ -591,15 +761,15 @@
  (c++)"typeinfo name for std::exception@Base" 4.2.0
  (c++)"typeinfo name for std::type_info@Base" 4.2.0
  (c++)"void 
std::__insertion_sort<__gnu_cxx::__normal_iterator<_TSK_DB_FILE_LAYOUT_RANGE*, 
std::vector<_TSK_DB_FILE_LAYOUT_RANGE, 
std::allocator<_TSK_DB_FILE_LAYOUT_RANGE> > >, 
__gnu_cxx::__ops::_Iter_less_iter>(__gnu_cxx::__normal_iterator<_TSK_DB_FILE_LAYOUT_RANGE*,
 std::vector<_TSK_DB_FILE_LAYOUT_RANGE, 
std::allocator<_TSK_DB_FILE_LAYOUT_RANGE> > >, 
__gnu_cxx::__normal_iterator<_TSK_DB_FILE_LAYOUT_RANGE*, 
std::vector<_TSK_DB_FILE_LAYOUT_RANGE, 
std::allocator<_TSK_DB_FILE_LAYOUT_RANGE> > >, 
__gnu_cxx::__ops::_Iter_less_iter)@Base" 4.2.0
- (c++)"void std::vector<NTFS_META_ADDR, std::allocator 
>::_M_emplace_back_aux(NTFS_META_ADDR const&)@Base" 4.3.0
- (c++)"void std::vector<TskAuto::error_record, 
std::allocator 
>::_M_emplace_back_aux(TskAuto::error_record 
const&)@Base" 4.3.0
- (c++)"void std::vector<_TSK_DB_FILE_LAYOUT_RANGE, 
std::allocator<_TSK_DB_FILE_LAYOUT_RANGE> 
>::_M_emplace_back_aux<_TSK_DB_FILE_LAYOUT_RANGE 
const&>(_TSK_DB_FILE_LAYOUT_RANGE const&)@Base" 4.3.0
- (c++)"void std::vector<_TSK_DB_FILE_LAYOUT_RANGE, 
std::allocator<_TSK_DB_FILE_LAYOUT_RANGE> 
>::_M_emplace_back_aux<_TSK_DB_FILE_LAYOUT_RANGE>(_TSK_DB_FILE_LAYOUT_RANGE&&)@Base"
 4.3.0
+#MISSING: 4.4.0# (c++)"void std::vector<NTFS_META_ADDR, 
std::allocator >::_M_emplace_back_aux(NTFS_META_ADDR const&)@Base" 4.3.0
+#MISSING: 4.4.0# (c++)"void std::vector<TskAuto::error_record, 
std::allocator 
>::_M_emplace_back_aux(TskAuto::error_record 
const&)@Base" 4.3.0
+#MISSING: 4.4.0# (c++)"void std::vector<_TSK_DB_FILE_LAYOUT_RANGE, 
std::allocator<_TSK_DB_FILE_LAYOUT_RANGE> 
>::_M_emplace_back_aux<_TSK_DB_FILE_LAYOUT_RANGE 
const&>(_TSK_DB_FILE_LAYOUT_RANGE const&)@Base" 4.3.0
+#MISSING: 4.4.0# (c++)"void std::vector<_TSK_DB_FILE_LAYOUT_RANGE, 
std::allocator<_TSK_DB_FILE_LAYOUT_RANGE> 
>::_M_emplace_back_aux<_TSK_DB_FILE_LAYOU

Bug#860223: marked as done (sleuthkit: please adjust symbols file for compatibility with -O3)

[Debian Bug Tracking System]

Your message dated Tue, 08 Aug 2017 22:36:23 +
with message-id <e1dfd6t-0007n3...@fasolo.debian.org>
and subject line Bug#860223: fixed in sleuthkit 4.4.0-6
has caused the Debian Bug report #860223,
regarding sleuthkit: please adjust symbols file for compatibility with -O3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
860223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sleuthkit
Version: 4.4.0-2
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu zesty ubuntu-patch

Dear maintainer,

In Ubuntu, the latest upload of sleuthkit was failing to build on ppc64el
because the Ubuntu ppc64el architecture uses -O3 optimization by default,
which causes one symbol listed in your libtsk13.symbols file to be inlined
instead.  In order to fix this build failure, I have applied the attached
patch which marks that symbol as optional, and also adds a number of other
symbols that showed up in the build log as added.  The added symbols
probably have nothing to do with -O3, and may not be related to ppc64el
either - they may be newer symbols that are added across all architectures
and therefore should not be marked as optional at all.

Please consider applying the attached patch (or a variant) to make sleuthkit
portable to building with -O3.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru sleuthkit-4.4.0/debian/libtsk13.symbols sleuthkit-4.4.0/debian/libtsk13.symbols
--- sleuthkit-4.4.0/debian/libtsk13.symbols	2017-01-24 16:30:19.0 -0800
+++ sleuthkit-4.4.0/debian/libtsk13.symbols	2017-04-12 16:29:42.0 -0700
@@ -129,6 +129,152 @@
  (c++)"tsk_fs_jentry_cpp_c_cb(TSK_FS_INFO*, TSK_FS_JENTRY*, int, void*)@Base" 4.2.0
  (c++)"tsk_fs_meta_walk_cpp_c_cb(TSK_FS_FILE*, void*)@Base" 4.2.0
  (c++)"TskHashInfo::~TskHashInfo()@Base" 4.2.0
+ (c++|optional)"tsk_fs_file_cpp_c_cb(TSK_FS_FILE*, long, unsigned long, char*, unsigned long, TSK_FS_BLOCK_FLAG_ENUM, void*)@Base" 4.4.0
+ (c++|optional)"transaction clone for std::bad_exception::what() const@Base" 4.4.0
+ (c++|optional)"transaction clone for std::bad_exception::~bad_exception() const@Base" 4.4.0
+ (c++|optional)"transaction clone for std::exception::what() const@Base" 4.4.0
+ (c++|optional)"transaction clone for std::exception::~exception() const@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__terminate(void (*)())@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__unexpected(void (*)())@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__forced_unwind::~__forced_unwind()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__forced_unwind::~__forced_unwind()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__forced_unwind::~__forced_unwind()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__class_type_info::~__class_type_info()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__class_type_info::~__class_type_info()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__class_type_info::~__class_type_info()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__foreign_exception::~__foreign_exception()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__foreign_exception::~__foreign_exception()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__foreign_exception::~__foreign_exception()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__terminate_handler@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__si_class_type_info::~__si_class_type_info()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__si_class_type_info::~__si_class_type_info()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__si_class_type_info::~__si_class_type_info()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__unexpected_handler@Base" 4.4.0
+ (c++|optional)"TskDbSqlite::getFsInfos(long, std::vector<_TSK_DB_FS_INFO, std::allocator<_TSK_DB_FS_INFO> >&)@Base" 4.4.0
+ (c++|optional)"TskDbSqlite::getVsInfos(long, std::vector<_TSK_DB_VS_INFO, std::allocator<_TSK_DB_VS_INFO> >&)@Base" 4.4.0
+ (c++|optional)"TskDbSqlite::storeObjId(long const&, TSK_FS_FILE const*, char const*, long const&)@Base" 4.4.0
+ (c++|optional)"TskDbS

sleuthkit is marked for autoremoval from testing

[Debian testing autoremoval watch]

sleuthkit 4.4.0-5 is marked for autoremoval from testing on 2017-09-04

It is affected by these RC bugs:
853663: sleuthkit: ftbfs with GCC-7


___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#860223: sleuthkit: please adjust symbols file for compatibility with -O3

[Steve Langasek]

Package: sleuthkit
Version: 4.4.0-5
Followup-For: Bug #860223
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch

Hello,

It appears the symbols file refactoring between 4.4.0-2 and 4.4.0-5 means
much fewer changes are now needed for -O3 compatibility.  Please find
attached a patch for the remaining one-line change.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru sleuthkit-4.4.0/debian/libtsk13.symbols 
sleuthkit-4.4.0/debian/libtsk13.symbols
--- sleuthkit-4.4.0/debian/libtsk13.symbols 2017-02-19 12:44:19.0 
-0800
+++ sleuthkit-4.4.0/debian/libtsk13.symbols 2017-04-28 07:28:53.0 
-0700
@@ -163,7 +163,7 @@
  (c++)"void std::vector<NTFS_META_ADDR, std::allocator 
>::_M_emplace_back_aux(NTFS_META_ADDR const&)@Base" 4.3.0
  (c++)"void std::vector<std::__cxx11::basic_string<char, 
std::char_traits, std::allocator >, 
std::allocator<std::__cxx11::basic_string<char, std::char_traits, 
std::allocator > > 
>::_M_emplace_back_aux<std::__cxx11::basic_string<char, std::char_traits, 
std::allocator > >(std::__cxx11::basic_string<char, 
std::char_traits, std::allocator >&&)@Base" 4.3.0
  (c++)"void std::vector<TskAuto::error_record, 
std::allocator 
>::_M_emplace_back_aux(TskAuto::error_record 
const&)@Base" 4.3.0
- (c++)"void std::vector<_TSK_DB_FILE_LAYOUT_RANGE, 
std::allocator<_TSK_DB_FILE_LAYOUT_RANGE> 
>::emplace_back<_TSK_DB_FILE_LAYOUT_RANGE>(_TSK_DB_FILE_LAYOUT_RANGE&&)@Base" 
4.3.0
+ (c++|optional)"void std::vector<_TSK_DB_FILE_LAYOUT_RANGE, 
std::allocator<_TSK_DB_FILE_LAYOUT_RANGE> 
>::emplace_back<_TSK_DB_FILE_LAYOUT_RANGE>(_TSK_DB_FILE_LAYOUT_RANGE&&)@Base" 
4.3.0
  (c++)"void std::vector<_TSK_DB_FILE_LAYOUT_RANGE, 
std::allocator<_TSK_DB_FILE_LAYOUT_RANGE> 
>::_M_emplace_back_aux<_TSK_DB_FILE_LAYOUT_RANGE 
const&>(_TSK_DB_FILE_LAYOUT_RANGE const&)@Base" 4.3.0
  (c++)"void std::vector<_TSK_DB_FILE_LAYOUT_RANGE, 
std::allocator<_TSK_DB_FILE_LAYOUT_RANGE> 
>::_M_emplace_back_aux<_TSK_DB_FILE_LAYOUT_RANGE>(_TSK_DB_FILE_LAYOUT_RANGE&&)@Base"
 4.3.0
  (c++)"void std::vector<_TSK_DB_FS_INFO, std::allocator<_TSK_DB_FS_INFO> 
>::_M_emplace_back_aux<_TSK_DB_FS_INFO const&>(_TSK_DB_FS_INFO const&)@Base" 
4.3.0
___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#860223: sleuthkit: please adjust symbols file for compatibility with -O3

[Steve Langasek]

Package: sleuthkit
Version: 4.4.0-2
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu zesty ubuntu-patch

Dear maintainer,

In Ubuntu, the latest upload of sleuthkit was failing to build on ppc64el
because the Ubuntu ppc64el architecture uses -O3 optimization by default,
which causes one symbol listed in your libtsk13.symbols file to be inlined
instead.  In order to fix this build failure, I have applied the attached
patch which marks that symbol as optional, and also adds a number of other
symbols that showed up in the build log as added.  The added symbols
probably have nothing to do with -O3, and may not be related to ppc64el
either - they may be newer symbols that are added across all architectures
and therefore should not be marked as optional at all.

Please consider applying the attached patch (or a variant) to make sleuthkit
portable to building with -O3.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru sleuthkit-4.4.0/debian/libtsk13.symbols sleuthkit-4.4.0/debian/libtsk13.symbols
--- sleuthkit-4.4.0/debian/libtsk13.symbols	2017-01-24 16:30:19.0 -0800
+++ sleuthkit-4.4.0/debian/libtsk13.symbols	2017-04-12 16:29:42.0 -0700
@@ -129,6 +129,152 @@
  (c++)"tsk_fs_jentry_cpp_c_cb(TSK_FS_INFO*, TSK_FS_JENTRY*, int, void*)@Base" 4.2.0
  (c++)"tsk_fs_meta_walk_cpp_c_cb(TSK_FS_FILE*, void*)@Base" 4.2.0
  (c++)"TskHashInfo::~TskHashInfo()@Base" 4.2.0
+ (c++|optional)"tsk_fs_file_cpp_c_cb(TSK_FS_FILE*, long, unsigned long, char*, unsigned long, TSK_FS_BLOCK_FLAG_ENUM, void*)@Base" 4.4.0
+ (c++|optional)"transaction clone for std::bad_exception::what() const@Base" 4.4.0
+ (c++|optional)"transaction clone for std::bad_exception::~bad_exception() const@Base" 4.4.0
+ (c++|optional)"transaction clone for std::exception::what() const@Base" 4.4.0
+ (c++|optional)"transaction clone for std::exception::~exception() const@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__terminate(void (*)())@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__unexpected(void (*)())@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__forced_unwind::~__forced_unwind()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__forced_unwind::~__forced_unwind()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__forced_unwind::~__forced_unwind()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__class_type_info::~__class_type_info()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__class_type_info::~__class_type_info()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__class_type_info::~__class_type_info()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__foreign_exception::~__foreign_exception()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__foreign_exception::~__foreign_exception()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__foreign_exception::~__foreign_exception()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__terminate_handler@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__si_class_type_info::~__si_class_type_info()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__si_class_type_info::~__si_class_type_info()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__si_class_type_info::~__si_class_type_info()@Base" 4.4.0
+ (c++|optional)"__cxxabiv1::__unexpected_handler@Base" 4.4.0
+ (c++|optional)"TskDbSqlite::getFsInfos(long, std::vector<_TSK_DB_FS_INFO, std::allocator<_TSK_DB_FS_INFO> >&)@Base" 4.4.0
+ (c++|optional)"TskDbSqlite::getVsInfos(long, std::vector<_TSK_DB_VS_INFO, std::allocator<_TSK_DB_VS_INFO> >&)@Base" 4.4.0
+ (c++|optional)"TskDbSqlite::storeObjId(long const&, TSK_FS_FILE const*, char const*, long const&)@Base" 4.4.0
+ (c++|optional)"TskDbSqlite::addImageInfo(int, int, long&, std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&)@Base" 4.4.0
+ (c++|optional)"TskDbSqlite::addImageInfo(int, int, long&, std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&, long, std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&)@Base" 4.4.0
+ (c++|optional)"TskDbSqlite::addImageInfo(int, long, long&, std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&, long, std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&, std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&)@Base" 4.4.0
+ (c++|optional)"TskDbSqlite::addImageName(long, char const*, int)@Base" 4.4.0
+ (c++|optional)&quo

sleuthkit 4.4.0-2 MIGRATED to testing

[Debian testing watch]

FYI: The status of the sleuthkit source package
in Debian's testing distribution has changed.

  Previous version: 4.3.1-2
  Current version:  4.4.0-2

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#853663: sleuthkit: ftbfs with GCC-7

[Matthias Klose]

Package: src:sleuthkit
Version: 4.4.0-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/sleuthkit_4.4.0-2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
+ _ZTVSt13bad_exception@Base 4.4.0
+ _ZTVSt9bad_alloc@Base 4.4.0
+ _ZTVSt9exception@Base 4.4.0
+ _ZTVSt9type_info@Base 4.4.0
+ _ZdlPv@Base 4.4.0
+ _ZdlPvm@Base 4.4.0
+ _ZlsRSoRK4Guid@Base 4.4.0
+ _Znwm@Base 4.4.0
  __cxa_allocate_dependent_exception@Base 4.2.0
  __cxa_allocate_exception@Base 4.2.0
  __cxa_begin_catch@Base 4.2.0
@@ -131,6 +300,7 @@
  __cxa_get_exception_ptr@Base 4.2.0
  __cxa_get_globals@Base 4.2.0
  __cxa_get_globals_fast@Base 4.2.0
+ __cxa_init_primary_exception@Base 4.4.0
  __cxa_pure_virtual@Base 4.2.0
  __cxa_rethrow@Base 4.2.0
  __cxa_throw@Base 4.2.0
@@ -591,15 +761,15 @@
  (c++)"typeinfo name for std::exception@Base" 4.2.0
  (c++)"typeinfo name for std::type_info@Base" 4.2.0
  (c++)"void 
std::__insertion_sort<__gnu_cxx::__normal_iterator<_TSK_DB_FILE_LAYOUT_RANGE*, 
std::vector<_TSK_DB_FILE_LAYOUT_RANGE, 
std::allocator<_TSK_DB_FILE_LAYOUT_RANGE> > >, 
__gnu_cxx::__ops::_Iter_less_iter>(__gnu_cxx::__normal_iterator<_TSK_DB_FILE_LAYOUT_RANGE*,
 std::vector<_TSK_DB_FILE_LAYOUT_RANGE, 
std::allocator<_TSK_DB_FILE_LAYOUT_RANGE> > >, 
__gnu_cxx::__normal_iterator<_TSK_DB_FILE_LAYOUT_RANGE*, 
std::vector<_TSK_DB_FILE_LAYOUT_RANGE, 
std::allocator<_TSK_DB_FILE_LAYOUT_RANGE> > >, 
__gnu_cxx::__ops::_Iter_less_iter)@Base" 4.2.0
- (c++)"void std::vector::_M_emplace_back_aux(NTFS_META_ADDR const&)@Base" 4.3.0
- (c++)"void std::vector::_M_emplace_back_aux(TskAuto::error_record 
const&)@Base" 4.3.0
- (c++)"void std::vector<_TSK_DB_FILE_LAYOUT_RANGE, 
std::allocator<_TSK_DB_FILE_LAYOUT_RANGE> 
>::_M_emplace_back_aux<_TSK_DB_FILE_LAYOUT_RANGE 
const&>(_TSK_DB_FILE_LAYOUT_RANGE const&)@Base" 4.3.0
- (c++)"void std::vector<_TSK_DB_FILE_LAYOUT_RANGE, 
std::allocator<_TSK_DB_FILE_LAYOUT_RANGE> 
>::_M_emplace_back_aux<_TSK_DB_FILE_LAYOUT_RANGE>(_TSK_DB_FILE_LAYOUT_RANGE&&)@Base"
 4.3.0
+#MISSING: 4.4.0# (c++)"void std::vector::_M_emplace_back_aux(NTFS_META_ADDR const&)@Base" 4.3.0
+#MISSING: 4.4.0# (c++)"void std::vector::_M_emplace_back_aux(TskAuto::error_record 
const&)@Base" 4.3.0
+#MISSING: 4.4.0# (c++)"void std::vector<_TSK_DB_FILE_LAYOUT_RANGE, 
std::allocator<_TSK_DB_FILE_LAYOUT_RANGE> 
>::_M_emplace_back_aux<_TSK_DB_FILE_LAYOUT_RANGE 
const&>(_TSK_DB_FILE_LAYOUT_RANGE const&)@Base" 4.3.0
+#MISSING: 4.4.0# (c++)"void std::vector<_TSK_DB_FILE_LAYOUT_RANGE, 
std::allocator<_TSK_DB_FILE_LAYOUT_RANGE> 
>::_M_emplace_back_aux<_TSK_DB_FILE_LAYOUT_RANGE>(_TSK_DB_FILE_LAYOUT_RANGE&&)@Base"
 4.3.0
  (c++)"void std::vector<_TSK_DB_FILE_LAYOUT_RANGE, 
std::allocator<_TSK_DB_FILE_LAYOUT_RANGE> 
>::emplace_back<_TSK_DB_FILE_LAYOUT_RANGE>(_TSK_DB_FILE_LAYOUT_RANGE&&)@Base" 
4.3.0
- (c++)"void std::vector<_TSK_DB_FS_INFO, std::allocator<_TSK_DB_FS_INFO> 
>::_M_emplace_back_aux<_TSK_DB_FS_INFO const&>(_TSK_DB_FS_INFO const&)@Base" 
4.3.0
- (c++)"void std::vector<_TSK_DB_VS_INFO, std::allocator<_TSK_DB_VS_INFO> 
>::_M_emplace_back_aux<_TSK_DB_VS_INFO const&>(_TSK_DB_VS_INFO const&)@Base" 
4.3.0
- (c++)"void std::vector<_TSK_DB_VS_PART_INFO, 
std::allocator<_TSK_DB_VS_PART_INFO> 
>::_M_emplace_back_aux<_TSK_DB_VS_PART_INFO const&>(_TSK_DB_VS_PART_INFO 
const&)@Base" 4.3.0
- (c++)"void std::vector, 
std::allocator > 
>::_M_emplace_back_aux >(std::__cxx11::basic_string&&)@Base" 4.3.0
+#MISSING: 4.4.0# (c++)"void std::vector<_TSK_DB_FS_INFO, 

Bug#851872: sleuthkit: New upstream version available

[Eriberto Mota]

2017-01-19 12:07 GMT-02:00 Hilko Bengen <ben...@debian.org>:
> Source: sleuthkit
> Version: 4.3.1-5
> Severity: wishlist
>
> Dear Maintainer,
>
> sleuthkit 4.4.0 has been released. We could still get this released with
> stretch.


Thanks. I will package it soon. Working hard over packit now. However,
TSK 4.4.0 will arrives to Stretch.

Regards,

Eriberto

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#850828: marked as done (sleuthkit: please update symbols file)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2017 19:51:14 +
with message-id <e1ctdjc-000cer...@fasolo.debian.org>
and subject line Bug#850828: fixed in sleuthkit 4.3.1-5
has caused the Debian Bug report #850828,
regarding sleuthkit: please update symbols file
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
850828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sleuthkit
Version: 4.3.1-2
Severity: minor

Dear Maintainer,

while preparing a Jessie backport for 4.3.1 I noticed that the symbols
file for libtsk13 could be improved:

 - C++ symbols are stored in their mangled form, so builds with different
   GCC versions will result in differences in the symbol file content -- I
   noticed this while building a backport with Jessie's GCC
 - symbols for the latest version 4.3.1 are missing, 4.2.0 is the latest
   in the file

Kind regards
Sascha
--- End Message ---
--- Begin Message ---
Source: sleuthkit
Source-Version: 4.3.1-5

We believe that the bug you reported is fixed in the latest version of
sleuthkit, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 850...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho <eribe...@debian.org> (supplier of updated sleuthkit 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 16 Jan 2017 17:16:08 -0200
Source: sleuthkit
Binary: sleuthkit libtsk13 libtsk-dev
Architecture: source
Version: 4.3.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Forensics <forensics-devel@lists.alioth.debian.org>
Changed-By: Joao Eriberto Mota Filho <eribe...@debian.org>
Description:
 libtsk-dev - library for forensics analysis (development files)
 libtsk13   - library for forensics analysis on volume and filesystem data
 sleuthkit  - tools for forensics analysis on volume and filesystem data
Closes: 850828
Changes:
 sleuthkit (4.3.1-5) unstable; urgency=medium
 .
   * Upload to unstable. (Closes: #850828)
   * debian/copyright: updated the packaging copyright years.
Checksums-Sha1:
 a5fb0ea2d2b9ab85cbf08ba5748203362a4fecee 2123 sleuthkit_4.3.1-5.dsc
 99c8a395850709e56b6159f449028ef0802a8e96 36508 sleuthkit_4.3.1-5.debian.tar.xz
Checksums-Sha256:
 8c73a3174c75d96fd6e21e2447e5a7446575ec9878f3d0e157338021f9f78c24 2123 
sleuthkit_4.3.1-5.dsc
 a2575e11993c7f9f1a0b64604d6cdf598e0b4ba2df736b88667fdac924c5eabe 36508 
sleuthkit_4.3.1-5.debian.tar.xz
Files:
 7378051493fe8afc62e5c6057060311a 2123 admin optional sleuthkit_4.3.1-5.dsc
 04fd47c1c6c9caa50917cad9a24c6559 36508 admin optional 
sleuthkit_4.3.1-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlh9HasACgkQ3mO5xwTr
6e9n9A//ZxbGJNuQWvefjdsB6gmIuP39Tzp5TV/RwgkWSdULES1IVuPiRSftEtnI
E9KG80xGb7lpglN/dzPaQ9Z8L2mNbRxeYHkf0KvShIZyhbQzzY62cP2CoLBlGlZx
oz5awPjQ5cRmREV1YSXQhtnzOmCEvQook39WicTFri08ZVzUAizxeCP1R7fDT0Nn
zwMtB6IXcNXEnkOaG90qyh7MewWTVd5Kx4U2twGPx5YUwakvZl8NPKdOT+TLre9j
SLqMtopKmCQz8N1UgbpK9bAnkEZoo0291oDbbG9we3SJdRmtKMTgj1YOmX41NDYp
1cUZDa0biW762u9R6do4TEd34e1DUZfSrwlKvFFqY5hVpaMI7bGVVP09kC+5CDPz
8+u+T+51Kp6vVtSBoOKEI6UTYkRqOwhgK8cEUzB5OIzAnOyUMakbW2hU+nXWcqHB
t3TP5YdakPe/CHwXoyjNjnkaKL91c8DAgJNHGQ6eu8pXf7xAhlwOHGXHEbf8hgmB
i2402B2PM0UdVnPaVMYJfa7OSgTk1IxXu4qchtoM6bFsUfPEk5k2J9e45WJC1CNK
PyR4X8syLw1zqocZ+Nu0ilzEBi2y87qcijsbZxYkXGacC+2s/1qLI9ujxOdAtjGy
j8Cabnt/7LtDvrq/FLS0AW1EcL0upLwVsttI/kum2vhNWOOPXbU=
=ARuX
-END PGP SIGNATURE End Message ---
___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#850828: marked as done (sleuthkit: please update symbols file)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 15:09:34 +
with message-id <e1cs3ty-000agn...@fasolo.debian.org>
and subject line Bug#850828: fixed in sleuthkit 4.3.1-3
has caused the Debian Bug report #850828,
regarding sleuthkit: please update symbols file
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
850828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sleuthkit
Version: 4.3.1-2
Severity: minor

Dear Maintainer,

while preparing a Jessie backport for 4.3.1 I noticed that the symbols
file for libtsk13 could be improved:

 - C++ symbols are stored in their mangled form, so builds with different
   GCC versions will result in differences in the symbol file content -- I
   noticed this while building a backport with Jessie's GCC
 - symbols for the latest version 4.3.1 are missing, 4.2.0 is the latest
   in the file

Kind regards
Sascha
--- End Message ---
--- Begin Message ---
Source: sleuthkit
Source-Version: 4.3.1-3

We believe that the bug you reported is fixed in the latest version of
sleuthkit, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 850...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho <eribe...@debian.org> (supplier of updated sleuthkit 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 13 Jan 2017 10:17:10 -0200
Source: sleuthkit
Binary: sleuthkit libtsk13 libtsk-dev
Architecture: source
Version: 4.3.1-3
Distribution: experimental
Urgency: medium
Maintainer: Debian Forensics <forensics-devel@lists.alioth.debian.org>
Changed-By: Joao Eriberto Mota Filho <eribe...@debian.org>
Description:
 libtsk-dev - library for forensics analysis (development files)
 libtsk13   - library for forensics analysis on volume and filesystem data
 sleuthkit  - tools for forensics analysis on volume and filesystem data
Closes: 850828
Changes:
 sleuthkit (4.3.1-3) experimental; urgency=medium
 .
   * Updated the symbols. Thanks to Hilko Bengen <ben...@debian.org>.
 (Closes: #850828)
Checksums-Sha1:
 a0f8d2131555b5facd05de4fde9ff30a10601c90 2123 sleuthkit_4.3.1-3.dsc
 36f01baf7ce02ad70b1fbc4594b840e00d78f976 36404 sleuthkit_4.3.1-3.debian.tar.xz
Checksums-Sha256:
 2491aadda6b66931d3ed3e37603171164a3e8a7df5de33176e1c3124e0b7efcd 2123 
sleuthkit_4.3.1-3.dsc
 0b6cc658f36db96c64cc292f7301a5b72e74d5c6897960e87642080bdd29b1be 36404 
sleuthkit_4.3.1-3.debian.tar.xz
Files:
 c1caaff66670667d53902285ea8a6107 2123 admin optional sleuthkit_4.3.1-3.dsc
 fef86cc4dabb6e81039dac8e5a22f591 36404 admin optional 
sleuthkit_4.3.1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlh43i0ACgkQ3mO5xwTr
6e/TGg//V0y6Szt0Xkl2XFRk5QnxakAB4jMfID093yWa4suvZecLXvddB20YAEPc
AXtGjGbhFy7+tPxAqU4Sgv71xvpOtcujenSkil0cZtpofTeNv4mODbFg6cfVI/NR
fNmpOYnWB5yRPidXhxpZq1nMJl4LkCY6imeijuHScwCXdEozoC3lIg2vObOav8Cd
H2S2XIgHbuF6J0Duns5K9qrq2JHbh9CKIAKIRS3A9jnKcjyloxIPRfBLOV1z07i1
IylnNmdsUXKBOy01NNGkUfzQcBj7dwzrznZv1XLiPP37/BDQ9sx6esybHGmetmRv
qPDyzKKGZffjREVBzdKdiUbsCOFkil7NVL0QggSny/d2M41w1fuOrREIPS5yHr+U
6NXWVDtjKmVpOwjBoQYVXJ+HW8yJWa2ElyIG54GJVWZSfPukvekiK9DWuBi+ZgK7
VsNN6z/oqNSr28DrZiWcp89MkSirQUatkV6ed7X9Q9s/rPbBWsgqTh9qNqR+TCTL
8yuXh/Lke9tlSlb4WvpRwRpc/PPnwHMT+ffT4pFrc7jdbU2WSLuKOJpeAhVnks5D
kZzJ0zQPDzklFvZkTwLht8hApdfk/v0goDmcGwUz9lsFPtEM66vJAc2x67uzS7Cf
R09t1XZI/KXnbVn9XEpiiob27s73iThtbiQM0w2adig5t9qCxPQ=
=d2KU
-END PGP SIGNATURE End Message ---
___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#850828: sleuthkit: please update symbols file

[Sascha Steinbiss]

Package: sleuthkit
Version: 4.3.1-2
Severity: minor

Dear Maintainer,

while preparing a Jessie backport for 4.3.1 I noticed that the symbols
file for libtsk13 could be improved:

 - C++ symbols are stored in their mangled form, so builds with different
   GCC versions will result in differences in the symbol file content -- I
   noticed this while building a backport with Jessie's GCC
 - symbols for the latest version 4.3.1 are missing, 4.2.0 is the latest
   in the file

Kind regards
Sascha

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#795052: sleuthkit: Uses embedded copy of libexif-0.6.20

[Eriberto Mota]

2015-08-09 20:58 GMT-03:00 Scott Kitterman <deb...@kitterman.com>:
> Source: sleuthkit
> Version: 4.1.3-11
> Severity: normal
>
> Although not a must in Debian policy, the preference is to not use embedded
> copies of libraries.  sleuthkit-4.1.3/framework/modules/c_LibExifModule has
> an embedded copy of libexif-0.6.20 that is used during package build.  It
> would be better to use the system libexif.

Control: tags 795052 moreinfo


Hi Scott,

I packaged the 4.3.1 version now. I did some checks and I saw that the
upstream does not use this library.

1. Via grep, I can not see a call for the library in main program. I
think that the upstream uses the directory to generate, manually,
files for MS Windows.

2. Removing the directory framework/modules/c_LibExifModule, the
package builds fine. The config.log and sleuthkit_4.3.1-1_amd64.build
don't show any call to libexif.

I thing this bug can be closed. What is your oppinion?

Thanks for your message.

Cheers,

Eriberto

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

sleuthkit 4.2.0-3 MIGRATED to testing

[Debian testing watch]

FYI: The status of the sleuthkit source package
in Debian's testing distribution has changed.

  Previous version: 4.2.0-2
  Current version:  4.2.0-3

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

sleuthkit 4.2.0-2 MIGRATED to testing

[Debian testing watch]

FYI: The status of the sleuthkit source package
in Debian's testing distribution has changed.

  Previous version: 4.1.3-12
  Current version:  4.2.0-2

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

sleuthkit 4.1.3-12 MIGRATED to testing

[Debian testing watch]

FYI: The status of the sleuthkit source package
in Debian's testing distribution has changed.

  Previous version: 4.1.3-11
  Current version:  4.1.3-12

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

sleuthkit 4.1.3-11 MIGRATED to testing

[Debian testing watch]

FYI: The status of the sleuthkit source package
in Debian's testing distribution has changed.

  Previous version: 4.1.3-8
  Current version:  4.1.3-11

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

sleuthkit is marked for autoremoval from testing

[Debian testing autoremoval watch]

sleuthkit 4.1.3-8 is marked for autoremoval from testing on 2015-09-04

It is affected by these RC bugs:
791737: sleuthkit: FTBFS with GCC 5: changes to symbols file

It (build-)depends on packages with these RC bugs:
790975: afflib: library transition may be needed when GCC 5 is the default


___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#795052: sleuthkit: Uses embedded copy of libexif-0.6.20

[Scott Kitterman]

Source: sleuthkit
Version: 4.1.3-11
Severity: normal

Although not a must in Debian policy, the preference is to not use embedded
copies of libraries.  sleuthkit-4.1.3/framework/modules/c_LibExifModule has
an embedded copy of libexif-0.6.20 that is used during package build.  It
would be better to use the system libexif.

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#791285: marked as done (sleuthkit: library transition may be needed when GCC 5 is the default)

[Debian Bug Tracking System]

Your message dated Wed, 05 Aug 2015 21:41:07 +
with message-id e1zn6qt-00070t...@franck.debian.org
and subject line Bug#791285: fixed in sleuthkit 4.1.3-10
has caused the Debian Bug report #791285,
regarding sleuthkit: library transition may be needed when GCC 5 is the default
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
791285: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791285
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:sleuthkit
Version: 4.1.3-8
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Background [1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
and dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

What is needed:

 - Rebuild the library using g++/g++-5 from experimental. Note that
   most likely all C++ libraries within the build dependencies need
   a rebuild too. You can find the log for a rebuild in
 https://people.debian.org/~doko/logs/gcc5-20150701/
   Search for BEGIN GCC CXX11 in the log.

 - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
   library API, and are used by the reverse dependencies of the
   library.

 - If there are no symbols matching __cxx11 or B5cxx11 in the symbols
   forming the library API, you should close this issue with a short
   explanation.
 
 - If there are no reverse dependencies, it should be the package
   maintainers decision if a transition is needed.  However this might
   break software which is not in the Debian archive, and built
   against these packages.

 - If a library transition is needed, please prepare for the change.
   Rename the library package, append v5 to the name of the package
   (e.g. libfoo2 - libfoo2v5). Such a change can be avoided, if you
   have a soversion bump and you upload this version instead of the
   renamed package.  Prepare a patch and attach it to this issue (mark
   this issue with patch), so that it is possible to NMU such a
   package. We'll probably have more than hundred transitions
   triggered. Then reassign the issue to release.debian.org and
   properly tag it as a transition issue, by sending an email to
   cont...@bugs.debian.org:
   
 user release.debian@packages.debian.org
 usertag this issue + transition
 block this issue by 790756
 reassign this issue release.debian.org
   
 - If unsure if a transition is needed, please tag the issue with help
   to ask for feedback from other Debian developers.

The libstdc++6 transition will be a large one, and it will come with a
lot of pain.  Please help it by preparing the follow-up transitions.

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
---End Message---
---BeginMessage---
Source: sleuthkit
Source-Version: 4.1.3-10

We believe that the bug you reported is fixed in the latest version of
sleuthkit, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 791...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho eribe...@debian.org (supplier of updated sleuthkit 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 05 Aug 2015 16:47:32 -0300
Source: sleuthkit
Binary: sleuthkit libtsk10 libtsk-dev
Architecture: source amd64
Version: 4.1.3-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Forensics forensics-devel@lists.alioth.debian.org
Changed-By: Joao Eriberto Mota Filho eribe...@debian.org
Description:
 libtsk-dev - library for forensics analysis (development files)
 libtsk10   - library for forensics analysis on volume and filesystem data
 sleuthkit  - tools for forensics analysis on volume and filesystem data
Closes: 791285 791737
Changes:
 sleuthkit (4.1.3-10) unstable; urgency=medium
 .
   * Upload to unstable

Bug#791285: sleuthkit: library transition may be needed when GCC 5 is the default

[Matthias Klose]

Package: src:sleuthkit
Version: 4.1.3-8
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Background [1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
and dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

What is needed:

 - Rebuild the library using g++/g++-5 from experimental. Note that
   most likely all C++ libraries within the build dependencies need
   a rebuild too. You can find the log for a rebuild in
 https://people.debian.org/~doko/logs/gcc5-20150701/
   Search for BEGIN GCC CXX11 in the log.

 - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
   library API, and are used by the reverse dependencies of the
   library.

 - If there are no symbols matching __cxx11 or B5cxx11 in the symbols
   forming the library API, you should close this issue with a short
   explanation.
 
 - If there are no reverse dependencies, it should be the package
   maintainers decision if a transition is needed.  However this might
   break software which is not in the Debian archive, and built
   against these packages.

 - If a library transition is needed, please prepare for the change.
   Rename the library package, append v5 to the name of the package
   (e.g. libfoo2 - libfoo2v5). Such a change can be avoided, if you
   have a soversion bump and you upload this version instead of the
   renamed package.  Prepare a patch and attach it to this issue (mark
   this issue with patch), so that it is possible to NMU such a
   package. We'll probably have more than hundred transitions
   triggered. Then reassign the issue to release.debian.org and
   properly tag it as a transition issue, by sending an email to
   cont...@bugs.debian.org:
   
 user release.debian@packages.debian.org
 usertag this issue + transition
 block this issue by 790756
 reassign this issue release.debian.org
   
 - If unsure if a transition is needed, please tag the issue with help
   to ask for feedback from other Debian developers.

The libstdc++6 transition will be a large one, and it will come with a
lot of pain.  Please help it by preparing the follow-up transitions.

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

sleuthkit 4.1.3-8 MIGRATED to testing

[Debian testing watch]

FYI: The status of the sleuthkit source package
in Debian's testing distribution has changed.

  Previous version: 4.1.3-7
  Current version:  4.1.3-8

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

sleuthkit is marked for autoremoval from testing

[Debian testing autoremoval watch]

sleuthkit 4.1.3-8 is marked for autoremoval from testing on 2015-07-25

It (build-)depends on packages with these RC bugs:
777938: libbfio: ftbfs with GCC-5
777945: libewf: ftbfs with GCC-5


___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

sleuthkit is marked for autoremoval from testing

[Debian testing autoremoval watch]

sleuthkit 4.1.3-7 is marked for autoremoval from testing on 2015-07-25

It (build-)depends on packages with these RC bugs:
777938: libbfio: ftbfs with GCC-5
777945: libewf: ftbfs with GCC-5


___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#789603: sleuthkit: add mips64el symbol file

[YunQiang Su]

Package: sleuthkit
Version: 4.1.3-7

Please add mips64el symbol file.


-- 
YunQiang Su


libtsk10.symbols.mips64el
Description: Binary data
___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#789603: marked as done (sleuthkit: add mips64el symbol file)

[Debian Bug Tracking System]

Your message dated Mon, 22 Jun 2015 18:34:29 +
with message-id e1z76y9-0007gk...@franck.debian.org
and subject line Bug#789603: fixed in sleuthkit 4.1.3-8
has caused the Debian Bug report #789603,
regarding sleuthkit: add mips64el symbol file
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
789603: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: sleuthkit
Version: 4.1.3-7

Please add mips64el symbol file.


-- 
YunQiang Su


libtsk10.symbols.mips64el
Description: Binary data
---End Message---
---BeginMessage---
Source: sleuthkit
Source-Version: 4.1.3-8

We believe that the bug you reported is fixed in the latest version of
sleuthkit, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 789...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho eribe...@debian.org (supplier of updated sleuthkit 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 22 Jun 2015 15:12:20 -0300
Source: sleuthkit
Binary: sleuthkit libtsk10 libtsk-dev
Architecture: source amd64
Version: 4.1.3-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Forensics forensics-devel@lists.alioth.debian.org
Changed-By: Joao Eriberto Mota Filho eribe...@debian.org
Description:
 libtsk-dev - library for forensics analysis (development files)
 libtsk10   - library for forensics analysis on volume and filesystem data
 sleuthkit  - tools for forensics analysis on volume and filesystem data
Closes: 789603
Changes:
 sleuthkit (4.1.3-8) unstable; urgency=medium
 .
   * Added debian/libtsk10.symbols.mips64el. (Closes: #789603)
Checksums-Sha1:
 10d8c2455d59ee12f6ffe259127d87df18d646e8 2134 sleuthkit_4.1.3-8.dsc
 9c69c7c0f22d697d248dcee57a9d665628d77832 37444 sleuthkit_4.1.3-8.debian.tar.xz
 c9602a5380bb661950ddc43e436661e6cff0e971 367766 libtsk-dev_4.1.3-8_amd64.deb
 052420f31f110d574a05069f171b0f539d2f67b2 303452 libtsk10_4.1.3-8_amd64.deb
 63a1f01ce08830ce2df4f990807c5c702396f76b 250636 sleuthkit_4.1.3-8_amd64.deb
Checksums-Sha256:
 150bbdd05b684bf5b45d434ce3d02b33645d5687b1dd38d7cee48acd344ab56e 2134 
sleuthkit_4.1.3-8.dsc
 ba55c4a5b99ec245166a86047c5f6b0c4cc31b15ecae45e08d20937f04005383 37444 
sleuthkit_4.1.3-8.debian.tar.xz
 d67696a0052864a8502dedd54ee53b700949bd0f388f2430149d7f232688affc 367766 
libtsk-dev_4.1.3-8_amd64.deb
 a32559f3446ee9a182131101cb045e620cc2254b97951a7c1eb442c9b1084a62 303452 
libtsk10_4.1.3-8_amd64.deb
 b593df95f467368b983857b4463291a93de310d79aecfef9a87977789c42935a 250636 
sleuthkit_4.1.3-8_amd64.deb
Files:
 8f263a9b1200ab6413b1599d9b90eeba 2134 admin optional sleuthkit_4.1.3-8.dsc
 924182621b877c2efae9e158dfb44776 37444 admin optional 
sleuthkit_4.1.3-8.debian.tar.xz
 7f513cc0cbb8763adda2691720e6f6cc 367766 libdevel optional 
libtsk-dev_4.1.3-8_amd64.deb
 7f169b0989c868d4c9c0e7b25085aa1a 303452 libs optional 
libtsk10_4.1.3-8_amd64.deb
 1e26de90c32bdc02d506d1fee17888db 250636 admin optional 
sleuthkit_4.1.3-8_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJViFMbAAoJEN5juccE6+nvv0QP/jwElkDlMmdEpXhbaeMqtJUL
hJy/R8tnZQSAstzkBN34idMdmK/z4uUOgRS4lFpYjrx+J8tvcqV1eeoAREfo/kTV
Se7V4XxxcheDZ24RPekH7tr+fcAFQj/z4W4FFU8rCt9W8jh0ZamuIfS7nLoGSVco
KWSOkVe+FQubmIdoYwk5DCdtaQRz/RqUvyDLyNM3Hw25OyhRzVeMaLKzlRfzVCo0
8ZIqEvEQ26sGX4IQ2ZZ0ddPEjRQFHIn0ph4EZd0/adQ77e89IgYKZQu7j3CxzDMX
cFQPd0ow59zmmj4o5Fd/kEjFpnrEKTcMVsXeM6rZIc9j/Z3s6t2Yd6yHblE7o47e
1AKr0bmuHWmVzsdHLmiYqBJhQrX/IuleKZp3ilMEw/OdZxg6irx+B0JnVrE5vxNF
z5eABuISOyWRlxjTsoQNDjPuPefRt9jTMYsLhpSWjQ1DpZJfiX3ExVWCC2fY2jeH
ST6G8CbXuKBfC07/TrrD3QA60RNxZiahVcfO3KXiQeUVBEeTQVBepuG5xUg/fpEV
EEVHlIEVUIiQnHfbY3hrZc97aZH95baCfUEggtCybIJzTDXwGR3qEIqqB7kw8ksP
7+MU+Z/NgY7K6kWmInn4Uu7MaUiYOWPzMlies/bZWWKhIpVUz5/Xj97DQI8AUAG0
scveRSSudx9pIT0LbMRi
=6Z/p
-END PGP SIGNATUREEnd Message---
___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

sleuthkit 4.1.3-7 MIGRATED to testing

[Debian testing watch]

FYI: The status of the sleuthkit source package
in Debian's testing distribution has changed.

  Previous version: 4.1.3-4
  Current version:  4.1.3-7

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

sleuthkit 4.1.3-3 MIGRATED to testing

[Debian testing watch]

FYI: The status of the sleuthkit source package
in Debian's testing distribution has changed.

  Previous version: 4.1.3-2
  Current version:  4.1.3-3

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#746909: marked as done (sleuthkit: ftbfs with GCC-4.9)

[Debian Bug Tracking System]

Your message dated Mon, 12 May 2014 18:22:39 +
with message-id e1wjus3-0008he...@franck.debian.org
and subject line Bug#746909: fixed in sleuthkit 4.1.3-3
has caused the Debian Bug report #746909,
regarding sleuthkit: ftbfs with GCC-4.9
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
746909: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746909
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:sleuthkit
Version: 4.1.3-2
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.9

The package fails to build in a test rebuild on at least amd64 with
gcc-4.9/g++-4.9, but succeeds to build with gcc-4.8/g++-4.8. The
severity of this report may be raised before the jessie release.

The full build log can be found at:
http://people.debian.org/~doko/logs/failed-gcc49/sleuthkit_4.1.3-2_unstable_gcc49.log
The last lines of the build log are at the end of this report.

To build with GCC 4.9, either set CC=gcc-4.9 CXX=g++-4.9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ 

Common build failures are new warnings resulting in build failures
with -Werror turned on, or new/dropped symbols in Debian symbols
files.  For other C/C++ related build failures see the porting guide
at http://gcc.gnu.org/gcc-4.9/porting_to.html

[...]
--- debian/libtsk10.symbols.amd64 (libtsk10_4.1.3-2_amd64)
+++ dpkg-gensymbols55Ocfh   2014-04-18 12:27:29.685620368 +
@@ -192,6 +192,7 @@
  _ZNK9__gnu_cxx24__concurrence_lock_error4whatEv@Base 4.1.3
  _ZNK9__gnu_cxx26__concurrence_unlock_error4whatEv@Base 4.1.3
  _ZNKSt13bad_exception4whatEv@Base 4.1.3
+ _ZNKSt5ctypeIcE8do_widenEc@Base 4.1.3-2
  
_ZNKSt8_Rb_treeIjSt4pairIKjlESt10_Select1stIS2_ESt4lessIjESaIS2_EE4findERS1_@Base
 4.1.3
  
_ZNKSt8_Rb_treeImSt4pairIKmSt3mapIjlSt4lessIjESaIS0_IKjlSt10_Select1stIS9_ES3_ImESaIS9_EE4findERS1_@Base
 4.1.3
  _ZNKSt9bad_alloc4whatEv@Base 4.1.3
@@ -263,15 +264,22 @@
  _ZNSt9type_infoD1Ev@Base 4.1.3
  _ZNSt9type_infoD2Ev@Base 4.1.3
  _ZSt10unexpectedv@Base 4.1.3
- 
_ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIP25_TSK_DB_FILE_LAYOUT_RANGESt6vectorIS2_SaIS2_lS2_EvT_T0_S9_T1_@Base
 4.1.3
- 
_ZSt13__heap_selectIN9__gnu_cxx17__normal_iteratorIP25_TSK_DB_FILE_LAYOUT_RANGESt6vectorIS2_SaIS2_EvT_S8_S8_@Base
 4.1.3
+#MISSING: 4.1.3-2# 
_ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIP25_TSK_DB_FILE_LAYOUT_RANGESt6vectorIS2_SaIS2_lS2_EvT_T0_S9_T1_@Base
 4.1.3
+ 
_ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIP25_TSK_DB_FILE_LAYOUT_RANGESt6vectorIS2_SaIS2_lS2_NS0_5__ops15_Iter_less_iterEEvT_T0_SB_T1_T2_@Base
 4.1.3-2
+#MISSING: 4.1.3-2# 
_ZSt13__heap_selectIN9__gnu_cxx17__normal_iteratorIP25_TSK_DB_FILE_LAYOUT_RANGESt6vectorIS2_SaIS2_EvT_S8_S8_@Base
 4.1.3
+ _ZSt13get_terminatev@Base 4.1.3-2
  _ZSt13set_terminatePFvvE@Base 4.1.3
+ _ZSt14get_unexpectedv@Base 4.1.3-2
  _ZSt14set_unexpectedPFvvE@Base 4.1.3
+ _ZSt15get_new_handlerv@Base 4.1.3-2
  _ZSt15set_new_handlerPFvvE@Base 4.1.3
- 
_ZSt16__insertion_sortIN9__gnu_cxx17__normal_iteratorIP25_TSK_DB_FILE_LAYOUT_RANGESt6vectorIS2_SaIS2_EvT_S8_@Base
 4.1.3
- 
_ZSt16__introsort_loopIN9__gnu_cxx17__normal_iteratorIP25_TSK_DB_FILE_LAYOUT_RANGESt6vectorIS2_SaIS2_lEvT_S8_T0_@Base
 4.1.3
+#MISSING: 4.1.3-2# 
_ZSt16__insertion_sortIN9__gnu_cxx17__normal_iteratorIP25_TSK_DB_FILE_LAYOUT_RANGESt6vectorIS2_SaIS2_EvT_S8_@Base
 4.1.3
+ 
_ZSt16__insertion_sortIN9__gnu_cxx17__normal_iteratorIP25_TSK_DB_FILE_LAYOUT_RANGESt6vectorIS2_SaIS2_NS0_5__ops15_Iter_less_iterEEvT_SA_T0_@Base
 4.1.3-2
+#MISSING: 4.1.3-2# 
_ZSt16__introsort_loopIN9__gnu_cxx17__normal_iteratorIP25_TSK_DB_FILE_LAYOUT_RANGESt6vectorIS2_SaIS2_lEvT_S8_T0_@Base
 4.1.3
  _ZSt18uncaught_exceptionv@Base 4.1.3
- 
_ZSt25__unguarded_linear_insertIN9__gnu_cxx17__normal_iteratorIP25_TSK_DB_FILE_LAYOUT_RANGESt6vectorIS2_SaIS2_EvT_@Base
 4.1.3
+ 
_ZSt22__move_median_to_firstIN9__gnu_cxx17__normal_iteratorIP25_TSK_DB_FILE_LAYOUT_RANGESt6vectorIS2_SaIS2_NS0_5__ops15_Iter_less_iterEEvT_SA_SA_SA_T0_@Base
 4.1.3-2
+#MISSING: 4.1.3-2# 
_ZSt25__unguarded_linear_insertIN9__gnu_cxx17__normal_iteratorIP25_TSK_DB_FILE_LAYOUT_RANGESt6vectorIS2_SaIS2_EvT_@Base
 4.1.3
+ 
_ZSt25__unguarded_linear_insertIN9__gnu_cxx17__normal_iteratorIP25_TSK_DB_FILE_LAYOUT_RANGESt6vectorIS2_SaIS2_NS0_5__ops14_Val_less_iterEEvT_T0_@Base
 4.1.3-2
  _ZSt7nothrow@Base 4.1.3
  _ZSt9terminatev@Base 4.1.3
  _ZTI7TskAuto@Base 4.1.3
@@ -336,7 +344,7 @@
  __cxa_throw@Base 4.1.3
  __gcclibcxx_demangle_callback

sleuthkit 4.1.3-1 MIGRATED to testing

[Debian testing watch]

FYI: The status of the sleuthkit source package
in Debian's testing distribution has changed.

  Previous version: 4.1.2-2
  Current version:  4.1.3-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See http://release.debian.org/testing-watch/ for more information.

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#695097: marked as done (sleuthkit: CVE-2012-5619: Fails to spot files named with a single dot on FAT filesystems)

[Debian Bug Tracking System]

Your message dated Tue, 11 Feb 2014 13:00:07 +
with message-id e1wdcwz-o1...@franck.debian.org
and subject line Bug#695097: fixed in sleuthkit 4.1.2-1
has caused the Debian Bug report #695097,
regarding sleuthkit: CVE-2012-5619: Fails to spot files named with a single dot 
on FAT filesystems
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
695097: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695097
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: sleuthkit
Severity: normal

I don't consider this a vulnerability, but it was assigned a CVE and should
be fixed up nonetheless: http://seclists.org/oss-sec/2012/q4/384

Cheers,
Moritz
---End Message---
---BeginMessage---
Source: sleuthkit
Source-Version: 4.1.2-1

We believe that the bug you reported is fixed in the latest version of
sleuthkit, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 695...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho eribe...@eriberto.pro.br (supplier of updated 
sleuthkit package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 19 Jan 2014 13:11:29 -0200
Source: sleuthkit
Binary: sleuthkit libtsk10 libtsk-dev
Architecture: source amd64
Version: 4.1.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Forensics forensics-devel@lists.alioth.debian.org
Changed-By: Joao Eriberto Mota Filho eribe...@eriberto.pro.br
Description: 
 libtsk-dev - library for forensics analysis (development files)
 libtsk10   - library for forensics analysis on volume and file system data
 sleuthkit  - collection of tools for forensics analysis on volume and file sys
Closes: 695097 702470
Changes: 
 sleuthkit (4.1.2-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #695097, #702470, LP: #1261135)
   * New co-maintainers:
   - Hilko Bengen ben...@debian.org
   - Joao Eriberto Mota Filho eribe...@eriberto.pro.br
   * Migrations:
   - Debhelper version from 8 to 9.
   - Standards-Version from 3.9.2 to 3.9.5.
   * Patches:
   - Added:
   - 20_fix_spelling_errors.diff
   - Removed:
   - 40_fix-typo.diff: the target file was dropped by the upstream.
   - 90_fix_ldflags.diff: new configure.ac and Makefile.am upstream
 files. The content is new.
   - 95_fix-libewf2-detection.patch: the upstream already uses the
 code in this version. The patch was based on code published in
 upstream git repository.
   - 96_fix_build_libewf2.patch: idem.
   - Updated:
   - 10_link-to-sqlite.diff
   - 30_fix-manpages.diff
   - 99_no_static_ldflags.diff
   * debian/changelog:
   - Added new Debian maintainers.
   - Reviewed all licenses and files.
   - Updated the Format field.
   - Updated the upstream copyright years.
   * debian/control:
   - Added the Conflicts field in sleuthkit binary.
   - Added mac-robber as suggestion to sleuthkit binary.
   - Changed VCS fields to canonical URI (anonscm.debian.org instead
 git.debian.org).
   - Improved the long descriptions.
   - Removed obsolete field DM-Upload-Allowed.
   - Removed 'Priority' field from libtsk-dev, that is optional now
 (instead extra).
   - Removed, after renamed, useless and empty binary libtsk10-dbg,
 because libtsk10 already is naturally 'stripped'.
   - Renamed libtsk3-3 to libtsk10.
   - Updated libewf-dev from '= 20100226' to '= 20130416' in
 Build-Depends.
   * debian/gbp.conf: added the pristine-tar line.
   * debian/libtsk-dev.install: updated.
   * debian/libtsk10.symbols.*: generated in amd64 and i386 arch.
   * debian/manpages: added fcat.1, fiwalk.1, jpeg_extract.1 and their
 sources.
   * debian/README.source: removed because it is useless now.
   * debian/rules:
   - Added the override_dh_installdocs to change the original name of
 the fiwalk README file.
   - Removed the override_dh_auto_install target, that adds -sleuthkit
 suffix to icat, ils and mactime files. It is obsolete because TCT

Bug#702470: marked as done (sleuthkit: sleuthkit is 3 versions behind upstream)

[Debian Bug Tracking System]

Your message dated Tue, 11 Feb 2014 13:00:07 +
with message-id e1wdcwz-o7...@franck.debian.org
and subject line Bug#702470: fixed in sleuthkit 4.1.2-1
has caused the Debian Bug report #702470,
regarding sleuthkit: sleuthkit is 3 versions behind upstream
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
702470: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: sleuthkit
Version: 3.2.3-2
Severity: normal

Hello,
 Thank you for maintaining this package in debian. Can you package the
latest upstream? Thanks in advance.

Features added since package available in debian:

 VERSION 4.0.2 --
Core:
New Features:
- Added fiwalk tool from Simson. Not supported in Visual Studio yet.

Bug Fixes:
- Fixed fcat to work on NTFS files (still doesn't support ADS though).
- Fixed HFS+ support in tsk_loaddb / SQLite -- root directory was not added.
- NTFS code now looks at all MFT entries when listing directory
contents. It used to only look at unallocated entries for orphan
files. This fixes an image that had allocated files missing from the
directory b-tree.
- NTFS code uses sequence number when searching MFT entries for all files.
- Libewf detection code change to support v2 API more reliably (ID: 3596212).
- NTFS $SII code could crash in rare cases if $SDS was multiple of block size.

Framework:
- Added new API to TskImgDB that returns the base name of an image.
- Numerous performance improvements to framework.
- Removed requirement in framework to specify module extension in
pipeline configuration file.
- Added blackboard artifacts to represent both operating system and
network service user accounts.

Java Bindings:
- added more APIs to find files by name, path and where clause
- added API to get currently processed dir when image is being added,
- added API to return specific types of children of image, volume
system, volume, file system.
- moved more common methods up to Content interface
- deprecated context of blackboard attributes,
- deprecated SleuthkitCase.runQuery() and SleuthkitCase.closeRunQuery()
- fixed ReadContentInputStream bugs (ignoring offset into a buffer,
implementing available() )
- methods that are lazy loading are now thread safe
- Hash class is now thread-safe
- use more PreparedStatements to improve performance
- changed source level from java 1.6 to 1.7
- Throw exceptions from C++ side better


 VERSION 4.0.1 --
New Features:
- Can open raw Windows devices with write mode sharing.
- More DOS partition types are displayed.
- Added fcat tool that takes in file name and exports content
(equivalent to using ifind and icat together).
- Added new API to TskImgDB that returns hash value associated with
carved files.
- performance improvements with FAT code (maps and dir_add)
- performance improvements with NTFS code (maps)
- added AONLY flag to block_walk
- Updated blkls and blkcalc to use AONLY flag -- MUCH faster.

Bug Fixes:
- Fixed mactime issue where it could choose the wrong timezone that did
  not follow daylight savings times.
- Fixed file size of alternate data streams in framework.
- Incorporated memory leak fixes and raw device fixes from ADF Solutions.



 VERSION 4.0.0 --
New Features:
- Added multithreaded support
- Added C++ wrapper classes
- Added JNI bindings / Java data model classes
- 3314047: Added utf8-specific versions of 'toid' methods for img,vs,fs types
- 3184429: More consistent printing of unset times (all zerso instead of 1970)
- New database design that allows for multiple images in the same database
- GPT volume system tries other sector sizes if first attempt fails.
- Added hash calculation and lookup to AutoDB and JNI.
- Upgraded SQLite to 3.7.9.
- Added Framework in (windows-only)
- EnCase hash support
- Libewf v2 support (it is now non-beta)
- First file in a raw split or E01 can be specified and the rest of the files
  are found.
- mactime displays times as 0 if the time is not set (isntead of 1970)
- Changed behavior of 'mactime -y' to use ISO8601 format.
- Updated HFS+ code from ATC-NY.
- FAT orphan file improvements to reduce false positives.
- TskAuto better reports errors.
- Upgrade build projects from Visual Studio 2008 to 2010.

Bug Fixes:
- Relaxed checking when conflict exists between DOS and GPT partitions.
Had a Mac image that was failing to resolve which partition table
to use.



-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (1

Bug#713364: marked as done (sleuthkit: FTBFS: dpkg-gensymbols errors)

[Debian Bug Tracking System]

Your message dated Mon, 02 Dec 2013 21:50:49 +
with message-id e1vnbod-0001gn...@franck.debian.org
and subject line Bug#713364: fixed in sleuthkit 3.2.3-2.1
has caused the Debian Bug report #713364,
regarding sleuthkit: FTBFS: dpkg-gensymbols errors
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
713364: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: sleuthkit
Version: 3.2.3-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
 make[1]: Entering directory `/«PKGBUILDDIR»'
 dh_strip -a -plibtsk3-3 --dbg-package=libtsk3-3-dbg
 make[1]: Leaving directory `/«PKGBUILDDIR»'
dh_makeshlibs
 dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
 diff output below
 dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
 file: see diff output below
 dpkg-gensymbols: warning: debian/libtsk3-3/DEBIAN/symbols doesn't match 
 completely debian/libtsk3-3.symbols.amd64
 --- debian/libtsk3-3.symbols.amd64 (libtsk3-3_3.2.3-2_amd64)
 +++ dpkg-gensymbols4oVzcg 2013-06-21 06:15:48.733874458 +
 @@ -80,6 +80,8 @@
   _ZN9__gnu_cxx26__concurrence_unlock_errorD1Ev@Base 3.2.1
   _ZN9__gnu_cxx26__concurrence_unlock_errorD2Ev@Base 3.2.1
   _ZN9__gnu_cxx27__verbose_terminate_handlerEv@Base 3.2.1
 + _ZN9__gnu_cxx30__throw_concurrence_lock_errorEv@Base 3.2.3-2
 + _ZN9__gnu_cxx32__throw_concurrence_unlock_errorEv@Base 3.2.3-2
   _ZNK10__cxxabiv117__class_type_info10__do_catchEPKSt9type_infoPPvj@Base 
 3.2.1
   
 _ZNK10__cxxabiv117__class_type_info11__do_upcastEPKS0_PKvRNS0_15__upcast_resultE@Base
  3.2.1
   _ZNK10__cxxabiv117__class_type_info11__do_upcastEPKS0_PPv@Base 3.2.1
 @@ -151,6 +153,7 @@
   __cxa_call_terminate@Base 3.2.1
   __cxa_call_unexpected@Base 3.2.1
   __cxa_current_exception_type@Base 3.2.1
 + __cxa_deleted_virtual@Base 3.2.3-2
   __cxa_demangle@Base 3.2.1
   __cxa_end_catch@Base 3.2.1
   __cxa_free_dependent_exception@Base 3.2.1
 @@ -164,7 +167,7 @@
   __gcclibcxx_demangle_callback@Base 3.2.1
   __gxx_personality_v0@Base 3.2.1
   aff_open@Base 3.2.1
 - ewf_open@Base 3.0.1-3~
 +#MISSING: 3.2.3-2# ewf_open@Base 3.0.1-3~
   ext2fs_block_getflags@Base 2.52
   ext2fs_block_walk@Base 3.0.1
   ext2fs_dir_open_meta@Base 2.52
 dh_makeshlibs: dpkg-gensymbols -plibtsk3-3 -Idebian/libtsk3-3.symbols.amd64 
 -Pdebian/libtsk3-3 -edebian/libtsk3-3/usr/lib/libtsk3.so.3.4.0
  returned exit code 1
 make: *** [binary] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/sleuthkit_3.2.3-2_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
---End Message---
---BeginMessage---
Source: sleuthkit
Source-Version: 3.2.3-2.1

We believe that the bug you reported is fixed in the latest version of
sleuthkit, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 713...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann a...@debian.org (supplier of updated sleuthkit package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 30 Nov 2013 21:15:15 +0100
Source: sleuthkit
Binary: sleuthkit libtsk3-3 libtsk3-3-dbg libtsk-dev
Architecture: source amd64
Version: 3.2.3-2.1
Distribution: unstable
Urgency: low
Maintainer: Debian Forensics forensics-devel@lists.alioth.debian.org
Changed-By: Andreas Beckmann a...@debian.org
Description: 
 libtsk-dev - library for forensics analysis (development files)
 libtsk3-3  - library for forensics analysis on volume and file system data
 libtsk3-3-dbg - library for forensics analysis (debug symbols)
 sleuthkit  - collection of tools

Re: Prepared sleuthkit 4.1.0

[Henri Salo]

On Tue, Jun 18, 2013 at 01:07:23PM +0200, Michael Prokop wrote:
 we're lagging quite some versions behind with our sleuthkit
 packaging in Debian. I tried to take care of it and just pushed
 upstream and pristine-tar branches for new upstream version 4.1.0 of
 sleuthkit to our git repos (I hope you don't mind, Christophe).
 
 I also pushed my changes related to Debian packaging into branch
 mika/4.1.0 (to not mess with main 'debian' branch yet until it's
 known to be fine).
 
 I'm a bit unsure how to handle the libtsk3 package though.
 Our latest package libtsk3-3 shipped /usr/lib/libtsk3.so.3.4.0
 but upstream seems to have renamed 'tsk3' to just 'tsk' and I'm not
 sure how to handle the resulting /usr/lib/libtsk.so.10.0.0 package
 wise.
 
 Julien, you seem to have handled also the symbol files in the past
 and know what you're doing. :) Any chance you could take a look at
 the current situation and help us in getting a new package release
 out?

Hello,

I can't see sleuthkit 4.1.0 yet in unstable. What is the status with this? I can
help with some smaller tasks and testing if needed. Without much checking
security vulnerability[1] has been fixed in newer versions. In my opinion
comment Hardly a vulnerability in tracker is understating this issue as per
mailing list post[2] says:


The vulnerability is already exploited, for example, by the Flame
malware (possibly unintendedly). Flame uses an encrypted SQLite-DB named
. for extraction of confidential files and for update distribution.
An analyst may miss the file as the Sleuth Kit does not appropriately
show the file.

http://labs.bitdefender.com/2012/06/flame-the-story-of-leaked-data-carried-by-human-vector/
http://blog.crysys.hu/2012/06/flame-usb-dot-file-confirmed/


1: https://security-tracker.debian.org/tracker/CVE-2012-5619
2: http://www.openwall.com/lists/oss-security/2012/12/01/2

---
Henri Salo


signature.asc
Description: Digital signature
___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Re: Prepared sleuthkit 4.1.0

[Michael Prokop]

* Henri Salo [Wed Jun 26, 2013 at 10:10:32AM +0300]:
 On Tue, Jun 18, 2013 at 01:07:23PM +0200, Michael Prokop wrote:
  we're lagging quite some versions behind with our sleuthkit
  packaging in Debian. I tried to take care of it and just pushed
  upstream and pristine-tar branches for new upstream version 4.1.0 of
  sleuthkit to our git repos (I hope you don't mind, Christophe).

  I also pushed my changes related to Debian packaging into branch
  mika/4.1.0 (to not mess with main 'debian' branch yet until it's
  known to be fine).

  I'm a bit unsure how to handle the libtsk3 package though.
  Our latest package libtsk3-3 shipped /usr/lib/libtsk3.so.3.4.0
  but upstream seems to have renamed 'tsk3' to just 'tsk' and I'm not
  sure how to handle the resulting /usr/lib/libtsk.so.10.0.0 package
  wise.

  Julien, you seem to have handled also the symbol files in the past
  and know what you're doing. :) Any chance you could take a look at
  the current situation and help us in getting a new package release
  out?

 I can't see sleuthkit 4.1.0 yet in unstable. What is the status with this? I 
 can
 help with some smaller tasks and testing if needed.
[...]

It's still as stated above. We need a decision how to handle the
tsk library.

regards,
-mika-


signature.asc
Description: Digital signature
___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#713364: sleuthkit: FTBFS: dpkg-gensymbols errors

[Lucas Nussbaum]

Source: sleuthkit
Version: 3.2.3-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
 make[1]: Entering directory `/«PKGBUILDDIR»'
 dh_strip -a -plibtsk3-3 --dbg-package=libtsk3-3-dbg
 make[1]: Leaving directory `/«PKGBUILDDIR»'
dh_makeshlibs
 dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
 diff output below
 dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
 file: see diff output below
 dpkg-gensymbols: warning: debian/libtsk3-3/DEBIAN/symbols doesn't match 
 completely debian/libtsk3-3.symbols.amd64
 --- debian/libtsk3-3.symbols.amd64 (libtsk3-3_3.2.3-2_amd64)
 +++ dpkg-gensymbols4oVzcg 2013-06-21 06:15:48.733874458 +
 @@ -80,6 +80,8 @@
   _ZN9__gnu_cxx26__concurrence_unlock_errorD1Ev@Base 3.2.1
   _ZN9__gnu_cxx26__concurrence_unlock_errorD2Ev@Base 3.2.1
   _ZN9__gnu_cxx27__verbose_terminate_handlerEv@Base 3.2.1
 + _ZN9__gnu_cxx30__throw_concurrence_lock_errorEv@Base 3.2.3-2
 + _ZN9__gnu_cxx32__throw_concurrence_unlock_errorEv@Base 3.2.3-2
   _ZNK10__cxxabiv117__class_type_info10__do_catchEPKSt9type_infoPPvj@Base 
 3.2.1
   
 _ZNK10__cxxabiv117__class_type_info11__do_upcastEPKS0_PKvRNS0_15__upcast_resultE@Base
  3.2.1
   _ZNK10__cxxabiv117__class_type_info11__do_upcastEPKS0_PPv@Base 3.2.1
 @@ -151,6 +153,7 @@
   __cxa_call_terminate@Base 3.2.1
   __cxa_call_unexpected@Base 3.2.1
   __cxa_current_exception_type@Base 3.2.1
 + __cxa_deleted_virtual@Base 3.2.3-2
   __cxa_demangle@Base 3.2.1
   __cxa_end_catch@Base 3.2.1
   __cxa_free_dependent_exception@Base 3.2.1
 @@ -164,7 +167,7 @@
   __gcclibcxx_demangle_callback@Base 3.2.1
   __gxx_personality_v0@Base 3.2.1
   aff_open@Base 3.2.1
 - ewf_open@Base 3.0.1-3~
 +#MISSING: 3.2.3-2# ewf_open@Base 3.0.1-3~
   ext2fs_block_getflags@Base 2.52
   ext2fs_block_walk@Base 3.0.1
   ext2fs_dir_open_meta@Base 2.52
 dh_makeshlibs: dpkg-gensymbols -plibtsk3-3 -Idebian/libtsk3-3.symbols.amd64 
 -Pdebian/libtsk3-3 -edebian/libtsk3-3/usr/lib/libtsk3.so.3.4.0
  returned exit code 1
 make: *** [binary] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/sleuthkit_3.2.3-2_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#702470: sleuthkit: sleuthkit is 3 versions behind upstream

[Douglas Calvert]

Package: sleuthkit
Version: 3.2.3-2
Severity: normal

Hello,
 Thank you for maintaining this package in debian. Can you package the
latest upstream? Thanks in advance.

Features added since package available in debian:

 VERSION 4.0.2 --
Core:
New Features:
- Added fiwalk tool from Simson. Not supported in Visual Studio yet.

Bug Fixes:
- Fixed fcat to work on NTFS files (still doesn't support ADS though).
- Fixed HFS+ support in tsk_loaddb / SQLite -- root directory was not added.
- NTFS code now looks at all MFT entries when listing directory
contents. It used to only look at unallocated entries for orphan
files. This fixes an image that had allocated files missing from the
directory b-tree.
- NTFS code uses sequence number when searching MFT entries for all files.
- Libewf detection code change to support v2 API more reliably (ID: 3596212).
- NTFS $SII code could crash in rare cases if $SDS was multiple of block size.

Framework:
- Added new API to TskImgDB that returns the base name of an image.
- Numerous performance improvements to framework.
- Removed requirement in framework to specify module extension in
pipeline configuration file.
- Added blackboard artifacts to represent both operating system and
network service user accounts.

Java Bindings:
- added more APIs to find files by name, path and where clause
- added API to get currently processed dir when image is being added,
- added API to return specific types of children of image, volume
system, volume, file system.
- moved more common methods up to Content interface
- deprecated context of blackboard attributes,
- deprecated SleuthkitCase.runQuery() and SleuthkitCase.closeRunQuery()
- fixed ReadContentInputStream bugs (ignoring offset into a buffer,
implementing available() )
- methods that are lazy loading are now thread safe
- Hash class is now thread-safe
- use more PreparedStatements to improve performance
- changed source level from java 1.6 to 1.7
- Throw exceptions from C++ side better


 VERSION 4.0.1 --
New Features:
- Can open raw Windows devices with write mode sharing.
- More DOS partition types are displayed.
- Added fcat tool that takes in file name and exports content
(equivalent to using ifind and icat together).
- Added new API to TskImgDB that returns hash value associated with
carved files.
- performance improvements with FAT code (maps and dir_add)
- performance improvements with NTFS code (maps)
- added AONLY flag to block_walk
- Updated blkls and blkcalc to use AONLY flag -- MUCH faster.

Bug Fixes:
- Fixed mactime issue where it could choose the wrong timezone that did
  not follow daylight savings times.
- Fixed file size of alternate data streams in framework.
- Incorporated memory leak fixes and raw device fixes from ADF Solutions.



 VERSION 4.0.0 --
New Features:
- Added multithreaded support
- Added C++ wrapper classes
- Added JNI bindings / Java data model classes
- 3314047: Added utf8-specific versions of 'toid' methods for img,vs,fs types
- 3184429: More consistent printing of unset times (all zerso instead of 1970)
- New database design that allows for multiple images in the same database
- GPT volume system tries other sector sizes if first attempt fails.
- Added hash calculation and lookup to AutoDB and JNI.
- Upgraded SQLite to 3.7.9.
- Added Framework in (windows-only)
- EnCase hash support
- Libewf v2 support (it is now non-beta)
- First file in a raw split or E01 can be specified and the rest of the files
  are found.
- mactime displays times as 0 if the time is not set (isntead of 1970)
- Changed behavior of 'mactime -y' to use ISO8601 format.
- Updated HFS+ code from ATC-NY.
- FAT orphan file improvements to reduce false positives.
- TskAuto better reports errors.
- Upgrade build projects from Visual Studio 2008 to 2010.

Bug Fixes:
- Relaxed checking when conflict exists between DOS and GPT partitions.
Had a Mac image that was failing to resolve which partition table
to use.



-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.8-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages sleuthkit depends on:
ii  file5.11-2
ii  libc6   2.13-38
ii  libdate-manip-perl  6.37-1
ii  libgcc1 1:4.7.2-5
ii  libstdc++6  4.7.2-5
ii  libtsk3-3   3.2.3-2
ii  perl5.14.2-18

sleuthkit recommends no packages.

Versions of packages sleuthkit suggests:
ii  autopsy  2.24-1

-- no debconf information

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#695097: sleuthkit: Fails to spot files named with a single dot on FAT filesystems

[Moritz Muehlenhoff]

Package: sleuthkit
Severity: normal

I don't consider this a vulnerability, but it was assigned a CVE and should
be fixed up nonetheless: http://seclists.org/oss-sec/2012/q4/384

Cheers,
Moritz

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

sleuthkit 3.2.3-2 MIGRATED to testing

[Debian testing watch]

FYI: The status of the sleuthkit source package
in Debian's testing distribution has changed.

  Previous version: 3.2.1-2
  Current version:  3.2.3-2

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See http://release.debian.org/testing-watch/ for more information.

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Re: Staging for sleuthkit 3.2.2

[Christophe Monniez]

On Sat, Aug 13, 2011 at 12:29 AM, Dan Chen seven.st...@gmail.com wrote:
 Hi all,

 I've prepared a pending debian branch for sleuthkit 3.2.2 with the
 intent of getting it into Ubuntu 11.10 with a FeatureFreezeException.
 Please see https://github.com/crimsun/sleuthkit (or
 git://github.com/crimsun/sleuthkit.git). I've updated the symbols
 files appropriately and test-built/installed/removed on amd64 local
 installs of both Debian Sid and Ubuntu Oneiric. Any comments are
 welcome, and I'm happy to help out in the future as part of the
 debian-forensics Alioth team (already a member of pkg-alsa-devel and
 pkg-pulseaudio-devel).

 Cheers,
 -Dan

 ___
 forensics-devel mailing list
 forensics-devel@lists.alioth.debian.org
 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel


Hi Dan,

thanks for your work, you are more than welcome to contribute to the team.
I added you to the team on alioth.

We already have a git repository on alioth for our work, not sure that
the github duplicate is a good idea.

-- 
Christophe Monniez

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Staging for sleuthkit 3.2.2

[Dan Chen]

Hi all,

I've prepared a pending debian branch for sleuthkit 3.2.2 with the
intent of getting it into Ubuntu 11.10 with a FeatureFreezeException.
Please see https://github.com/crimsun/sleuthkit (or
git://github.com/crimsun/sleuthkit.git). I've updated the symbols
files appropriately and test-built/installed/removed on amd64 local
installs of both Debian Sid and Ubuntu Oneiric. Any comments are
welcome, and I'm happy to help out in the future as part of the
debian-forensics Alioth team (already a member of pkg-alsa-devel and
pkg-pulseaudio-devel).

Cheers,
-Dan

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#219010: Please cooperate with sleuthkit

[Goran Vulić]

Package: tct
Version: 1.19-1
Severity: normal

When both tct and sleuthkit are installed binary /usr/bin/icat from tct 
overwrites symbolic
link /usr/bin/icat - /etc/alternatives/icat for update-alternatives mechanism 
in sleuthkit.
That brakes /usr/bin/sorter of sleuthkit (autopsy), because sorter calls icat.

-- System Information:
Debian Release: 6.0.2
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable'), (900, 
'proposed-updates'), (350, 'testing'), (250, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-option.01 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=sr_RS.UTF-8@latin (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages tct depends on:
ii  coreutils 8.5-1  GNU core utilities
ii  file  5.04-5 Determines file type using magic
ii  libc6 2.11.2-10  Embedded GNU C Library: Shared lib
ii  libdate-manip-perl6.11-1 module for manipulating dates

Versions of packages tct recommends:
ii  lsof   4.81.dfsg.1-1 List open files

Versions of packages tct suggests:
pn  acct  none (no description available)

-- no debconf information



___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

sleuthkit 3.2.1-2 MIGRATED to testing

[Debian testing watch]

FYI: The status of the sleuthkit source package
in Debian's testing distribution has changed.

  Previous version: 3.1.3-1
  Current version:  3.2.1-2

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See http://release.debian.org/testing-watch/ for more information.

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#630207: marked as done (sleuthkit: FTBFS: symbol missmatch)

[Debian Bug Tracking System]

Your message dated Sun, 12 Jun 2011 13:33:07 +
with message-id e1qvkmp-0006wt...@franck.debian.org
and subject line Bug#630207: fixed in sleuthkit 3.2.1-2
has caused the Debian Bug report #630207,
regarding sleuthkit: FTBFS: symbol missmatch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
630207: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:sleuthkit
Version: 3.2.1-1
Severity: serious
Tags: sid wheezy
Justification: fails to build from source (but built successfully in the past)

Hi!

Your pacage failed to build on all non any-amd64 buildds e.g.:
+ _ZNK10__cxxabiv117__class_type_info20__do_find_public_srcEiPKvPKS0_S2_@Base 
3.2.1-1
+#MISSING: 3.2.1-1# 
_ZNK10__cxxabiv117__class_type_info20__do_find_public_srcElPKvPKS0_S2_@Base 
3.2.1
  
_ZNK10__cxxabiv120__si_class_type_info11__do_upcastEPKNS_17__class_type_infoEPKvRNS1_15__upcast_resultE@Base
 3.2.1
- 
_ZNK10__cxxabiv120__si_class_type_info12__do_dyncastElNS_17__class_type_info10__sub_kindEPKS1_PKvS4_S6_RNS1_16__dyncast_resultE@Base
 3.2.1
- 
_ZNK10__cxxabiv120__si_class_type_info20__do_find_public_srcElPKvPKNS_17__class_type_infoES2_@Base
 3.2.1
+ 
_ZNK10__cxxabiv120__si_class_type_info12__do_dyncastEiNS_17__class_type_info10__sub_kindEPKS1_PKvS4_S6_RNS1_16__dyncast_resultE@Base
 3.2.1-1
+#MISSING: 3.2.1-1# 
_ZNK10__cxxabiv120__si_class_type_info12__do_dyncastElNS_17__class_type_info10__sub_kindEPKS1_PKvS4_S6_RNS1_16__dyncast_resultE@Base
 3.2.1
+ 
_ZNK10__cxxabiv120__si_class_type_info20__do_find_public_srcEiPKvPKNS_17__class_type_infoES2_@Base
 3.2.1-1
+#MISSING: 3.2.1-1# 
_ZNK10__cxxabiv120__si_class_type_info20__do_find_public_srcElPKvPKNS_17__class_type_infoES2_@Base
 3.2.1
  _ZNK9__gnu_cxx24__concurrence_lock_error4whatEv@Base 3.2.1
  _ZNK9__gnu_cxx26__concurrence_unlock_error4whatEv@Base 3.2.1
  _ZNKSt13bad_exception4whatEv@Base 3.2.1
dh_makeshlibs: dpkg-gensymbols -plibtsk3-3 -Idebian/libtsk3-3.symbols 
-Pdebian/libtsk3-3 -edebian/libtsk3-3/usr/lib/libtsk3.so.3.3.1
 returned exit code 1

Full build log at
https://buildd.debian.org/status/fetch.php?pkg=sleuthkitarch=kfreebsd-i386ver=3.2.1-1stamp=1307743372

Regards

Christoph

If you have further questions please mail debian-...@lists.debian.org

-- 
9FED 5C6C E206 B70A 5857  70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer

A. Because it breaks the logical sequence of discussion
Q. Why is top posting bad?


pgpyVmjC9rJab.pgp
Description: PGP signature
---End Message---
---BeginMessage---
Source: sleuthkit
Source-Version: 3.2.1-2

We believe that the bug you reported is fixed in the latest version of
sleuthkit, which is due to be installed in the Debian FTP archive:

libtsk-dev_3.2.1-2_amd64.deb
  to main/s/sleuthkit/libtsk-dev_3.2.1-2_amd64.deb
libtsk3-3-dbg_3.2.1-2_amd64.deb
  to main/s/sleuthkit/libtsk3-3-dbg_3.2.1-2_amd64.deb
libtsk3-3_3.2.1-2_amd64.deb
  to main/s/sleuthkit/libtsk3-3_3.2.1-2_amd64.deb
sleuthkit_3.2.1-2.debian.tar.gz
  to main/s/sleuthkit/sleuthkit_3.2.1-2.debian.tar.gz
sleuthkit_3.2.1-2.dsc
  to main/s/sleuthkit/sleuthkit_3.2.1-2.dsc
sleuthkit_3.2.1-2_amd64.deb
  to main/s/sleuthkit/sleuthkit_3.2.1-2_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 630...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julien Valroff jul...@debian.org (supplier of updated sleuthkit package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 12 Jun 2011 14:57:56 +0200
Source: sleuthkit
Binary: sleuthkit libtsk3-3 libtsk3-3-dbg libtsk-dev
Architecture: source amd64
Version: 3.2.1-2
Distribution: unstable
Urgency: low
Maintainer: Debian Forensics forensics-devel@lists.alioth.debian.org
Changed-By: Julien Valroff jul...@debian.org
Description: 
 libtsk-dev - library for forensics analysis (development files)
 libtsk3-3  - library for forensics analysis on volume and file system data
 libtsk3-3-dbg - library for forensics analysis (debug symbols)
 sleuthkit  - collection of tools for forensics analysis on volume and file sys
Closes: 630207
Changes: 
 sleuthkit (3.2.1-2) unstable; urgency=low
 .
   * Team upload.
   * Fix symbols files for non

Re: sleuthkit

[Christophe Monniez]

Le vendredi 03 juin 2011 à 07:29 +0200, Julien Valroff a écrit :
 Le samedi 07 mai 2011 à 17:13:57 (+0200 CEST), Julien Valroff a écrit :
  Le samedi 07 mai 2011 à 09:46:02 (+0200 CEST), Christophe Monniez a écrit :
   Le samedi 07 mai 2011 à 09:15 +0200, Julien Valroff a écrit :
   Unfortunately, I have too much work this week and will not be able to
   work on sleuthkit package before mai 12th.
   
   I will probably need help on how to de-embed sqlite and I don't really
   understand the last Error.
  
  I have just pushed the easy changes. I am unfortunately not skilled for
  de-embedding sqlite.
 
 I have worked on Sleuth Kit and the package seems now in good shape.
 
 I have managed to lin dynamically against libsqlite3 rather than using the
 embedded copy which was linked statically: as from sqlite.c headers, this
 was only meant to improve performance by 5% or more - which doesn't seem
 that signifcant compared to the potential problems embedding this could
 cause.
 
 However, I would appreciate if some of you could actually test the packages
 and report any issue linked to this change - I do not use sleuthkit nor
 libtsk…
 

I build the seluthkit packages with pbuilder and it build smoothly.

I did some test on sleuthkit, I tested nearly all tools against a
forensic copy and they worked very well. The tool that use a sqlite
database worked without any problem.

I made a little change on the debian/control file to support afflib.
I did a rebuild of the package with pbuilder and t worked again.
I then verified the tools against an aff forensic image and it worked
too.

So, from my point of view, the package is ready for upload.

Thanks for the great work you did Julien. Once again, I learned a lot
from someone of the team !


-- 
Christophe Monniez christophe.monn...@fccu.be


___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Bug#549071: marked as done (sleuthkit: compile against afflib)

[Debian Bug Tracking System]

Your message dated Sat, 11 Jun 2011 07:30:43 +0200
with message-id 20110611053043.gc2...@kirya.net
and subject line Closing bugs
has caused the Debian Bug report #549071,
regarding sleuthkit: compile against afflib
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
549071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: sleuthkit
Version: 3.0.1-5
Severity: wishlist


IIRC the maintainer is already aware of that,
just for the record:

Now that afflib just entered Debian/unstable it would be
nice if sleuthkit could have a build dependency against
libafflib-dev so it supports the AFF format.

regards,
-mika-


---End Message---
---BeginMessage---
Package: sleuthkit
Version: 3.2.1-1

Hi,

Both bugs were closed with the upload of the 3.2.1-1 package.

Cheers,
Julien

-- 
  .''`.   Julien Valroff ~ jul...@kirya.net ~ jul...@debian.org
 : :'  :  Debian Developer  Free software contributor
 `. `'`   http://www.kirya.net/
   `- 4096R/ E1D8 5796 8214 4687 E416  948C 859F EF67 258E 26B1

---End Message---
___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Re: sleuthkit

[Julien Valroff]

Le mercredi 04 mai 2011 à 10:14:57 (+0200 CEST), Christophe Monniez a écrit :
 Hi,
 
 I worked on sleuthkit and after a long search, I discover that some
 files were missing in the git repos.
 
 I don't know what kind of mistake I made when I imported upstream the
 first time. Anyway, I imported usptream again and now it builds fine.
 
 I think that this version is now ready for upload.
 
I'll have a look at it during the week-end.

It seems however several changes need to be applied to make lintian happy:

I: sleuthkit source: missing-debian-source-format
W: sleuthkit source: no-human-maintainers
W: sleuthkit source: build-depends-on-1-revision build-depends: libewf-dev (= 
20100226-1)
W: sleuthkit source: changelog-should-mention-nmu
W: sleuthkit source: source-nmu-has-incorrect-version-number 3.1.3-1
W: sleuthkit source: patch-system-but-direct-changes-in-diff Makefile.am and 
110 more
E: sleuthkit: embedded-library usr/bin/tsk_loaddb: sqlite
W: sleuthkit: manpage-has-errors-from-man usr/share/man/man1/hfind.1.gz 98: 
warning [p 2, 6.2i]: cannot adjust line
I: sleuthkit: hyphen-used-as-minus-sign 
usr/share/man/man1/tsk_comparedir.1.gz:33
I: sleuthkit: hyphen-used-as-minus-sign usr/share/man/man1/tsk_gettimes.1.gz:17
I: sleuthkit: hyphen-used-as-minus-sign usr/share/man/man1/tsk_gettimes.1.gz:25
I: sleuthkit: hyphen-used-as-minus-sign usr/share/man/man1/tsk_loaddb.1.gz:35
I: sleuthkit: hyphen-used-as-minus-sign usr/share/man/man1/tsk_loaddb.1.gz:38
I: sleuthkit: hyphen-used-as-minus-sign usr/share/man/man1/tsk_recover.1.gz:31
E: libtsk3-3: embedded-library usr/lib/libtsk3.so.3.3.1: sqlite
E: libtsk3-3: symbols-file-contains-current-version-with-debian-revision on 
symbol _ZN7TskAuto10closeImageEv@Base and 233 others

Cheers,
Julien

-- 
  .''`.   Julien Valroff ~ jul...@kirya.net ~ jul...@debian.org
 : :'  :  Debian Developer  Free software contributor
 `. `'`   http://www.kirya.net/
   `- 4096R/ E1D8 5796 8214 4687 E416  948C 859F EF67 258E 26B1

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/forensics-devel

Re: sleuthkit

[Christophe Monniez]

Le samedi 07 mai 2011 à 09:15 +0200, Julien Valroff a écrit :
 Le mercredi 04 mai 2011 à 10:14:57 (+0200 CEST), Christophe Monniez a écrit :
  Hi,
  
  I worked on sleuthkit and after a long search, I discover that some
  files were missing in the git repos.
  
  I don't know what kind of mistake I made when I imported upstream the
  first time. Anyway, I imported usptream again and now it builds fine.
  
  I think that this version is now ready for upload.
  
 I'll have a look at it during the week-end.
 
 It seems however several changes need to be applied to make lintian happy:
 
 I: sleuthkit source: missing-debian-source-format
 W: sleuthkit source: no-human-maintainers
 W: sleuthkit source: build-depends-on-1-revision build-depends: libewf-dev 
 (= 20100226-1)
 W: sleuthkit source: changelog-should-mention-nmu
 W: sleuthkit source: source-nmu-has-incorrect-version-number 3.1.3-1
 W: sleuthkit source: patch-system-but-direct-changes-in-diff Makefile.am and 
 110 more
 E: sleuthkit: embedded-library usr/bin/tsk_loaddb: sqlite
 W: sleuthkit: manpage-has-errors-from-man usr/share/man/man1/hfind.1.gz 98: 
 warning [p 2, 6.2i]: cannot adjust line
 I: sleuthkit: hyphen-used-as-minus-sign 
 usr/share/man/man1/tsk_comparedir.1.gz:33
 I: sleuthkit: hyphen-used-as-minus-sign 
 usr/share/man/man1/tsk_gettimes.1.gz:17
 I: sleuthkit: hyphen-used-as-minus-sign 
 usr/share/man/man1/tsk_gettimes.1.gz:25
 I: sleuthkit: hyphen-used-as-minus-sign usr/share/man/man1/tsk_loaddb.1.gz:35
 I: sleuthkit: hyphen-used-as-minus-sign usr/share/man/man1/tsk_loaddb.1.gz:38
 I: sleuthkit: hyphen-used-as-minus-sign usr/share/man/man1/tsk_recover.1.gz:31
 E: libtsk3-3: embedded-library usr/lib/libtsk3.so.3.3.1: sqlite
 E: libtsk3-3: symbols-file-contains-current-version-with-debian-revision on 
 symbol _ZN7TskAuto10closeImageEv@Base and 233 others
 
 Cheers,
 Julien
 

Thanks Julien,

I forgot to have a look at lintian results, I was so happy that it
finally builds.

Unfortunately, I have too much work this week and will not be able to
work on sleuthkit package before mai 12th.

I will probably need help on how to de-embed sqlite and I don't really
understand the last Error.

regards,

-- 
Christophe Monniez christophe.monn...@fccu.be


___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/forensics-devel

Re: sleuthkit

[Julien Valroff]

Le samedi 07 mai 2011 à 09:46:02 (+0200 CEST), Christophe Monniez a écrit :
 Le samedi 07 mai 2011 à 09:15 +0200, Julien Valroff a écrit :
 Unfortunately, I have too much work this week and will not be able to
 work on sleuthkit package before mai 12th.
 
 I will probably need help on how to de-embed sqlite and I don't really
 understand the last Error.

I have just pushed the easy changes. I am unfortunately not skilled for
de-embedding sqlite.

The last error roughly means you have to update the symbols file
(dpkg-gensymbols keeps the debian revision from the auto-generated symbols
file).

Hope this helps somehow...

Cheers,
Julien

-- 
  .''`.   Julien Valroff ~ jul...@kirya.net ~ jul...@debian.org
 : :'  :  Debian Developer  Free software contributor
 `. `'`   http://www.kirya.net/
   `- 4096R/ E1D8 5796 8214 4687 E416  948C 859F EF67 258E 26B1

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/forensics-devel

sleuthkit

[Christophe Monniez]

Hi,

I worked on sleuthkit and after a long search, I discover that some
files were missing in the git repos.

I don't know what kind of mistake I made when I imported upstream the
first time. Anyway, I imported usptream again and now it builds fine.

I think that this version is now ready for upload.

I'm going to work on the latest version reglookup, if anyone with python
packaging experience wants to help, feel free  ...

-- 
Christophe Monniez christophe.monn...@fccu.be


___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/forensics-devel

sleuthkit with afflib?

[Michael Prokop]

Hi,

regarding #549071 - Subject: sleuthkit: compile against afflib I'd
like to make sure it doesn't get lost (as afflib is available in
testing/unstable nowadays).

Is there any reason that prevents us from merging the afflib branch
in sleuthkit.git into the debian branch and upload it the result to
experimental? (We won't make it into squeeze with this change
anymore, so we should avoid uploading to unstable at least for now
IMHO.)

regards,
-mika-


signature.asc
Description: Digital signature
___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/forensics-devel

sleuthkit - afflib

[Christophe Monniez]

Hi all,

I pushed a new branch into the sleuthkit package repository.
It's a try to compile sleuthkit with afflib support.

It seems to work. If Cristian agree, it can be merged with the debian
branch.

It will close #549071.

-- 
Christophe Monniez
___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/forensics-devel

sleuthkit 3.1.1-1 MIGRATED to testing

[Debian testing watch]

FYI: The status of the sleuthkit source package
in Debian's testing distribution has changed.

  Previous version: 3.1.0-1
  Current version:  3.1.1-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See http://release.debian.org/testing-watch/ for more information.

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/forensics-devel

sleuthkit 3.1.0-1 MIGRATED to testing

[Debian testing watch]

FYI: The status of the sleuthkit source package
in Debian's testing distribution has changed.

  Previous version: 3.0.1-5
  Current version:  3.1.0-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See http://release.debian.org/testing-watch/ for more information.

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/forensics-devel

Re: Sleuthkit Autopsy updates

[Cristian Greco]

On Sun, 31 Jan 2010 22:31:12 +
Dennis 123321 dennis123...@googlemail.com wrote:

 Could the newest Sleuthkit  Autopsy be packaged for Debian please?
 
 http://www.sleuthkit.org/
 January 13, 2010: TSK 3.1.0 and Autopsy 2.22 are now available for
 download. 

Hi Dennis,

I'll try to get this new version (tsk) uploaded as soon as possible. There are
a number of change, and my spare time is a bit reduced these weeks.

Thanks,
--
Cristian Greco
GPG key ID: 0xCF4D32E4 (old: 0x0C095825)


signature.asc
Description: PGP signature
___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/forensics-devel

Sleuthkit Autopsy updates

[Dennis 123321]

Could the newest Sleuthkit  Autopsy be packaged for Debian please?

http://www.sleuthkit.org/
January 13, 2010: TSK 3.1.0 and Autopsy 2.22 are now available for download. 


Cheers

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/forensics-devel

Bug#549071: sleuthkit: compile against afflib

[Michael Prokop]

Package: sleuthkit
Version: 3.0.1-5
Severity: wishlist


IIRC the maintainer is already aware of that,
just for the record:

Now that afflib just entered Debian/unstable it would be
nice if sleuthkit could have a build dependency against
libafflib-dev so it supports the AFF format.

regards,
-mika-



___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/forensics-devel

uploading sleuthkit?

[Daniel Baumann]

Hi Cristian,

do you think sleuthkit is ready to be uploaded? i think it is, and i'd
like to see the ITA closed soon.

Regards,
Daniel

-- 
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:  daniel.baum...@panthera-systems.net
Internet:   http://people.panthera-systems.net/~daniel-baumann/

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/forensics-devel