Project

General

Profile

Actions
Copy link

Feature #15323

open
PW

Display server description when WOL is sent using mac url or power-on button

Feature #15323: Display server description when WOL is sent using mac url or power-on button

Added by Phil Wardt over 2 years ago. Updated 10 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Wake on LAN
Target version:
CE-Next
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Plus-Next
Release Notes:
Default

Description

When we use the send WOL to all devices link, the description of servers is properly printed
However, when we send WOL to a single server clicking on mac url or power-on button, the description is not printed

Fix this and properly display the description when sending WOL to a single server using both links

Files

services_wol-pf2.7.2-v1.0.php.patch (1.62 KB) services_wol-pf2.7.2-v1.0.php.patch Phil Wardt, 03/08/2024 09:33 PM

PW Updated by Phil Wardt over 2 years ago Actions
Copy link
 #1

Github commit:
https://github.com/pfsense/pfsense/pull/4673

And a patch file for current pfsense 2.7.2

JG Updated by Jordan G over 2 years ago Actions
Copy link
 #2

the described behavior is also present in the current version of pfSense+ as well (24.03)

JP Updated by Jim Pingle over 2 years ago Actions
Copy link
 #3

  • Status changed from New to Pull Request Review
  • Target version set to 2.8.0
  • Plus Target Version set to 24.08

JP Updated by Jim Pingle almost 2 years ago Actions
Copy link
 #4

  • Plus Target Version changed from 24.08 to 24.11

JP Updated by Jim Pingle almost 2 years ago Actions
Copy link
 #5

  • Plus Target Version changed from 24.11 to 25.01

JP Updated by Jim Pingle almost 2 years ago Actions
Copy link
 #6

  • Plus Target Version changed from 25.01 to 25.03

PW Updated by Phil Wardt almost 2 years ago Actions
Copy link
 #7

I just noticed that the widget needs also a patch to display server description when wol is sent using the widget.
Should it be done on distinct commit than this ?

JP Updated by Jim Pingle almost 2 years ago Actions
Copy link
 #8

Both could be on the same PR since they're for the same issue, but the PR needs work anyhow -- I left a comment on there.

It's helpful to use Git to squash the commits so they only appear as one commit in the PR, but not a hard requirement in most cases.

PW Updated by Phil Wardt almost 2 years ago Actions
Copy link
 #9

Jim Pingle wrote in #note-8:

Both could be on the same PR since they're for the same issue, but the PR needs work anyhow -- I left a comment on there.

It's helpful to use Git to squash the commits so they only appear as one commit in the PR, but not a hard requirement in most cases.

Is it ok if I use hmtlspecialchars() instead, as I should've done from start in fact ? It'll make it safe in that case
Or you prefer the check from config entries ?

JP Updated by Jim Pingle almost 2 years ago Actions
Copy link
 #10

While that method offers protection, it's still putting too much trust in user-supplied data to get passed around. Looking up the entry is better since it eliminates the concern entirely.

JP Updated by Jim Pingle over 1 year ago Actions
Copy link
 #11

  • Plus Target Version changed from 25.03 to 25.07

JP Updated by Jim Pingle over 1 year ago Actions
Copy link
 #12

  • Target version changed from 2.8.0 to 2.9.0

JP Updated by Jim Pingle about 1 year ago Actions
Copy link
 #13

  • Plus Target Version changed from 25.07 to 25.11

JP Updated by Jim Pingle 10 months ago Actions
Copy link
 #14

  • Status changed from Pull Request Review to New
  • Target version changed from 2.9.0 to CE-Next
  • Plus Target Version changed from 25.11 to Plus-Next
Actions
Copy link

Also available in: Atom