Code Signing Certificate Expiration Date: 850 day(s)

[NewsArchive]

Hello Friedrich,

for the first time ever I noticed that line at the end of the compile log:

Code Signing Certificate Expiration Date: 850 day(s)

That is simply a reminder to put some bucks into the socket to have enough
cash to shell out to Comodo in 850 days?

It does NOT mean that my install-file made today are invalid or
not-code-signed anymore on day 851?

I have, of course, added that timestamp-URL
http://timestamp.comodoca.com/authenticode.

But as I am easy to scare, I decided to ask the Master who knows
Everything!

Ich wünsche ein schönes Wochenende dann noch (gehabt zu haben)


--
Wolfgang Orth

www.odata.de
www.kik-service.de


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

It's five o'clock somewhere.....




Written with Operas News-/ Mailclient: http://www.opera.com/mail/

[NewsArchive]

Wolfgang,

> That is simply a reminder to put some bucks into the socket to have enough
> cash to shell out to Comodo in 850 days?

That's it, just a reminder so you take care of it when needed.

--
Lee White

RPM Report Viewer.: http://www.cwaddons.com/products/rpm/
RPM Review........: http://www.clarionmag.com/cmag/v11/v11n06rpm.html
Report Faxing.....: http://www.cwaddons.com/products/afe/
---Enroll Today---: http://CWaddons.com

Enhanced Reporting: http://CreativeReporting.com


Product Release & Update Notices
http://twitter.com/DeveloperPLUS

[NewsArchive]

Hello Wolfgang,

>
> for the first time ever I noticed that line at the end of the compile log:
>

It's this improvement in 7.7 Build 3648

IMPROVEMENT: [SB#202031] IDE: The compiler displays the code signing
expiration date in the compiler window. If the expiration
date is < 45 days, it gives a compiler warning. The warning
is skipped in command line compilation mode.

> It does NOT mean that my install-file made today are invalid or
> not-code-signed anymore on day 851?

If you timestamp, then you are safe! If you do NOT timestamp then your
application does not have a valid signature in 851 days.

When you sign code, a hash of your code will be sent to Certification
authority to be timestamped. This means that you will not need to worry
about re-signing code when your Digital ID expires. Microsoft Authenticode
allows you to timestamp your signed code so that signatures will not expire
when your certificate does.

Friedrich

[NewsArchive]

> It's this improvement in 7.7 Build 3648
>
> IMPROVEMENT: [SB#202031] IDE: The compiler displays the code signing
> expiration date in the compiler window. If the expiration
> date is < 45 days, it gives a compiler warning. The warning
> is skipped in command line compilation mode.

You expect me to read the improvement list, eh?



>> It does NOT mean that my install-file made today are invalid or
>> not-code-signed anymore on day 851?
>
> If you timestamp, then you are safe! If you do NOT timestamp then your
> application does not have a valid signature in 851 days.

Thats what I expected, but it made me nervous when I read that line, as it
was new and unknown to me.

To be honest, it scared the hell out of me!

Old people and autists strongly dislike modifications in their daily work
- especially old autists!

How about a friendly warning, like:

"eh, you, moron, eh, its better you timestamp your stuff!"

just in case someone has forgotten......

Sincerly, your ever obedient
Caspar Milquetoast



--
Wolfgang Orth

www.odata.de
www.kik-service.de

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

It's five o'clock somewhere.....




Written with Operas News-/ Mailclient: http://www.opera.com/mail/

[NewsArchive]

Hi Friedrich

I am on build 7.7 3648 and I cannot find the code signing sert expiration date on
screen anywhere after a build. Not on the Compile screen, or in the .HTM log report or
the .CSV

I can see after signing files with SB7.7 that my certificate is good until 1 / 03/
2013.

John Griffiths

[NewsArchive]

Hi John,

> I am on build 7.7 3648 and I cannot find the code signing sert expiration
> date on screen anywhere after a build. Not on the Compile screen, or in
> the
> .HTM log report or the .CSV
>
> I can see after signing files with SB7.7 that my certificate is good until
> 1 / 03/ 2013.

If you have the uninstall option enabled and you code-sign your setup with a
key that is part of Microsoft's chain of trust then you should see something
like the following (see screenshot).

Friedrich

[NewsArchive]

Hi Friedrich

I am not using the UnInstall option. That would explain it.
Hell, who want their software uninstalled? <G>

JohnG

[NewsArchive]

> Hello Wolfgang,
>
>>
>> for the first time ever I noticed that line at the end of the compile log:
>>
>
> It's this improvement in 7.7 Build 3648
>
> IMPROVEMENT: [SB#202031] IDE: The compiler displays the code signing
> expiration date in the compiler window. If the expiration
> date is < 45 days, it gives a compiler warning. The warning
> is skipped in command line compilation mode.

Friedrich, THANK You very much! Over the years, some were definitely
"embarassed" or "dis-comforted" by overlooking a timely renewal.

Does Lindersoft SetupBuilder 7.7 Build 3648 now offer the ability to
autoload K-Cups with Keurig Signature Brewer and brew the coffee, or will
we still have to manually insert K-Cups, and wait for this future feature?
:-)

David

--
From David Troxell - Product Scope 7.9 - Encourager Software
Product Description - App Data UAC Safe, MFG - Encourager Software
Internet Link - http://www.encouragersoftware.com/software-developers.html

[NewsArchive]

> Friedrich, THANK You very much! Over the years, some were definitely
> "embarassed" or "dis-comforted" by overlooking a timely renewal.
>
> Does Lindersoft SetupBuilder 7.7 Build 3648 now offer the ability to
> autoload K-Cups with Keurig Signature Brewer and brew the coffee, or
> will we still have to manually insert K-Cups, and wait for this
> future feature?
> :-)

<G> ;-)

Friedrich