Skip to main content
replaced http://security.stackexchange.com/ with https://security.stackexchange.com/
Source Link
replaced http://security.stackexchange.com/ with https://security.stackexchange.com/
Source Link
replaced http://security.stackexchange.com/ with https://security.stackexchange.com/
Source Link

The closing of thisthis question perplexes me. I understand that the question it is supposedly a duplicate of--How do I deal with a compromised server?How do I deal with a compromised server? --is basically the canonical question on here about what can be done to remediate any potentially/known-compromised server with a full, general-purpose OS on it. (And perhaps it is for general-purpose PCs as well.) And I don't think I have any real issue with it being that. But is it really the judgment of the community that dealing with a potentially compromised modem or router--especially a SOHO modem/router--is almost exactly the same thing, at a practical level, as dealing with a compromised server?

If so, I'd definitely appreciate some more guidance about what types of computational device compromises don't fall within the scope of that canonical question, at least when we're talking about the purpose of closing a new question as a duplicate of it. Cause (as someone who has done both many home/small biz gigs and some corporate-scale work) I honestly do have some trouble seeing the almost "exact" practical ( vs. theoretical) similarity myself in the case of remediating SOHO routers vs. enterprise servers.

The closing of this question perplexes me. I understand that the question it is supposedly a duplicate of--How do I deal with a compromised server? --is basically the canonical question on here about what can be done to remediate any potentially/known-compromised server with a full, general-purpose OS on it. (And perhaps it is for general-purpose PCs as well.) And I don't think I have any real issue with it being that. But is it really the judgment of the community that dealing with a potentially compromised modem or router--especially a SOHO modem/router--is almost exactly the same thing, at a practical level, as dealing with a compromised server?

If so, I'd definitely appreciate some more guidance about what types of computational device compromises don't fall within the scope of that canonical question, at least when we're talking about the purpose of closing a new question as a duplicate of it. Cause (as someone who has done both many home/small biz gigs and some corporate-scale work) I honestly do have some trouble seeing the almost "exact" practical ( vs. theoretical) similarity myself in the case of remediating SOHO routers vs. enterprise servers.

The closing of this question perplexes me. I understand that the question it is supposedly a duplicate of--How do I deal with a compromised server? --is basically the canonical question on here about what can be done to remediate any potentially/known-compromised server with a full, general-purpose OS on it. (And perhaps it is for general-purpose PCs as well.) And I don't think I have any real issue with it being that. But is it really the judgment of the community that dealing with a potentially compromised modem or router--especially a SOHO modem/router--is almost exactly the same thing, at a practical level, as dealing with a compromised server?

If so, I'd definitely appreciate some more guidance about what types of computational device compromises don't fall within the scope of that canonical question, at least when we're talking about the purpose of closing a new question as a duplicate of it. Cause (as someone who has done both many home/small biz gigs and some corporate-scale work) I honestly do have some trouble seeing the almost "exact" practical ( vs. theoretical) similarity myself in the case of remediating SOHO routers vs. enterprise servers.

Tweeted twitter.com/StackSecurity/status/784505062404030465
fixed simple spelling, style issues
Source Link
Loading
Source Link
Loading