Bug 294580 - Unclear status of jpg-pics: how to check for hidden or even malicious data in jpg?
Summary: Unclear status of jpg-pics: how to check for hidden or even malicious data in...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Bqm-Convert (show other bugs)
Version: 2.1.1
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-21 19:27 UTC by Axel Krebs
Modified: 2016-07-04 08:29 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.0.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Axel Krebs 2012-02-21 19:27:41 UTC
Version:           2.1.1 (using KDE 4.7.4) 
OS:                Linux

Dear all:

I have some hundres of jpg-pics woith pairwise diffeent length. 
I can open most of these pics without aqppearing problems.

When thinking about these different lengths, I come across different metadata. Other data could be included in hidden. 

I there a way to "normalize" jpg´s to take away all not visual data contained?

Please let me know

Thank you,


Axel

Reproducible: Always

Steps to Reproduce:
Just having a look at pairs of pics. 

Actual Results:  
Just having a look at pairs of pics. 

Expected Results:  
I´d like to understand, and, if neede to "normalize" all jpg pics.

OS: Linux (x86_64) release 3.0.0-16-generic
Compiler: gcc
Comment 1 caulier.gilles 2012-02-21 21:10:26 UTC
Axel,

I don't understand th problem exactly ?

Gilles Caulier
Comment 2 Axel Krebs 2012-02-22 00:35:59 UTC
I ask myself, if there is a way to check the questioned pics for
integrity and/or the existance/absence of non-visual ("hidden") information.

Onw way to achieve this could be, to erase those secondary data to get a
standardized pic _without_ this information.


Am 21.02.2012 22:10, schrieb Gilles Caulier:
> https://bugs.kde.org/show_bug.cgi?id=294580
> 
> 
> Gilles Caulier <caulier.gilles@gmail.com> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |caulier.gilles@gmail.com
> 
> 
> 
> 
> --- Comment #1 from Gilles Caulier <caulier gilles gmail com>  2012-02-21 21:10:26 ---
> Axel,
> 
> I don't understand th problem exactly ?
> 
> Gilles Caulier
>
Comment 3 caulier.gilles 2012-02-22 06:12:26 UTC
What do you mean by hidden information ?

Gilles Caulier
Comment 4 Christoph Feck 2012-02-22 11:15:29 UTC
Axel wants to remove comments and any other metadata, which is not needed to reproduce the image data.
Comment 5 caulier.gilles 2012-02-22 11:20:36 UTC
All digiKam metadata are visible through Captions & Tags from right sidebar.

If he want to remove these info, for example to export images, Batch Queue Manager has a tool to remove metadata.

Gilles Caulier
Comment 6 Axel Krebs 2012-02-22 19:04:13 UTC
Am 22.02.2012 12:20, schrieb Gilles Caulier:
> https://bugs.kde.org/show_bug.cgi?id=294580
> 
> 
> 
> 
> 
> --- Comment #5 from Gilles Caulier <caulier gilles gmail com>  2012-02-22 11:20:36 ---
> All digiKam metadata are visible through Captions & Tags from right sidebar.
> 
> If he want to remove these info, for example to export images, Batch Queue
> Manager has a tool to remove metadata.
> 
> Gilles Caulier
> 
Dear all:

Excuse me for late answering.

I have numbers of pairwise different pics. As much as I can see, most of
these pics open ok.

All have the _same_ original file, still they have _different_ sizes.
For this reason, I assumed the size differences must be related to
different metadata.

Here, I assumed additionally, that different metadata produce different
sizes.

For this reason, I´d like to create a "minimum standard" file without
(or with controlled) metadata content.

Batch maybe a good solution, if metadata removing works reliable.

Thank you for your consideration-


Axel
Comment 7 caulier.gilles 2013-12-19 13:39:56 UTC
A tool in BQM exist to remove all metadata at export time...

Gilles Caulier