Re: [OT] unhosing .rev and .livecode files

[Jerry Jensen]

Just one additional level of warning - if you keep Dropbox or Google Drive 
online, malware can get there too. Usually the baddies just trash your 
directory, but if they encrypt everything you have accessible online, Dropbox 
and Google Drive won’t help you. Offline backup is essential, offsite is even 
better.

> On Dec 3, 2016, at 6:46 PM, Kay C Lan  wrote:
> 
> Hi Richmond,
> 
> Glad to hear that you've been able to rescue most of your files. The
> Data Rescue programme I use is imaginatively called 'Data Rescue' by
> Prosoft. I don't think it would help in your case as I don't think the
> Mac version can recover non-Mac HDs. The reason I mention it is that
> it has a feature called 'FileIQ', so you drag a .livecode file onto
> FileIQ, it then learns the structure of an LC file, then you can Start
> Data Rescue to search all similar such files on a HD. I'm sure it
> wouldn't be the only Disk Rescue programme that supported such a
> feature.
> 
> Good luck.
> 
> PS. Every single LC stack I create, no matter how large, small,
> trivial or world changing, sits in a suitably named folder within a
> generic folder 'my stacks' which lives on my Google Drive. I have
> plenty of back-up options (as covered by Richard) as I just can't
> afford to loose a HD, but for reasons I can't explain, for LC Stacks I
> feel it necessary to have quadruple redundancy back-up. Some one on
> this List mentioned using Dropbox or Google Drive as a working
> location for their stacks, and since following that advise I've been
> most thankful. No fuss, no thought, works a treat.
> 
> ___
> 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: live code seems to gratuitously unlock write permission for directories

[Stephen Barncard]

This has been standard practice for shared hosting at Dreamhost for years.
I made an index.irev file that looked at the contents of the directory and
displayed a list, subject to filtering. Parameters set with simple txt
file. Very easy.

sqb

--
Stephen Barncard - Sebastopol Ca. USA -
mixstream.org

On Sat, Dec 3, 2016 at 3:10 PM, Mike Bonner  wrote:

> Most likely directory browsing is turned off.  You could change the
> setting, or you could put in an irev that gets "the files" and builds a
> link list dynamically, minus itself of course.
>
> On Sat, Dec 3, 2016 at 3:54 PM, Alex Tweedly  wrote:
>
> > You're right - and I confess I don't know why the downloads folder is
> > inaccessible. Permission is set to 755, and there's no .htaccess file or
> > anything else I know of to prevent it.
> >
> > Anyway - if you wanted the taskrunner files, they are :
> >  - taskrunner.rev
> >  - taskClientLib.rev
> >  - test-task-runner.rev
> >  - verybusy.rev
> >  - IndexFiles.rev
> >  - CheckURL.rev
> >
> > and each one can be downloaded individually, for example
> >
> > http://tweedly.org/downloads/taskrunner.rev
> >
> >
> > I guess I'll just have to find a silver lining . this must be a
> > security measure to keep files hidden unless I reveal the actual URLs.
> And
> > I will very shortly change the taskRunner page to make the file entry
> line
> > into links that are clickable.
> >
> > (and btw, although I do still use taskRunner regularly, I haven't rebuilt
> > the executables since probably LC 5.0 - so approach with some caution :-)
> >
> > -- Alex.
> >
> >
> > On 03/12/2016 20:54, Alejandro Tejada wrote:
> >
> >> Hi Alex,
> >>
> >> Downloads folder in your server is not accessible.
> >>
> >> It's not possible to download this stack either:
> >> http://tweedly.org/showpage.lc?page=taskRunner
> >>
> >> Al
> >>
> >> ___
> >> 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
>
___
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: [OT] unhosing .rev and .livecode files

[Kay C Lan]

Hi Richmond,

Glad to hear that you've been able to rescue most of your files. The
Data Rescue programme I use is imaginatively called 'Data Rescue' by
Prosoft. I don't think it would help in your case as I don't think the
Mac version can recover non-Mac HDs. The reason I mention it is that
it has a feature called 'FileIQ', so you drag a .livecode file onto
FileIQ, it then learns the structure of an LC file, then you can Start
Data Rescue to search all similar such files on a HD. I'm sure it
wouldn't be the only Disk Rescue programme that supported such a
feature.

Good luck.

