Skip to content

NeoPool always output valid sensitive data#24573

Merged
arendst merged 1 commit intoarendst:developmentfrom
curzon01:neopool
Mar 23, 2026
Merged

NeoPool always output valid sensitive data#24573
arendst merged 1 commit intoarendst:developmentfrom
curzon01:neopool

Conversation

@curzon01
Copy link
Copy Markdown
Contributor

Description:

NeoPool always returns valid data, even if SO157 is set to 0 (default). In this case, a hash value is returned instead of the original NodeID.

Checklist:

  • The pull request is done against the latest development branch
  • Only relevant files were touched
  • Only one feature/fix was added per PR and the code change compiles without warnings
  • The code change is tested and works with Tasmota core ESP8266 V.2.7.8
  • The code change is tested and works with Tasmota core ESP32 V.3.1.10 / V.3.3.7
  • I accept the CLA.

@arendst arendst merged commit beed56f into arendst:development Mar 23, 2026
64 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants