maemo.org - Talk - View Single Post - [Announce] vpn9c -- vpnc client with launch GUI for n9...I

	too	2012-08-16 , 12:05
	Posts: 122 \| Thanked: 135 times \| Joined on Dec 2009 @ Helsinki	#23

Originally Posted by rainisto

Thats a false statement, developer mode does not allow you to install with same credentials that ovi store provides. (Only if you have R&D certificate, which normal users don't have). In open mode you can use AEGIS_FIXED_ORIGIN to install with any origin.

Developer mode only adds develsh shell that has same capabilities that ovi origin has, and you have to run develsh with aegis-exec if you want to run with those credentials.

The point of developer mode is that developers can test their
software using (sub)set of the capabilities ovi store provides before
submitting to the ovi store.

Developers don't have devices with R&D certificate.

vpnc.sh requests the following:
<aegis>
<request>
<credential name="CAP::kill" /> 
<credential name="CAP::net_bind_service" />
<credential name="CAP::net_admin" />
<credential name="CAP::net_raw" />

<for path="/opt/vpn9c/bin/vpnc.sh" />
</request>
</aegis>

And it will get those if developer mode is activated -- In my
tests and whoever installs this package when developer mode
is enabled.

When I've started vpnc I get this on terminal:

/home/developer $ accli -I -p $(pgrep vpnc)
Credentials:
UID::user
GID::users
CAP::kill
CAP::net_bind_service
CAP::net_admin
CAP::net_raw
AID::.vpn9c.
vpn9c::vpn9c

(When running from meego-terminal, as 'user' the same output is produced)

I don't have R&D certificate nor open mode device. I Installed
the sw hundreds of times during development using

$ pkgmgr install-file -f vpn9c_*.deb

on command line.

Quote & Reply |