On EC2, /dev/mem appears to depend slightly on the Xen _host_. It will
either correctly return EPERM on RAM reads, or if not, it will return
all zeros. So, this is technically safe, but likely due to the Xen host.
** Package changed: linux (Ubuntu) => linux-ec2 (Ubuntu)
** Changed in: linux-ec2 (Ubuntu)
Importance: Undecided => Low
** Also affects: linux-ec2 (Ubuntu Karmic)
Importance: Undecided
Status: New
** Also affects: linux-ec2 (Ubuntu Lucid)
Importance: Undecided
Status: New
** Summary changed:
- Lucid 2.6.32-29.58 /dev/mem is readable
+ Lucid on EC2 /dev/mem does not return EPERM
** Changed in: linux-ec2 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux-ec2 (Ubuntu)
Importance: Low => Undecided
** Changed in: linux-ec2 (Ubuntu Karmic)
Importance: Undecided => Wishlist
** Changed in: linux-ec2 (Ubuntu Karmic)
Status: New => Confirmed
** Changed in: linux-ec2 (Ubuntu Lucid)
Status: New => Confirmed
** Changed in: linux-ec2 (Ubuntu Lucid)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/725308
Title:
Lucid on EC2 /dev/mem does not return EPERM
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
