Posts made by dobey

There is no way to do such a thing. Why do you want to do that?

@futurecn Maybe it would help if you could explain what you're trying to do exactly, rather than making comparisons to features in docker and stating we should have those. It's not easy to provide help, when we cannot understand what exactly you're trying to do.

@futurecn said in How to keep my python running in the container properly while the screen is locked?(N7 2013 flo):

It seems that I cannot run apt install on the original ubuntu out side the container?Why is that?

It is unsupported. UT is not a traditional Linux distribution and phones are not traditional PCs. The rootfs is read-only for these reasons.

@hummlbach said in Q&A 44 This Saturday 16/02/2019 @ 19:00UTC:

@mymike the app developers i have talked to find it makes most sense to use native qqc2 components wherever possible and have only the missing ones on top of qqc2 in our own toolkit. From looking at https://gitlab.com/dobey/ergo/issues/5 it seems thats the idea already pursuit by ergo right @dobey?

Yes, mostly. QQC2 itself is not ideal for much of the convergence landscape, so the idea is that Ergo will be a cohesive converged toolkit based on QQC2.

@Church said in Encryption and vpn:

So encryption is on hold then. looked at the guide and a bit of my depth there. So basically what is the safeguards in place if say a thief would just copy the phone with adb commands, the rootpassword?

Really, there can be no safeguards, because currently we cannot re-lock the bootloader, and even if we had full disk encryption, the key has to be stored on the same flash as the encrypted data. Given that, one could simply copy all data off, and then brute force the wrapped passphrase for the encryption key, to eventually decrypt. Until we can re-lock the bootloader and have recovery without adb, and ideally store the encryption key in the SoC's internal secure key storage rather than on flash, what we can do in UT in terms of physical security is fairly limited.

@mymike or not so great acronym as the case may be. acronyms are usually a bad way to name something.

1. No, full disk encryption is not supported yet, and it's not as simple as one might think.

2. Apt is not supported on the rootfs, which is read-only for a reason. Unfortunately, I think ovpn files are not yet supported, so the certificates need to be manually split out and loaded manually, along with other settings, into the VPN settings UI.

There are already enough things named Unity. The name "Unity" is a bigger problem here than Ubuntu, I'd say.

@advocatux It might work for some, but in my experience, bridges are pretty awful alternatives to having a real client.

@mymike said in "UbuntuTouch" name:

@3arn0wl no please, I hate names that ends with OS , their awful, the name should say it's an operating system imo. Names don't do it for other products/softwares, why should the do it for OSes?

That's just not true. Have you never heard of AutoCAD? PHOTOshop? Painter? macOS?

Names are just that, names, and often it is good to make it more unique by adding what specifically it is as such.

@tigerpro said in "UbuntuTouch" name:

I have actually been thinking about this alot in recent days, I talked a friend d I to trying it, the name however puts him off because he is strictly a Windows and Android person, Im thinking "Ultimate Touch" could be a good name, as UT IMO is miles better than Android and iOS, however most of the people I've talked to have told me they're not interested in trying Linux, until I tell them that Android is for all purposes of the argument a Linux distro, albeit a very poorly designed Linux distro, but a Linux distro just the same. So what are your guys' thoughts?

Rather, Android is a very well designed Linux distro, precisely because the users don't even realize they're using Linux. Maybe you should also educate your friend about all the other devices they have which are most likely also running Linux (TV, thermostat, alarm system, fridge, car, etc…).

@jezek No, that has nothing to do with the Android container part.

@RaphAstronome said in PNG vulnerability:

A way to remove it ?

The image would need to be re-built without the file, and I don't know if that's doable. However, as I said, I'm pretty certain it's not used.

Also, it's not clear that the vulnerability affects the version of Android which currently supported devices is built upon. So far, everything I can find about this specific vulnerability, is saying Android 7.0-9 only. It would help to have accurate information, rather than vague statements.

@advocatux Mooooooooooo

Unless Google releases an update for older Android (4.4, 5.1), it's not likely that file will be updated in UBports. However, I don't think it is used either (though something in the android container may link to it and require its presence).

MMS handling in UT does not use that library.

Lets avoid any more Utopic Unicorns please.

@mic_ Please keep the FUD out. No need to make such statements about competitors when you have no proof of it, and it has no relevance to making UT better.

There isn't a problem with the apparmor confinement. The things which messaging-app needs to access requires it to have the unconfined profile if it's to be a click.

@wartburgritter said in gps info app:

Is it may be possible to compile this for ubuntu touch?

I think not. It would need to be rewritten to use the location-service API rather than whatever Sailfish provides. It's theoretically possible to develop a similar app for UT though.

I think it is not possible via USB cable at the moment, no.

You can use SSH to connect from one to the other, if you have the keys generated and set up properly, and SSH enabled on the phone you wish to connect to.