PS. Every single LC stack I create, no matter how large, small,
trivial or world changing, sits in a suitably named folder within a
generic folder 'my stacks' which lives on my Google Drive. I have
plenty of back-up options (as covered by Richard) as I just can't
afford to loose a HD, but for reasons I can't explain, for LC Stacks I
feel it necessary to have quadruple redundancy back-up. Some one on
this List mentioned using Dropbox or Google Drive as a working
location for their stacks, and since following that advise I've been
most thankful. No fuss, no thought, works a treat.

___
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: Non-Public API Usage

[pink]

I have not used those names, so I submitted it:

http://quality.livecode.com/show_bug.cgi?id=18958



--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/Non-Public-API-Usage-tp4710840p4710842.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: Non-Public API Usage

[Mark Schonewille]

Hi Pink,

If you are using the names _getcontext, _makecontext and _setcontext for 
your handlers in your scripts, just change the names and make sure they 
are nowhere mentioned in your app. If you didn't use these handler 
names, report it as a bug to the QCC.


Kind regards,

Mark Schonewille
http://economy-x-talk.com
https://www.facebook.com/marksch

Buy the most extensive book on the
LiveCode language:
http://livecodebeginner.economy-x-talk.com

Op 04-Dec-16 om 01:03 schreef pink:

I compiled and submitted an app using iTunes Connect. I received the
following rejection message.

I compiled using Livecode 8.1.2 rc2, I have Xcode 8.1 installed. I tried
recompiling a few times and got the same results each time.

How do I fix this?

Dear developer,

We have discovered one or more issues with your recent delivery for
"PlanningBoard 2". To process your delivery, the following issues must be
corrected:

Non-public API usage:

The app references non-public symbols in MadPink Planning Board:
_getcontext, _makecontext, _setcontext
If method names in your source code match the private Apple APIs listed
above, altering your method names will help prevent this app from being
flagged in future submissions. In addition, note that one or more of the
above APIs may be located in a static library that was included with your
app. If so, they must be removed.

If you think this message was sent in error and that you have only used
Apple-published APIs in accordance with the guidelines, send the app's
nine-digit Apple ID, along with detailed information about why you believe
the above APIs were incorrectly flagged, to apprev...@apple.com. For further
information, visit the Technical Support Information page.

Though you are not required to fix the following issues, we wanted to make
you aware of them:

Missing Push Notification Entitlement - Your app includes an API for Apple's
Push Notification service, but the aps-environment entitlement is missing
from the app's signature. To resolve this, make sure your App ID is enabled
for push notification in the Provisioning Portal. Then, sign your app with a
distribution provisioning profile that includes the aps-environment
entitlement. This will create the correct signature, and you can resubmit
your app. See "Provisioning and Development" in the Local and Push
Notification Programming Guide for more information. If your app does not
use the Apple Push Notification service, no action is required. You may
remove the API from future submissions to stop this warning. If you use a
third-party framework, you may need to contact the developer for information
on removing the API.

Once the required corrections have been made, you can then redeliver the
corrected binary.

Regards,

The App Store team




___
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

Non-Public API Usage

[pink]

I compiled and submitted an app using iTunes Connect. I received the
following rejection message.

I compiled using Livecode 8.1.2 rc2, I have Xcode 8.1 installed. I tried
recompiling a few times and got the same results each time.

How do I fix this?

Dear developer,

We have discovered one or more issues with your recent delivery for
"PlanningBoard 2". To process your delivery, the following issues must be
corrected:

Non-public API usage:

The app references non-public symbols in MadPink Planning Board:
_getcontext, _makecontext, _setcontext
If method names in your source code match the private Apple APIs listed
above, altering your method names will help prevent this app from being
flagged in future submissions. In addition, note that one or more of the
above APIs may be located in a static library that was included with your
app. If so, they must be removed.

If you think this message was sent in error and that you have only used
Apple-published APIs in accordance with the guidelines, send the app's
nine-digit Apple ID, along with detailed information about why you believe
the above APIs were incorrectly flagged, to apprev...@apple.com. For further
information, visit the Technical Support Information page.

Though you are not required to fix the following issues, we wanted to make
you aware of them:

