Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2224518 ** Information from BlockerBugs App:
The votes have been last counted at 2023-08-28 15:55 UTC and the last processed comment was #comment-871218
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)
BetaBlocker +1
BetaBlocker
FinalBlocker
BetaFE
FinalFE
0Day
PreviousRelease
+1
0
-1
If this bug still applies, so I vote:
The reverse connection works when the Firewall is switched off on the target machine. This however creates a security hole, I suppose.
I'm not really convinced about this one. I think it's been this way for a long time, and we haven't blocked on it before. The thing basically works, we just don't know what the required firewall settings are on the client. I don't think that's worth blocking on (and I don't even know what we could change in the compose to "fix" this - the issue is almost certainly not in the installer image).
BetaBlocker -1
This feels more like a documentation issue regarding required ports than a functionality issue.
As visible in the Bugzilla, this was a firewall configuration problem, not a vnc problem.
AGREED RejectedBetaBlocker
The following votes have been closed:
Yeah, as commented by Adam here, I agree with rejecting this as a blocker.
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F39 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.