Reputation
601
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
6 13 29
Newest
 Yearling
Impact
~464k people reached

Apr
27
awarded  Yearling
Apr
25
awarded  Popular Question
Feb
16
awarded  Notable Question
Jan
5
awarded  Nice Question
Dec
17
awarded  Necromancer
Dec
15
comment Cipher suits supported by TLS1.1. and 1.2
RTFRFC: ietf.org/rfc/rfc5246.txt Also might just be an RTFM issue. Not sure about your application, but it's possible that the cipher suite selections could be defined on a per-protocol level. So, if you cut off TLS 1.0 without defining any allowed ciphers for 1.2, you'd end up with what you have.
Dec
15
comment Cipher suites supported by TLS1.1. and 1.2
You also might want to check the appropriate RFC.
Nov
5
revised In Windows, using the command line, how do you check if a remote port is open?
added 111 characters in body
Nov
5
comment In Windows, using the command line, how do you check if a remote port is open?
@samsmith Are you talking about the command in my answer, or the one ST8Z...'s comment? The one in my answer only works for Win8/2k12 and higher, and the answer says as much.
Oct
21
comment Separate TLS control for MSSQL & IIS
@JimB We thought of that too. Probably going to be brought up in our next discussion on the topic. But I was kind-of hoping there was an "easier" fix along these lines.
Oct
21
comment Separate TLS control for MSSQL & IIS
If there's really no way to separately control TLS for the two services, segmenting is one option - and would address other "best practice issues" - but I think the real "bite the bullet" that we should probably be looking at is upgrading the MSSQL software to something TLS 1.1/1.2-compatible. That's also under discussion, but I'm hoping to figure something else out for the interim too.
Oct
21
asked Separate TLS control for MSSQL & IIS
Sep
8
awarded  Constituent
Sep
2
comment Active directory authentication and authorization for an application
This is security related, but more about the implementation details than it is about the vulnerability/risk aspects. I'm voting for Server Fault.
Sep
1
awarded  Caucus
Aug
26
revised Identify if a server is currently accessed via Remote Desktop Connection
added 1448 characters in body
Aug
26
answered Identify if a server is currently accessed via Remote Desktop Connection
Aug
26
comment Identify if a server is currently accessed via Remote Desktop Connection
Would be interesting to know your reasons against PsLoggedOn. It's been my preferred method for awhile, though I've never tried the QUERY tool myself.
Aug
26
comment Identify if a server is currently accessed via Remote Desktop Connection
Also, qwinsta can be run against a remote computer as well without having to use PsExec.
Aug
26
comment Identify if a server is currently accessed via Remote Desktop Connection
As long as you're bringing up PsTools already, why not PsLoggedOn? It's designed for exactly this sort of situation.