Netgate shared root with ISP? ¯\_(❞⦈)_/¯

TheHowTo

@stephenw10 Would you please tell Dev to fix these loophole (superuser's backdoor) and bug (openvpn over tcp) on the next PfSense version.
Thank you.

johnpoz

OMG dude - there is not a "superuser" backdoor.. And what bug in openvpn over tcp... It work it just fine. Where is the redmine link to this "bug"??

stephenw10

If you think you have found a bug (you almost certainly haven't) then you should open a redmine ticket with the details and how to replicate.

You are going to have to present some evidence though. There is no reason you can't post screenshots of your config history or system log text with your public IPs removed. That gives away nothing that you should care about.
Otherwise it just looks like you're trolling. We will have to lock the thread.

Steve

AKEGEC

Hi all, I had similar problem with (2.4.5-p1) openvpn running over TCP specifically the client site. You need to edit your openvpn.inc file to fix this.

@johnpoz said in Netgate shared root with ISP? ¯\_(❞⦈)_/¯:

OMG dude - there is not a "superuser" backdoor.. And what bug in openvpn over tcp... It work it just fine. Where is the redmine link to this "bug"??

johnpoz

@C3G3K4 said in Netgate shared root with ISP? ¯\_(❞⦈)_/¯:

You need to edit your openvpn.inc file to fix this.

And where is the link to this bug report? Or even the thread discussing this issue, or what exactly did you change.

And lets be specific.. Stating there is a "bug" in openvpn tcp, as a client to to some vpn service? With site 2 site? I run tcp client to pfsense from my phone, from my pc at work over tcp and have not seen any "bugs" or issues at all.

Saying there is a "bug" doesn't help anyone nor is going to get anything fixed if there is an actual issue.

kiokoman

i don't intend to feed the troll, reported him for 3 post without any meaning, registered 27 minutes ago,I start collecting bets, 5$ .. he's a spammer

AKEGEC

Hi all, I am just trying to help and contribute, but why do I get aggressive and hostile treatments?
If you do not know how to edit an openvpn.inc file, then I suggest you have to wait for the next pfsense version. Don’t falsely accused someone, specially without established proof.

Anyway, my family and I believe, good acts will have good consequences, bad acts will have bad ones. You'd think by now people would understand…
that you reap what you sow.

Happy Sunday Everyone.

stephenw10

What did you have to change in the client side config file?

How did the issue present before you made that change?

I'm not aware of any OpenVPN TCP issue in 2.4.5p1, if you have found something you should open a redmine bug report: https://redmine.pfsense.org/

Steve

johnpoz

Great you want to help, then actually provide that vs just saying "you" fixed something...

Saying there is bug, and "you" fixed by editing openvpn.inc doesn't help or contribute anything.. Posting what was fixed, and how you fixed it would be information people could actually use.

jimp

The OpenVPN TCP issue has already been fixed in the repo. You can install the System Patches package and then create an entry for e1c689eeb3a4439f3a66e8686b1fc32db536ac78 to apply the fix.

There is no "superuser backdoor". You still have not shown any evidence that anything was changed by someone other than yourself, a package you installed, or as a consequence of a configuration change you made.

jimp

Locking this. If no solid evidence has turned up by now after they have been asked repeatedly for details, they are trolling or otherwise being deliberately disingenuous with their posts.