Missing Push Notification Entitlement - Your app includes an API for Apple's
Push Notification service, but the aps-environment entitlement is missing
from the app's signature. To resolve this, make sure your App ID is enabled
for push notification in the Provisioning Portal. Then, sign your app with a
distribution provisioning profile that includes the aps-environment
entitlement. This will create the correct signature, and you can resubmit
your app. See "Provisioning and Development" in the Local and Push
Notification Programming Guide for more information. If your app does not
use the Apple Push Notification service, no action is required. You may
remove the API from future submissions to stop this warning. If you use a
third-party framework, you may need to contact the developer for information
on removing the API.

Once the required corrections have been made, you can then redeliver the
corrected binary.

Regards,

The App Store team



--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/Non-Public-API-Usage-tp4710840.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: live code seems to gratuitously unlock write permission for directories

[Mike Bonner]

Most likely directory browsing is turned off.  You could change the
setting, or you could put in an irev that gets "the files" and builds a
link list dynamically, minus itself of course.

On Sat, Dec 3, 2016 at 3:54 PM, Alex Tweedly  wrote:

> You're right - and I confess I don't know why the downloads folder is
> inaccessible. Permission is set to 755, and there's no .htaccess file or
> anything else I know of to prevent it.
>
> Anyway - if you wanted the taskrunner files, they are :
>  - taskrunner.rev
>  - taskClientLib.rev
>  - test-task-runner.rev
>  - verybusy.rev
>  - IndexFiles.rev
>  - CheckURL.rev
>
> and each one can be downloaded individually, for example
>
> http://tweedly.org/downloads/taskrunner.rev
>
>
> I guess I'll just have to find a silver lining . this must be a
> security measure to keep files hidden unless I reveal the actual URLs. And
> I will very shortly change the taskRunner page to make the file entry line
> into links that are clickable.
>
> (and btw, although I do still use taskRunner regularly, I haven't rebuilt
> the executables since probably LC 5.0 - so approach with some caution :-)
>
> -- Alex.
>
>
> On 03/12/2016 20:54, Alejandro Tejada wrote:
>
>> Hi Alex,
>>
>> Downloads folder in your server is not accessible.
>>
>> It's not possible to download this stack either:
>> http://tweedly.org/showpage.lc?page=taskRunner
>>
>> Al
>>
>> ___
>> 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: live code seems to gratuitously unlock write permission for directories

[Alex Tweedly]

You're right - and I confess I don't know why the downloads folder is 
inaccessible. Permission is set to 755, and there's no .htaccess file or 
anything else I know of to prevent it.


Anyway - if you wanted the taskrunner files, they are :
 - taskrunner.rev
 - taskClientLib.rev
 - test-task-runner.rev
 - verybusy.rev
 - IndexFiles.rev
 - CheckURL.rev

and each one can be downloaded individually, for example

http://tweedly.org/downloads/taskrunner.rev


I guess I'll just have to find a silver lining . this must be a 
security measure to keep files hidden unless I reveal the actual URLs. 
And I will very shortly change the taskRunner page to make the file 
entry line into links that are clickable.


(and btw, although I do still use taskRunner regularly, I haven't 
rebuilt the executables since probably LC 5.0 - so approach with some 
caution :-)


-- Alex.


On 03/12/2016 20:54, Alejandro Tejada wrote:

Hi Alex,

Downloads folder in your server is not accessible.

It's not possible to download this stack either:
http://tweedly.org/showpage.lc?page=taskRunner

Al

___
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: live code seems to gratuitously unlock write permission for directories

[Alex Tweedly]

Very strange - the correct URL is 
http://tweedly.org/downloads/checkpermissionsetting.livecode


i.e. without the last 's'

Did you know that, in Chrome, if you modify the URL, and it turns out to 
be a downloadable file - then Chrome downloads it, and then changes the 
visible URL in the address bar back to what it was before !!   So - very 
sorry, the  correct address is indeed


http://tweedly.org/downloads/checkpermissionsetting.livecode (checked 
and downloaded in a new Chrome window :-)


-- Alex.



On 03/12/2016 19:32, Dr. Hawkins wrote:

On Sat, Dec 3, 2016 at 9:47 AM, Alex Tweedly  wrote:


It's at http://tweedly.org/downloads/checkpermissionsettings.livecode



Not Found

The requested URL /downloads/checkpermissionsettings.livecode was not found
on this server.

Additionally, a 404 Not Found error was encountered while trying to use an
ErrorDocument to handle the request.




___
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

live code seems to gratuitously unlock write permission for directories

[Alejandro Tejada]

Hi Alex,

Downloads folder in your server is not accessible.

