This now a filed bug
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811037
Sent from my Motorola XT1505
Other people seem to be seeing this too with Android > 5.0 and recent
Linux. Debian Jessie and Ubuntu Trusty seem affected. But I have my
old SD card set up around 2/7/2015 and it works fine. That would have
been Wheezy I think, I had to modify Debian Kit to not install
Squeeze. I have at
I installed dpkg_1.18.4_armhf.deb by remounting selinux, It seems to
help a tiny bit. By the changelog there have been recent selinux
changes to it. I still almost always get the error about the security
handle though.
Is it possible that it can't get a security handle because the file
doesn't
On Fri, Jan 15, 2016 at 10:24 AM, Alan Corey wrote:
> I installed dpkg_1.18.4_armhf.deb by remounting selinux, It seems to
> help a tiny bit. By the changelog there have been recent selinux
> changes to it. I still almost always get the error about the security
> handle though.
I don't think
I extracted the Jessie and Wheezy(?) binary debs to grep them. The
string "security labeling" is in the Jessie dpkg binary, it's not in
the Wheezy(?) one.
dpkg 1.17.25 has it, 1.16.16 doesn't. That's why the old version
doesn't give that error. Now to find the source and look there.
Wondering
On Thu, Jan 14, 2016 at 12:37 PM, Alan Corey wrote:
> Maybe I should scrap this and reinstall.
Not sure. Either way, once you figured out the issue, please add a
section to the chroot on Android page.
https://wiki.debian.org/ChrootOnAndroid
--
bye,
pabs
https://wiki.debian.org/PaulWise
OK, I had something strange with my mounts but I found the suggestion
somewhere to do:
cat /proc/mounts > /etc/mtab
and that worked (mtab was empty, fstab too).
Now mount shows:
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
so I did mount -o remount,ro /sys/fs/selinux
And I was able
What I have in my SD card slot right now is a Wheezy I set up about
February on another phone under Android 4.4. No selinux issues at
all. Unfortunately it's only a 64 gig card, it's armel instead of
armhf, and of course it's old. But the cards function
interchangeably, it's like a multiboot
On Sat, Jan 02, 2016 at 06:46:14PM -0500, Alan Corey wrote:
> I basically stumbled across this. I just did apt-get update and I'm
> running dpkg 1.17.25. There's a page at
> https://fossies.org/diffs/dpkg/1.18.0_vs_1.18.1/src/selinux.c-diff.html
> talking about an selinux change in dpkg 1.18.1.
I basically stumbled across this. I just did apt-get update and I'm
running dpkg 1.17.25. There's a page at
https://fossies.org/diffs/dpkg/1.18.0_vs_1.18.1/src/selinux.c-diff.html
talking about an selinux change in dpkg 1.18.1. I should do an
apt-get upgrade if my current apt-get -f install
On Thu, Dec 31, 2015 at 5:10 AM, Alan Corey wrote:
> With my Debian Kit installation on a phone (Motorola Mote-e2, Android
> 5.02) I seem to be having selinux problems.
I expect it is due to the Android version or build of the Linux kernel
that you are using. Try to get the Linux build config
With my Debian Kit installation on a phone (Motorola Mote-e2, Android
5.02) I seem to be having selinux problems. I've read part of
Gentoo's selinux tutorial at
https://wiki.gentoo.org/wiki/SELinux/Tutorials and I'm trying to
figure this out.
Did:
setenforce permissive
root@gsm:/# getenforce
Maybe I figured out something. I don't have an selinux policy under
Debian, no files for creating one. But the kernel was built for
Android which expects one. That could be the missing file. In
OpenBSD there are tools for finding out things about the kernel, I
don't know how to do that in
13 matches
Mail list logo
