Hi Seth! You know what? It seems, that I finally get a proper Pidgin
profile. Everything seems to works okay: entering password, chat with
people or check history, there is not '[][][][][][][]' signs etc.

,-------
| $ sudo apparmor_status |grep pidgin
| /usr/bin/pidgin
| /usr/bin/pidgin//launchpad_integration
`-------

I am curious if this profile will be working after computer restart. It
seems to me, that it should works okay, because I already put Pidgin in
'enforce' (with "aa-enforce" command) mode and restarted AppArmor (via
"/etc/init.d/apparmor restart"). There is one thing, which I worried
about:

,-------
| /{dev,run}/shm/ r,
| /{dev,run}/shm/* rw,
`-------

"By default, /dev/shm is mounted read/write, with permission to execute
programs. In recent years, many security mailing lists have noted many
exploits where /dev/shm is used in an attack (...)" [1]. Ubuntu seems to
mount '/run/shm' as a "tmpfs" type with 'rw,nosuid,nodev' options. When
I want to mount as '/dev/shm' by adding a proper line to the
'/etc/fstab' (see [1]) during remounting '/dev/shm' I get an error like;
"warning: there is no end of the line at the end of the /etc/fstab file"
etc.

Seth, what do You think about access to '/run/shm'?  Why it could not be
mounted as '/dev/shm', which is resulting with an error (see above)?

Best regards, Seth.
________________
[1] https://help.ubuntu.com/community/StricterDefaults

** Attachment added: "New Pidgin profile for AppArmor."
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1066369/+attachment/3422861/+files/usr.bin.pidgin

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066369

Title:
  AppArmor parser error, Warning from stdin (line 1), syntax error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1066369/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to