What's new

pixelserv pixelserv - A Better One-pixel Webserver for Adblock

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

When I have used this in the past it restarts the webui and then you can log in and test to see the lock icon. The webui never restarts and even though it looks configured the sample https://192.168.14.1:port number shows not https://router.asus.com:port number in the webui at the bottom of the system page.

Just to make sure: did you configure the settings below correctly?

5z32Xdp.png


You could try manually restarting the webui by executing:

Code:
service restart_httpd

and see if that makes a difference?
 
No luck with TLS 1.3 yet... (using the version of pixelserv-tls with the statically linked newer OpenSSL library)

I installed the iOS profile to enable TLS 1.3. When I visit https://www.ssllabs.com/ssltest/viewMyClient.html it does indeed list (experimental) 1.3 protocol support, but when I visit pages on the internet I still see 0 for v13 on the pixelserv-tls server stats page (only v12 is greater than zero).

Additionally I have installed Firefox 63 Beta 14 on my MacBook Pro and checked that security.tls.version.max is 4, as is written here: https://www.ghacks.net/2017/06/15/how-to-enable-tls-1-3-support-in-firefox-and-chrome/ However, when I visit the above SSL Labs page again it now only lists 1.2 support (no 1.3!) and again the v13 counter remains at 0.

What am I doing wrong?
 
Update: should have read the post by Xentrk, as this command did the trick:
Code:
sudo defaults write /Library/Preferences/com.apple.networkd tcp_connect_enable_tls13 1
SSL Labs test page still lists 1.2 only, but page visits in both Safari and Firefox (on macOS) now increase the v13 counter.
 
Just to make sure: did you configure the settings below correctly?

5z32Xdp.png


You could try manually restarting the webui by executing:

Code:
service restart_httpd

and see if that makes a difference?
You just gave me a huge idea....I enabled:
Code:
Redirect webui access to router.asus.com = yes
All is well!!:):):) Thanks for the great tip!
 
SSL Labs test page still lists 1.2 only, but page visits in both Safari and Firefox (on macOS) now increase the v13 counter.

I believe the SSL Lab page only tests DRAFT versions of TLS 1.3. Also TLS 1.3 support in Firefox & Chrome has nothing to do with the Apple system-wide default flag..

So now with a few people have tried it on Mac. Seems like Apple indeed has TLS 1.3 final version built in Mojave (& iOS 12..) but not enabled.

EDIT:

If people want to test your browsers supporting TLS 1.3 final version or not, the easiest is to make use of pixelserv-tls.

Visit https://<pixelserv ip>/serverstats. When the page loads, v13 counters should increment. That indicates your browser support the official TLS 1.3 version aka the final version.
 
Last edited:
This should not get buried and lost..

A script to enable on the fly and present pixelserv-tls log (for whitelisting domain, privacy breach inspection, and etc):
I should emphasise that pixelserv-tls itself is not a script. It's a first-class citizen as a service aka daemon in Linux/Unix world. That is always running in background and serving you for a good purpose.

Hence, people should not wrongly call it a script. Though in the special context of this forum, people in general will understand when you say a script..meant to say an "add-on" feature to your router's FW.

Volunteers looking for opportunity to develop for pixelserv-tls may start with the above script. The goal:
  • light-weight & user friendly
  • make use of available tools if necessary
  • do not re-invent the wheel
A project like this will bring peer to peer support within pixelserv-tls to the next level. I'm not looking for the script. Hence multiple scripts trying to achieve the same functionality are welcome and encouraged.

EDIT:

Added a project section to the first post of this thread and links back to this project/post.
 
However for my download of that profile the removal date (as given by the "security" command) is somewhere in 2019; not 2018-01-01...

So I might experiment with this after all!
Where you find that profile?
I want it to be enable for my iOS. 12.1
 
Same link as before (see a few posts back).

Only for members of the Apple Developer Program.
Thx. Got it for my iOS 12.1 beta3

upload_2018-10-16_22-34-33.jpeg


upload_2018-10-16_22-35-49.jpeg
 
Unfortunately no release date for TLS 1.3 though.

It's already available in iOS 12.1 developer BETA 4 so the code is integrated and functional ( with probably few things left to sort out ) and all they need to do now is enable it by default so probably they'll do it with iOS 12.1 release. [emoji1695]

Something in macOS Mojave.
 
My macOS tests might have been wrong...

Reloading the serverstats page by itself increases the v13 counter by 2...
 
My macOS tests might have been wrong...

Reloading the serverstats page by itself increases the v13 counter by 2...
Probably like iOS, the tls 1.3 final only contains in iOS beta and so is macOS. Maybe u can consider macOS beta?
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top