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

The question How do we instruct our employees to protect themselves from Heartbleed?How do we instruct our employees to protect themselves from Heartbleed? was closed as a duplicate of Heartbleed: What is it and what are options to mitigate it?Heartbleed: What is it and what are options to mitigate it?. Was that closure in error?

The closed question is all about how to instruct our clients (users) to protect themselves against Heartbleed. The canonical question appears to be all about how to protect our servers against heartbleed.

There is some room for ambiguity: The title and text of the canonical question is quite broad, mentioning neither server nor user. The answers to the canonical question, however, are all about the server. The question has clearly been understood to be about the server, not the user.

  • Should the closure stand because the question is truly a duplicate?
  • Should the closure stand because the question is not really about system administration, but is a user question in a thin disguise?
  • Should the closure be undone? If so, should the canonical question be edited to make it clear that it is about the server?
  • Should the closed question be merged with the canonical question?

The question How do we instruct our employees to protect themselves from Heartbleed? was closed as a duplicate of Heartbleed: What is it and what are options to mitigate it?. Was that closure in error?

The closed question is all about how to instruct our clients (users) to protect themselves against Heartbleed. The canonical question appears to be all about how to protect our servers against heartbleed.

There is some room for ambiguity: The title and text of the canonical question is quite broad, mentioning neither server nor user. The answers to the canonical question, however, are all about the server. The question has clearly been understood to be about the server, not the user.

  • Should the closure stand because the question is truly a duplicate?
  • Should the closure stand because the question is not really about system administration, but is a user question in a thin disguise?
  • Should the closure be undone? If so, should the canonical question be edited to make it clear that it is about the server?
  • Should the closed question be merged with the canonical question?

The question How do we instruct our employees to protect themselves from Heartbleed? was closed as a duplicate of Heartbleed: What is it and what are options to mitigate it?. Was that closure in error?

The closed question is all about how to instruct our clients (users) to protect themselves against Heartbleed. The canonical question appears to be all about how to protect our servers against heartbleed.

There is some room for ambiguity: The title and text of the canonical question is quite broad, mentioning neither server nor user. The answers to the canonical question, however, are all about the server. The question has clearly been understood to be about the server, not the user.

  • Should the closure stand because the question is truly a duplicate?
  • Should the closure stand because the question is not really about system administration, but is a user question in a thin disguise?
  • Should the closure be undone? If so, should the canonical question be edited to make it clear that it is about the server?
  • Should the closed question be merged with the canonical question?
Fixed link
Source Link

The question How do we instruct our employees to protect themselves from Heartbleed? was closed as a duplicate of How do we instruct our employees to protect themselves from Heartbleed?Heartbleed: What is it and what are options to mitigate it?. Was that closure in error?

The closed question is all about how to instruct our clients (users) to protect themselves against Heartbleed. The canonical question appears to be all about how to protect our servers against heartbleed.

There is some room for ambiguity: The title and text of the canonical question is quite broad, mentioning neither server nor user. The answers to the canonical question, however, are all about the server. The question has clearly been understood to be about the server, not the user.

  • Should the closure stand because the question is truly a duplicate?
  • Should the closure stand because the question is not really about system administration, but is a user question in a thin disguise?
  • Should the closure be undone? If so, should the canonical question be edited to make it clear that it is about the server?
  • Should the closed question be merged with the canonical question?

The question How do we instruct our employees to protect themselves from Heartbleed? was closed as a duplicate of How do we instruct our employees to protect themselves from Heartbleed?. Was that closure in error?

The closed question is all about how to instruct our clients (users) to protect themselves against Heartbleed. The canonical question appears to be all about how to protect our servers against heartbleed.

There is some room for ambiguity: The title and text of the canonical question is quite broad, mentioning neither server nor user. The answers to the canonical question, however, are all about the server. The question has clearly been understood to be about the server, not the user.

  • Should the closure stand because the question is truly a duplicate?
  • Should the closure stand because the question is not really about system administration, but is a user question in a thin disguise?
  • Should the closure be undone? If so, should the canonical question be edited to make it clear that it is about the server?
  • Should the closed question be merged with the canonical question?

The question How do we instruct our employees to protect themselves from Heartbleed? was closed as a duplicate of Heartbleed: What is it and what are options to mitigate it?. Was that closure in error?

The closed question is all about how to instruct our clients (users) to protect themselves against Heartbleed. The canonical question appears to be all about how to protect our servers against heartbleed.

There is some room for ambiguity: The title and text of the canonical question is quite broad, mentioning neither server nor user. The answers to the canonical question, however, are all about the server. The question has clearly been understood to be about the server, not the user.

  • Should the closure stand because the question is truly a duplicate?
  • Should the closure stand because the question is not really about system administration, but is a user question in a thin disguise?
  • Should the closure be undone? If so, should the canonical question be edited to make it clear that it is about the server?
  • Should the closed question be merged with the canonical question?
Source Link

Closed as duplicate in error?

The question How do we instruct our employees to protect themselves from Heartbleed? was closed as a duplicate of How do we instruct our employees to protect themselves from Heartbleed?. Was that closure in error?

The closed question is all about how to instruct our clients (users) to protect themselves against Heartbleed. The canonical question appears to be all about how to protect our servers against heartbleed.

There is some room for ambiguity: The title and text of the canonical question is quite broad, mentioning neither server nor user. The answers to the canonical question, however, are all about the server. The question has clearly been understood to be about the server, not the user.

  • Should the closure stand because the question is truly a duplicate?
  • Should the closure stand because the question is not really about system administration, but is a user question in a thin disguise?
  • Should the closure be undone? If so, should the canonical question be edited to make it clear that it is about the server?
  • Should the closed question be merged with the canonical question?