Running console apps on n950: Operation not permitted

[svlasov]

Hello,

I wrote a "hello world" app but can't run it on the phone.

#include <stdio.h>

int main(int argc, char **argv)
{
	printf("hello world!\n");
	return 0;
}

sbox-HARMATTAN_ARMEL:~/helloworld$ make
gcc main.c -o hello
sbox-HARMATTAN_ARMEL:~/helloworld$ ./hello 
hello world!
sbox-HARMATTAN_ARMEL:~/helloworld$ file hello 
hello: ELF 32-bit LSB executable, ARM, version 1 (SYSV), for GNU/Linux 2.6.16, dynamically linked (uses shared libs), not stripped
sbox-HARMATTAN_ARMEL:~/helloworld$ scp hello root@n950:/root
sbox-HARMATTAN_ARMEL:~/helloworld$ ssh root@n950
RM680-22-6_PR_RM680:~# chmod +x hello
RM680-22-6_PR_RM680:~# ./hello 
-sh: ./hello: Operation not permitted
RM680-22-6_PR_RM680:~# ls -l
total 8
-rwxr-xr-x    1 root     root          5540 Jul 11 12:13 hello

However no problem running it in QEMU. Please help!

[divanov]

Security framework prevents unregistered binaries execution. Place your binary in a Debian package and install it, then it will be properly registered and you will be able to execute it.

[svlasov]

Well, that's really troublesome to package every single binary/test-app. Is there a way to disable this Security framework? After all I'm playing with a developer device.

[divanov]

Qt Creator produces template package for the project you build. Even if you are not using Qt Creator for development you can open it once to have a Debian packaging.

[kypeli]

Regarding the Security FW; I have not been able to find any documentation about it. Is there any that would be relevant for developers?

But I have to agree, that this is an unnecessary inconvenience for the developers not to be able to run on their own device their own test scripts with the Security FW disabled. After all, the developer devices are in developer mode already, while N9 consumer devices are not, it would make sense to have this disabled. Of course if the application is to be distributed through OVI store (err, Nokia Store) then the packaging must be done.

[svlasov]

Agree, it should be allowed to disable the Security FW when the device is in developer mode, we are talking about N950 and not N9. Qt Creator templates won't work in every situation, also re-installing the package after every build is a serious hassle for me.

[svlasov]

Found something relevant there http://talk.maemo.org/showthread.php?t=73231. It seems that the security framework is using DigSig http://disec.sourceforge.net/ Now the question is how to disable it?

[achipa]

Regarding the Security FW; I have not been able to find any documentation about it. Is there any that would be relevant for developers?

http://library.developer.nokia.com/t...rity_6cbe.html

[kypeli]

Thanks! Still no documentation on how to disable the Security FW :-/

[divanov]

Qt Creator templates won't work in every situation, also re-installing the package after every build is a serious hassle for me.

Could you please provide an example, where template won't work?

[svlasov]

for projects that don't follow the unix-way and use messy file structure, while when packaging one supposed to install files into proper locations: executable to bin/, binaries to lib/, resources to share/ etc.

but well, let me prove myself wrong that packaging is fun and easy. I want to use scratchbox and not Qt Creator templates, so I followed the packaging guide http://www.developer.nokia.com/Commu...n_Platform_SDK

sbox-HARMATTAN_X86:~/coolproject$ dh_make -e hello@there.com -f ../coolproject-0.1.tar.gz -c GPL
bash: dh_make: command not found
sbox-HARMATTAN_X86:~/coolproject$ dpkg -L debhelper | grep dh_make
/usr/share/man/man1/dh_makeshlibs.1.gz
/usr/share/man/fr/man1/dh_makeshlibs.1.gz
/usr/bin/dh_makeshlibs

Where is dh_make?

[divanov]

for projects that don't follow the unix-way and use messy file structure, while when packaging one supposed to install files into proper locations: executable to bin/, binaries to lib/, resources to share/ etc.

You are supposed to install standalone executables into /usr/bin/... Any how installation is something Debian package rules takes care off, if you have working qmake configuration, it will do the rest.

Where is dh_make?

dh_make is in dh-make package.

[svlasov]

You are supposed to install standalone executables into /usr/bin/...

Not always it's just a single standalone executable

Any how installation is something Debian package rules takes care off

That's what I mean, I have to take care of 'rules' file + I need to modify the project to find its files after they were installed into different locations. With Security FW disabled I would just copy over the whole build to /home/user/ and execute it from there, that's how I do it on N900.

if you have working qmake configuration, it will do the rest.

Projects are not always Qt-based

dh_make is in dh-make package.

There is no 'dh-make' package in scratchbox repositories, should I enable some extra repo?

[helex]

I've at the moment exactly the same problem.

I created a small *.sh script using vi, chmod to executable. And now I got "Operation not permitted"

Could I "checkin" my small script into the security framework?

[kypeli]

I've at the moment exactly the same problem.
I created a small *.sh script using vi, chmod to executable. And now I got "Operation not permitted"

You can run shell scripts with "sh < myscript.sh" - which in its own demonstrates how un-useful the Security FW is since it cannot block random shell scripts from being executed. Just an annoyance for us, developers.