EldoS | Feel safer!

Software components for data protection, secure storage and transfer

Invalid signature after Signing PDF - "document has been changed"

Also by EldoS: MsgConnect
Cross-platform protocol-independent communication framework for building peer-to-peer and client-server applications and middleware components.
#13947
Posted: 07/16/2010 10:28:08
by Roman Krejci (Basic support level)
Joined: 07/15/2010
Posts: 8

Hi Dmytro, things are OK now. I had the correct version installed.
I did not have previous versions of SecureBlackBox installed on
the Win7 machine, however, I did copy Borland registry keys and
Borland program files folders from the old machine when upgrading.
Don't know whether this has any meaning.
It seems that there were some problems with License, because
the compiled project first warned that the licence is not valid
(I ignored this one), and later on it raised an exception during
signature addition telling that I need some other license -
(I got across this by using an obvious hack during Delphi debug
session)

Nevertheless - I unistalled BlackBox and installed it again.
From then on, everything works fine - no license warnings and
signed PDF passes the reader test.
It is a big mystery for me how I got into this - probably I became
a victim of Win7 virtual stores. However, I've got no time to examinate
the exact cause.

Many thanks again for quick responses and my apology for
bothering you with this issue.

Regards

Roman Krejci
#13948
Posted: 07/16/2010 10:47:01
by Roman Krejci (Basic support level)
Joined: 07/15/2010
Posts: 8

I think I discovered it - seems that I did copy the
ProgramFiles\EldoS folder from the old machine when
upgrading some months ago. The unit and packages part
of EldoS Program files subfolder has been overwritten
during current package installation this week
However, the Samples subfolder did remain there from
the old copy, while the correct Samples subfolder
now installs into Documents by default.
I did not notice that and used the old Samples projects
located under Program Files.
So it looks like I compiled the old sample TinySigner
project while using new version of the evaluation DCU's.
Is this possible cause?

Roman Krejci
#13951
Posted: 07/16/2010 15:55:24
by Dmytro Bogatskyy (EldoS Corp.)

Quote
things are OK now

Great!
Quote

the compiled project first warned that the licence is not valid
(I ignored this one), and later on it raised an exception during
signature addition telling that I need some other license -
(I got across this by using an obvious hack during Delphi debug
session)
...
So it looks like I compiled the old sample TinySigner
project while using new version of the evaluation DCU's.
Is this possible cause?

Yes, it is possible.
The old sample have an old license key that doesn't work with version 8.0 (as said in message "the licence is not valid", and continuing execution could lead to unexpected behavior like an invalid signature).

Reply

Statistics

Topic viewed 3372 times

Number of guests: 1, registered members: 0, in total hidden: 0




|

Back to top

As of July 15, 2016 EldoS Corporation will operate as a division of /n software inc. For more information, please read the announcement.

Got it!