Moved to main. (component-mismatches-proposed wanted the systemtap-doc
binary package as well, which is clearly harmless so I included it.)
** Changed in: systemtap (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bug
OK, the systemtap-sdt-dev package can be promoted, but only that one.
If it's just that package, we can skip the security review and the test
requirement. But if we ever revisit promoting more, we should do both.
** Changed in: systemtap (Ubuntu)
Status: New => Fix Committed
--
You recei
Team subscribed to bugs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1203590
Title:
[MIR] systemtap
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemta
Debian bug about enabling tests:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526957
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1203590
Title:
[MIR] systemtap
To manage notifications about t
Note, /usr/bin/dtrace is shipped in systemtap-sdt-dev. It is a python
program and would not run privileged, so it doesn't need the review
either.
** Changed in: systemtap (Ubuntu)
Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)
** Changed in: systemtap (Ubuntu)
Status
If that's the case, then we don't need a security review. systemtap the
*source* and the systemtap-sdt-dev binary can go to main, but everything
else should stay in universe.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Seth, the lttng-ust development bits don't require systemtap as a whole, but
the sys/sdt.h header file.
(Systemtap is not for only kernel instrumentation these days, by the way; with
dyninst can be used pure-userspace.)
--
You received this bug notification because you are a member of Ubuntu
Bu
I'd also like to understand the motivation behind this but meanwhile you
should note that most of the security vulnerabilities can only be
exploited by users that have been added to the privileged stapusr group.
Just installing the package does not make you vulnerable.
--
You received this bug no
Sorry, CVE-2008-1514 was in the kernel, not systemtap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1203590
Title:
[MIR] systemtap
To manage notifications about this bug go to:
https://bugs.launch
I would quite prefer systemtap not be promoted to main because it actually does
have a security history:
CVE-2008-1514
CVE-2009-0784
CVE-2009-2911
CVE-2009-4273
CVE-2010-0411
CVE-2010-0412
CVE-2010-4170
CVE-2010-4171
CVE-2011-1769
CVE-2011-1781
CVE-2011-2502
CVE-2011-2503
CVE-2012-0875
Can someon
Is that for use with lttng user space tracepoints? Do they need
CONFIG_UPROBES? (See http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=691167 )
** Bug watch added: Debian Bug tracker #691167
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691167
--
You received this bug notification because
Why does Mir need to dynamically insert tracing code into the kernel?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1203590
Title:
[MIR] systemtap
To manage notifications about this bug go
Another blocker is the lack of a team subscriber in Ubuntu. Some team
should be helping to maintain this in Ubuntu and be subscribed to bugs.
Arguably closing bug 1144040 in the process.
This will also need a quick security audit.
I like that we're in sync right now, and it seems well maintaine
I'm still looking at this, but the tests should be run. They aren't run
during build because they are designed to be run against an installed
systemtap, but that's where dep8 comes in. Especially now that dep8
results are used for proposed migration.
See http://bugs.debian.org/cgi-bin/bugreport.
14 matches
Mail list logo