It's not possible to download this stack either:
http://tweedly.org/showpage.lc?page=taskRunner

Al

___
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: live code seems to gratuitously unlock write permission for directories

[Dr. Hawkins]

On Sat, Dec 3, 2016 at 9:47 AM, Alex Tweedly  wrote:

> It's at http://tweedly.org/downloads/checkpermissionsettings.livecode
>


Not Found

The requested URL /downloads/checkpermissionsettings.livecode was not found
on this server.

Additionally, a 404 Not Found error was encountered while trying to use an
ErrorDocument to handle the request.

-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
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: [OT] unhosing .rev and .livecode files

[Richmond Mathewson]

That sounds great, but I wonder exactly how I should look for the file 
headers.


Richmond.

On 12/3/16 7:42 pm, Stephen Barncard wrote:

On Sat, Dec 3, 2016 at 7:58 AM, Richmond Mathewson <
richmondmathew...@gmail.com> wrote:


files, and NOT .rev and .livecode files I wonder if anyone has any bright
suggestions how one might
go about looking for them.


Look for the file header text at the beginning of every stack:

like
REVO7000
REVO5500

you may need to do research on the headers for the vintage stack formats.
--
Stephen Barncard - Sebastopol Ca. USA -
mixstream.org
___
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: live code seems to gratuitously unlock write permission for directories

[Alex Tweedly]

OK, I got slightly lost in this thread - we've gone off to solve a 
work-around to your problem, and I'd like to go back to the problem itself.



If I understood it properly, what you;re seeing is that setting the 
permission of a directory to disallow write *should* prevent you from 
saving a stack within that directory - but it doesn't.


So I decided to write a small test stack that did just that, and see how 
it performs. And it does just what I would expect (which I think is the 
same as you would expect :-)


I know it's unhelpful, even annoying, to be told "it works OK for me" - 
but it works ok for me.


Could I ask you to download my simple stack, and try it out in your 
environment - ideally on the same directory - and report back on what it 
does ? Hopefully this will isolate whether it's your 
OS/filesystem/environment or something else going on in your scrips.


It's at http://tweedly.org/downloads/checkpermissionsettings.livecode

very simple stack - 4 buttons

 - one let's you specify a directory

 - one checks the permission of that directory and write that to the 
msg box


 - one removes write permission on the specified folder

 - the last one adds write permisison.

I actually saved this stack within the folder so I was testing something 
as close as possible to what I thought was your situation.


So you should find that after specifying the folder, you can check the 
permissions, save the stack, remove write permission, check permissions 
(and see that it's gone), then try to save the stack again - and it 
fails. Then add wrote permission back again, chek permissions and then 
save - works OK.


Thanks

-- Alex.



On 02/12/2016 20:34, Dr. Hawkins wrote:

I've added the following after setting the name, and also moved the save
into this block:

*if* (char 1 to 6 of bkNm) <> (char -17 to -12 of the long name of this
stack) *then*

*--date has changed*

bmpVrsn stkNm

*else*

*save* this stack

*end* *if*


bmpVrsn is my routine to bump the filename.  Without this, it would keep
backing up yesterday's file . . .




___
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: [OT] unhosing .rev and .livecode files

[Stephen Barncard]

On Sat, Dec 3, 2016 at 9:42 AM, Stephen Barncard 
wrote:

> Look for the file header text at the beginning of every stack:
>
> like
> REVO7000
> REVO5500
>

There should also be a file termination character(s)

--
Stephen Barncard - Sebastopol Ca. USA -
mixstream.org
___
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: [OT] unhosing .rev and .livecode files

[Stephen Barncard]

On Sat, Dec 3, 2016 at 7:58 AM, Richmond Mathewson <
richmondmathew...@gmail.com> wrote:

> files, and NOT .rev and .livecode files I wonder if anyone has any bright
> suggestions how one might
> go about looking for them.
>

Look for the file header text at the beginning of every stack:

like
REVO7000
REVO5500

you may need to do research on the headers for the vintage stack formats.
--
Stephen Barncard - Sebastopol Ca. USA -
mixstream.org
___
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

[OT] unhosing .rev and .livecode files

[Richmond Mathewson]

Aa all forensic software for digging in blanked hard drives seems to 
find the most obvious
files, and NOT .rev and .livecode files I wonder if anyone has any 
bright suggestions how one might

go about looking for them.

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