Re: Another naive question about code signing

[Graham Samuel via use-livecode]

Thanks Matthias, that’s very clear!

Graham

> On 14 Jan 2017, at 23:04, Matthias Rebbe via use-livecode 
>  wrote:
> 
> Graham,
> 
> first you have to sign the standalone with all externals. If you are using 
> Ksign.exe then just add the folder,which contains the standalone and its 
> subfolders, in Ksign.
> Please be aware that if your standalone make use of the tsNet external,then 
> you have to change the file attributes of tsnet.dll to be writable before you 
> codesign it. Otherwise Ksign.exe will not be able to sign the tsnet.dll.
> tsnet.dll by default is read only. At least if the Windows standalone is 
> created  on Mac.
> 
> After you have signed the standalone and its externals create the installer 
> and codesign that exe again. 
> 
> That´s how i am doing it.
> 
> Regards,
> 
> Matthias
> 
> 
> 
>> Am 14.01.2017 um 19:47 schrieb Graham Samuel via use-livecode 
>> >:
>> 
>> Having taken a lot of advice from this list and after a delay getting 
>> certificates, I’m about to do some actual code signing for an app that has a 
>> Windows and a Mac version. I am so unsure about the process that i don’t 
>> understand whether I apply the process (let’s say with Ksign for Windows) to 
>> the installer or the app itself.
>> 
>> In my case the installer installs additional files apart from the executable 
>> (all neatly packaged up in the Mac version of course, but separate in the 
>> Windows one). Since an installer is itself executable, I suppose starting an 
>> installer will generate those irritating warnings (yes, I know, they are for 
>> my users’ benefit, but still…) - on that basis, should the installer be 
>> signed? Or should I codesign everything, executables, additional files 
>> (these can be stacks, which are in some sense executable) and the installer 
>> too? I think the latter, but I’m not sure.
>> 
>> This must be blindingly obvious to everyone else, but it is not easy to get 
>> a simple answer from the internet. Of course I will just do it and see what 
>> happens, but I would be glad to understand what ‘normal practice’ might be.
>> 
>> Graham
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com 
>> Please visit this url to subscribe, unsubscribe and manage your subscription 
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Another naive question about code signing

[Matthias Rebbe via use-livecode]

Graham,

first you have to sign the standalone with all externals. If you are using 
Ksign.exe then just add the folder,which contains the standalone and its 
subfolders, in Ksign.
Please be aware that if your standalone make use of the tsNet external,then you 
have to change the file attributes of tsnet.dll to be writable before you 
codesign it. Otherwise Ksign.exe will not be able to sign the tsnet.dll.
tsnet.dll by default is read only. At least if the Windows standalone is 
created  on Mac.

After you have signed the standalone and its externals create the installer and 
codesign that exe again. 

That´s how i am doing it.

Regards,

Matthias



> Am 14.01.2017 um 19:47 schrieb Graham Samuel via use-livecode 
> >:
> 
> Having taken a lot of advice from this list and after a delay getting 
> certificates, I’m about to do some actual code signing for an app that has a 
> Windows and a Mac version. I am so unsure about the process that i don’t 
> understand whether I apply the process (let’s say with Ksign for Windows) to 
> the installer or the app itself.
> 
> In my case the installer installs additional files apart from the executable 
> (all neatly packaged up in the Mac version of course, but separate in the 
> Windows one). Since an installer is itself executable, I suppose starting an 
> installer will generate those irritating warnings (yes, I know, they are for 
> my users’ benefit, but still…) - on that basis, should the installer be 
> signed? Or should I codesign everything, executables, additional files (these 
> can be stacks, which are in some sense executable) and the installer too? I 
> think the latter, but I’m not sure.
> 
> This must be blindingly obvious to everyone else, but it is not easy to get a 
> simple answer from the internet. Of course I will just do it and see what 
> happens, but I would be glad to understand what ‘normal practice’ might be.
> 
> Graham
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com 
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Another naive question about code signing

[Graham Samuel via use-livecode]

Having taken a lot of advice from this list and after a delay getting 
certificates, I’m about to do some actual code signing for an app that has a 
Windows and a Mac version. I am so unsure about the process that i don’t 
understand whether I apply the process (let’s say with Ksign for Windows) to 
the installer or the app itself.

In my case the installer installs additional files apart from the executable 
(all neatly packaged up in the Mac version of course, but separate in the 
Windows one). Since an installer is itself executable, I suppose starting an 
installer will generate those irritating warnings (yes, I know, they are for my 
users’ benefit, but still…) - on that basis, should the installer be signed? Or 
should I codesign everything, executables, additional files (these can be 
stacks, which are in some sense executable) and the installer too? I think the 
latter, but I’m not sure.

This must be blindingly obvious to everyone else, but it is not easy to get a 
simple answer from the internet. Of course I will just do it and see what 
happens, but I would be glad to understand what ‘normal practice’ might be.

