Reputation
1,555
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
9 22
Newest
 Yearling
Impact
~240k people reached

Feb
4
awarded  Yearling
Dec
3
comment sshd_config limit / disable multiplexing
Let us continue this discussion in chat.
Dec
3
comment sshd_config limit / disable multiplexing
Could you paste the sshd_config somewhere such as fpaste if possible please? tried this on AMI openssh-6.6.1p1-12.57.amzn1.x86_64 and still have the same problems ... it's baffling me.
Dec
3
comment sshd_config limit / disable multiplexing
openssh-6.6.1p1-22.el7.x86_64 installed and whilst this is the latest RHEL package this suffer the same issues it would appear
Dec
3
comment sshd_config limit / disable multiplexing
ok I'll keep an eye out for relevant updates; you wouldn't happen to know the RH BZ id at all ?
Dec
2
comment sshd_config limit / disable multiplexing
oddly MaxSessions does not prevent the creation nor use of multiplexing when set to 1 [root@localhost ~]# cat /etc/redhat-release CentOS Linux release 7.1.1503 (Core) [root@localhost ~]# rpm -q openssh openssh-6.6.1p1-12.el7_1.x86_64
Nov
27
comment sshd_config limit / disable multiplexing
@womble hosts may wish to prevent this feature from being used for auditing / enforce 2FA for each connection purposes.
Nov
27
asked sshd_config limit / disable multiplexing
Sep
2
awarded  Caucus
Jul
23
awarded  Notable Question
Jun
18
revised ModSecurity rule to not scan URI
added additional link resource for rule chaining
Jun
18
comment ModSecurity rule to not scan URI
@Arlion, disabling inspection of URI is just as bad as disabling the rule in some cases, the URI can often be matched by signatures for known exploit locations; you can look at rule modification if you really must ignore the URI but that is not something I can help with.
Jun
18
comment ModSecurity rule to not scan URI
Let us continue this discussion in chat.
Jun
18
comment ModSecurity rule to not scan URI
@Arlion hence the comment about using LocationMatch directive to ensure rules are only disabled for known falsepositives.
Jun
18
comment ModSecurity rule to not scan URI
The shortest method is to correlate your false positives and selectively disable the associated rules; it may be possible to negate URI inspection through source / rule modification however I could not give an direction here at this time.
Jun
18
answered ModSecurity rule to not scan URI
Jun
18
comment ModSecurity rule to not scan URI
ModSecurity does not perform packet inspection, it is performing HTTP request inspection at the various stages of the HTTP transaction; I assume you wish to only negate false positives due to the URI?
Jun
18
comment ModSecurity rule to not scan URI
I think the issue is more on the question itself; you want to exclude all URI's from ModSecurity inspection; begs the question of why you want ModSecurity at all in this case as it will become completely redundant if instructed to not inspect any URI at all.
Jun
6
awarded  Nice Answer
Apr
7
awarded  Popular Question