We Need A Standard Layered Image Format

Re:We Need A Standard Layered Image Format by rlpb on Tuesday April 30, 2013 @05:54PM (#5635117)

Won't this format leave behind traces of what was in the file before? I'm not sure that this is something that we want in a standard interchange format. Users will assume what they are sending is only what they see in an application. This is reasonable. I am concerned that using this format will lead to data leaks.

[ Parent | on HN ]

Re:We Need A Standard Layered Image Format by SQLite on Tuesday April 30, 2013 @07:55PM (#5635648)

Not if you set "PRAGMA secure_delete=ON;" See http://www.sqlite.org/pragma.html#pragma_secure_delete for additional information.

[ Parent | on HN ]

Re:We Need A Standard Layered Image Format by eurleif on Tuesday April 30, 2013 @06:26PM (#5635270)

It could be defined in the format spec that applications should VACUUM the database after every save.

[ Parent | on HN ]

Re:We Need A Standard Layered Image Format by angersock on Tuesday April 30, 2013 @06:18PM (#5635226)

That ship has pretty much sailed with EXIF and embedded metadata anyways, right?

This would seem to be more targeted at digital content creation (and toolchain application interop) than a normal-use file format.

[ Parent | on HN ]

Re:We Need A Standard Layered Image Format by rlpb on Tuesday April 30, 2013 @06:25PM (#5635262)

It's up to your editor what metadata it chooses to save. It is not up to your editor what data was in the sqlite row that it just modified or deleted but may still be forensically available. There is a fundamental difference here.

It is possible to clean it up of course - perhaps by vacuuming, or definitely by copying to a new file at database level. But it seems dangerous to me to start with a native format with this behavior and attempt to clean it up later.

[ Parent | on HN ]

Re:We Need A Standard Layered Image Format by eurleif on Tuesday April 30, 2013 @06:36PM (#5635315)

>But it seems dangerous to me to start with a native format with this behavior and attempt to clean it up later.

File formats don't have behaviors. Programs do.

Lots of binary formats, including PNG, will ignore any extra junk after the end of the file. So if a change makes a PNG file smaller, there's nothing stopping a program from leaving data from the old version at the end. But that's not normal behavior for programs that write PNG, so it's not an issue.

As long as programs adopted the behavior of VACUUMing the database, this wouldn't be an issue either.

[ Parent | on HN ]

Re:We Need A Standard Layered Image Format by seanalltogether on Tuesday April 30, 2013 @06:54PM (#5635405)

How is that different from a psd or editable fireworks png file? I can have several groups with various visibility toggles that any normal user wouldn't see unless they dig into the layers.

[ Parent | on HN ]