Graham
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Tarting up the scriptEditor

[AndyP via use-livecode]

Hi Matthias ,

Im working on this right now and know what and how to sort the error.

The problem is general to LCV8 and LCV9 and not with the OS being used.

There will be an update to Seth later tonight.







-
Andy Piddock 


My software never has bugs. It just develops random features. 

TinyIDETinyIDE a Free alternative minimalist IDE Plugin for LiveCode
TinyIDE 


Script editor Themer for LC http://2108.co.uk  

PointandSee is a FREE simple but full featured under cursor colour picker / 
finder.
http://www.pointandsee.co.uk  - made with LiveCode
--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/Tarting-up-the-scriptEditor-tp4711657p4711662.html
Sent from the Revolution - User mailing list archive at Nabble.com.

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Tarting up the scriptEditor

[Matthias Rebbe via use-livecode]

Hi Andy,

i think it would be a good idea to let the people know that with LC 8, at least 
under Mac OSX there are problems with setting the colors which makes revSeth 
useless if you want to use the dark theme.
The dark theme by default  shows black colored font on black BG and cannot be 
changed although the settings of the theme show correct colors.

After sending this to your issue tracker i noticed, that there is already  a 
confirmed bug report for this in your issue tracker from 24.06.2015. 



Matthias



Matthias Rebbe
Bramkampsieke 13
32312 Lübbecke
Tel +49 5741 31
+49 160 5504462
Fax: +49 5741 310002
eMail: matth...@m-r-d.de 

BR5 Konverter - BR5 -> MP3 
> Am 14.01.2017 um 14:12 schrieb AndyP via use-livecode 
> >:
> 
> Hi Stephen,
> 
> Im in the process of readying the latest version for open source at the
> moment
> Seth will still be a paid for product but password restriction will be
> removed
> 
> 
> 
> 
> -
> Andy Piddock 
> 
> 
> My software never has bugs. It just develops random features. 
> 
> TinyIDETinyIDE a Free alternative minimalist IDE Plugin for LiveCode
> TinyIDE 
> 
> 
> Script editor Themer for LC http://2108.co.uk   
> 
> PointandSee is a FREE simple but full featured under cursor colour picker / 
> finder.
> http://www.pointandsee.co.uk   - made with 
> LiveCode
> --
> View this message in context: 
> http://runtime-revolution.278305.n4.nabble.com/Tarting-up-the-scriptEditor-tp4711657p4711660.html
>  
> 
> Sent from the Revolution - User mailing list archive at Nabble.com 
> .
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com 
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Tarting up the scriptEditor

[AndyP via use-livecode]

Hi Stephen,

Im in the process of readying the latest version for open source at the
moment
Seth will still be a paid for product but password restriction will be
removed




-
Andy Piddock 


My software never has bugs. It just develops random features. 

TinyIDETinyIDE a Free alternative minimalist IDE Plugin for LiveCode
TinyIDE 


Script editor Themer for LC http://2108.co.uk  

PointandSee is a FREE simple but full featured under cursor colour picker / 
finder.
http://www.pointandsee.co.uk  - made with LiveCode
--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/Tarting-up-the-scriptEditor-tp4711657p4711660.html
Sent from the Revolution - User mailing list archive at Nabble.com.

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Tarting up the scriptEditor

[Richmond Mathewson via use-livecode]

Wonderful, but; despite your efforts (and it being confined to 
Commercial versions of LiveCode),

this should be easier for the end user in the Open Source version.

Richmond.

On 1/14/17 12:06 pm, AndyP via use-livecode wrote:

Have a look here

Script editor Themer (SETH) 





-
Andy Piddock


My software never has bugs. It just develops random features.

Copy the new cloud space, get your free 15GB space now:
Get Copy


Script editor Themer for LC http://2108.co.uk

PointandSee is a FREE simple but full featured under cursor colour picker / 
finder.
http://www.pointandsee.co.uk  - made with LiveCode
--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/Tarting-up-the-scriptEditor-tp4711657p4711658.html
Sent from the Revolution - User mailing list archive at Nabble.com.

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Tarting up the scriptEditor

[AndyP via use-livecode]

Have a look here

Script editor Themer (SETH)   





-
Andy Piddock 


My software never has bugs. It just develops random features. 

Copy the new cloud space, get your free 15GB space now:
Get Copy 


Script editor Themer for LC http://2108.co.uk  

PointandSee is a FREE simple but full featured under cursor colour picker / 
finder.
http://www.pointandsee.co.uk  - made with LiveCode
--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/Tarting-up-the-scriptEditor-tp4711657p4711658.html
Sent from the Revolution - User mailing list archive at Nabble.com.

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Tarting up the scriptEditor

[Richmond Mathewson via use-livecode]

It would be lovely if the options for colourising (or even 'colorizing' 
. . .) the

scriptEditor could be extended:

http://forums.livecode.com/viewtopic.php?f=7=28646

Richmond.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode