Will the paper size B5-paper (17cm by 24cm) you suggested include the front, back & spine or is this just the size of the front????

Thank you for your question, I have dug into the publishers requirements and now have more explicit sizes:

The finished book will have dimensions 17cm by 24cm by ?cm.
The (flat-)spine thickness is yet unknown, but will probably be about 1cm.

The cover design thus needs from left-to-right:
- a back of 17cm by 24cm
- in between a spine of about 1cm by 24cm
- a front of 17cm by 24cm
Around this design a 3mm bleeding/cutoff edge is needed
(leading to a total height of 24.6 cm and total width of 35.6cm).
The spine-fold is located 7mm from the spine on the front and back cover,
so the title etc. should be removed at least 1cm from the spine.

Hi,
Do you want to place any matter or author message on the back side ?

Thanks & REgards
Avi

Hi,

no matter or author message is planned for the back side.

As a book, a PhD thesis is not commercial.

The cover is used for presentation and to reflect on its academic contents,

often in very abstract illustrations.

The cover does not need to ''sell'' the book as with commercial books,

as readers will not choose a thesis by the cover, but focused on specific research topics.

My thesis is focused on hash functions: a software program that computes a ''fingerprint'' for files.

And specifically on breaking these hash functions by finding two files that have identical ''fingerprints''.

Two such files are found by making sure that the differences between the two computations of the ''fingerprint'' follow some ''differential path''.

This is for instance illustrated in the following image:

http://www.win.tue.nl/hashclash/rogue-ca/images/botsing.png

In this image there are 15 blocks separated by yellow lines:

- a black pixel represents a bit that is the same in the fingerprint-computation for both files

- a red/blue pixel represents a positive/negative difference in a bit in the fingerprint-computation

As you can see, the first 8 block have random bit-differences.

The attack takes place in the next 3 blocks where there are very few and very structured bit-differences.

After the attack no bit-differences occur anymore and this leads to identical ''fingerprints''.

Hi,
Feedback appreciated.


Thanks & Regards
Avi

Hi all,

I have received many designs, however I still miss more reflection to the contents.
I know it is very technical stuff, so I''ve been trying to give some ideas to you designers.
So now I want to try some very abstract (non-technical) ideas.


My thesis is all about attacks on digital fingerprints and more specifically how to alter two files such that they result in the exact same digital fingerprint.

In the real world, two different persons with the same fingerprint can cause all sorts of problems, where the one person can do all sorts of stuff in the name of the other person (say entering an authorized persons only building that uses fingerprint scanners).

The same holds for digital fingerprints: one harmless file can be scrutenized and its fingerprint put into a white-list. The second file can then avoid further scruteny and cause harm.
Think for instance of an original "Microsoft Windows Security Patch" file that shares its fingerprint with a virus-infected version of the file.

So the core abstract idea would be that there are two files with the same fingerprint.
Where one file is harmless and the other can be harmful.

Hi,
Please find the revised design of mine.

Feedback appreciated

Thanks & Regards
Avi