[Summary]
MIR Team conditional ack. To be complete I'd recommend an update to v3.4 and I'd
request a security review. The updates are important, but no blocker for the
security review therefore I'm assigning the security Team.
TODOs:
@Jamespage - bug subscriber
I guess openstack will subscribe for this one right?
Jamespage could you make that happen?
@Jamespage - update to version 3.4 for a bunch of crash fixes
@security - please put this on your review queue.
[Duplication]
This is essentially a ceph/LIO gateway translating between the two.
Such functionality isn't in main, duplication is no issue.
[Dependencies]
- no other Dependencies to MIR due to this (only those listed in this bug
already)
- no -dev/-debug/-doc packages that need exclusion
[Embedded sources and static linking]
- no embedded source present
- no static linking
[Security]
OK:
- history of CVEs does not look concerning
- does not use webkit1,2
- does not process arbitrary web content
- does not use lib*v8 directly
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)
Problems:
- does run two daemons as root
- does parse data formats (via REST API)
- does open a port (for REST)
=> a security review is needed
[Common blockers]
OK:
- does not FTBFS currently
- does have a test suite that runs at build time
- test suite fails will fail the build upon error (Thanks James for enabling
these).
- no translation present, but none needed for this case (admin only)?
- no new python2 dependency
- uses dh_python
Problems:
- Does not yet have a team bug subscriber?
- does not have a test suite that runs as autopkgtest (sort of ok for now, if
tested e.g. in other openstack context)
[Packaging red flags]
OK:
- Ubuntu does carry a delta, but it is reasonable and maintenance under control
- symbols tracking not applicable for this kind of code.
- d/watch is present and looks ok
- Upstream update history is ok
- Debian/Ubuntu update history is not long enough to have a good insight how frequent they will be
- promoting this does not seem to cause issues for MOTUs that so far maintained the package
- no massive Lintian warnings
- d/rules is rather clean
- not using Built-Using
[Upstream red flags]
OK:
- no Errors/warnings during the build
- no incautious use of malloc/sprintf (python)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH
- no use of user nobody
- no use of setuid (needs very careful design (prefer systemd to set those for services))
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- no embedded source copies
- not part of the UI for extra checks
Problems:
- The upstream bug tracker has a list of bad bugs, but they seem to be actively
worked on so that should be ok.
## ceph-iscsi ##
[Summary]
MIR Team conditional ack. To be complete I'd recommend an update to v3.4 and I'd
request a security review. The updates are important, but no blocker for the
security review therefore I'm assigning the security Team.
TODOs:
@Jamespage - bug subscriber
I guess openstack will subscribe for this one right?
Jamespage could you make that happen?
@Jamespage - update to version 3.4 for a bunch of crash fixes
@security - please put this on your review queue.
[Duplication]
This is essentially a ceph/LIO gateway translating between the two.
Such functionality isn't in main, duplication is no issue.
[Dependencies]
- no other Dependencies to MIR due to this (only those listed in this bug
already)
- no -dev/-debug/-doc packages that need exclusion
[Embedded sources and static linking]
- no embedded source present
- no static linking
[Security]
OK:
- history of CVEs does not look concerning
- does not use webkit1,2
- does not process arbitrary web content
- does not use lib*v8 directly
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)
Problems:
- does run two daemons as root
- does parse data formats (via REST API)
- does open a port (for REST)
=> a security review is needed
[Common blockers]
OK:
- does not FTBFS currently
- does have a test suite that runs at build time
- test suite fails will fail the build upon error (Thanks James for enabling
these).
- no translation present, but none needed for this case (admin only)?
- no new python2 dependency
- uses dh_python
Problems:
- Does not yet have a team bug subscriber?
- does not have a test suite that runs as autopkgtest (sort of ok for now, if
tested e.g. in other openstack context)
[Packaging red flags]
OK:
- Ubuntu does carry a delta, but it is reasonable and maintenance under control
- symbols tracking not applicable for this kind of code.
- d/watch is present and looks ok
- Upstream update history is ok
- Debian/Ubuntu update history is not long enough to have a good insight how frequent they will be
- promoting this does not seem to cause issues for MOTUs that so far maintained the package
- no massive Lintian warnings
- d/rules is rather clean
- not using Built-Using
Problems: /github. com/ceph/ ceph-iscsi/ releases/ tag/3.4 /github. com/ceph/ ceph-iscsi/ compare/ 3.3...3. 4
- the current release is not packaged
=> https:/
Fixing some crashes
=> https:/
@Jamespage would you mind getting this packaged?
[Upstream red flags]
OK:
- no Errors/warnings during the build
- no incautious use of malloc/sprintf (python)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH
- no use of user nobody
- no use of setuid (needs very careful design (prefer systemd to set those for services))
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- no embedded source copies
- not part of the UI for extra checks
Problems:
- The upstream bug tracker has a list of bad bugs, but they seem to be actively
worked on so that should be ok.