Bug 1578584 - unshield: newer versions available
Summary: unshield: newer versions available
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: unshield
Version: 30
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-15 22:48 UTC by Armijn Hemel
Modified: 2020-05-26 14:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-26 14:48:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Armijn Hemel 2018-05-15 22:48:36 UTC
Description of problem:

Curretly unshield on rawhide is still on 1.0-9 and hasnot been updated since 2014. Since then there have been a few more upstream releases (latest is 1.4.2), some which apparently contain security related fixes.

Version-Release number of selected component (if applicable):

1.0-9

How reproducible:

Always


Steps to Reproduce:
1. not applicable
2.
3.

Actual results:

Old unshield on current Fedora.

Expected results:

Newer unshield on current Fedora.

Additional info:

Comment 1 Jan Kurik 2018-08-14 10:02:21 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.

Comment 2 Armijn Hemel 2018-11-13 12:19:33 UTC
It was not fixed in Fedora 29, so changing back to rawhide. Latest version of unshield is 1.4.3 (released two weeks ago).

Comment 3 Armijn Hemel 2018-12-22 12:10:36 UTC
The latest versions fix CVE-2015-1386 (and various other bugs). Also see https://bugzilla.redhat.com/show_bug.cgi?id=1185717

Comment 4 Tomas Hoger 2019-01-02 09:44:31 UTC
No good reason to restrict this bug as the flaw has been public for a long time.

Comment 5 Armijn Hemel 2019-01-06 17:21:56 UTC
There was a very good reason for me to do this: the bug is not being addressed. The maintainer does not seem to be responsive.

Comment 6 Ben Cotton 2019-02-19 17:12:15 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 30 development cycle.
Changing version to '30.

Comment 7 Armijn Hemel 2019-04-11 21:09:51 UTC
So what should be done to get this fixed?

Comment 8 Ben Cotton 2020-04-30 22:13:16 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Ben Cotton 2020-05-26 14:48:29 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.