Initial patch for Systemd-manager.
Currently there is still security risk, because current cargo version doesn't verify checksums.
Cargo verify checksums starting with version 0.13, so once updated it would be safe to use cargo packages.
| hjajet | |
| Nov 17 2016, 12:46 PM |
| F8221: 0003-Enable-networking.patch | |
| Dec 9 2016, 4:56 PM |
| F7866: 0002-Some-formal-fixes.patch | |
| Nov 23 2016, 4:36 PM |
| F7658: 0001-Initial-commit-of-systemd-manager.patch | |
| Nov 17 2016, 12:46 PM |
Initial patch for Systemd-manager.
Currently there is still security risk, because current cargo version doesn't verify checksums.
Cargo verify checksums starting with version 0.13, so once updated it would be safe to use cargo packages.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Wontfix | JoshStrobl | T24 Systemd-manager | |||
| Invalid | None | T1612 Systemd-manager |
git|https://github.com/mmstick/systemd-manager.git : a83a102ef918d0499a02da6a69ef113b7c82a160 needs to be changed to git|https://github.com/mmstick/systemd-manager.git : 1.0.0
+license : + - GPL-3.0
Can be changed to license : GPL-3.0
Currently there is still security risk, because current cargo version doesn't verify checksums.
So why is it being merged then?
Once T1718: Update Cargo to 0.13.0 is merged there is no security risk.
This patches should not be merged before.
Cargo is 0.13.0 now, so there should not be any security risk.
Only problem may be that dependencies are downloaded during setup.
@ikey Is it OK to package cargo-based projects by this way?