Skip to content

Conversation

@krishna-pandey
Copy link
Contributor

What is this PR for?

Security conscious organisations does not want to reveal the Application Server name and version to prevent Script-kiddies from finding the information easily when fingerprinting the Application. The exact version number can tell an Attacker if the current Application Server is patched for or vulnerable to certain publicly known CVE associated to it.

What type of PR is it?

[Improvement | Feature]

What is the Jira issue?

How should this be tested?

Providing a value in zeppelin-site.xml will replace the actual Jetty server version found in HTTP Header with provided value. E.g.

  • edit zeppelin-site.xml and add a property zeppelin.server.jetty.name and with value say TOMCAT
  • restart the server
  • open the app in browser then observe the Response Headers for the key "Server" this should now reflect "TOMCAT"

Screenshots (if appropriate)

Questions:

  • Does the licenses files need update? N/A
  • Is there breaking changes for older versions? N/A
  • Does this needs documentation? N/A

@prabhjyotsingh
Copy link
Contributor

@krishna-pandey
Copy link
Contributor Author

krishna-pandey commented May 2, 2017

@prabhjyotsingh Jenkins job is successful.
@Leemoonsoo, @felixcheung, @jongyoul, @bzz Can you help review this?

@jongyoul
Copy link
Member

jongyoul commented May 2, 2017

LGTM

1 similar comment
@Leemoonsoo
Copy link
Member

LGTM

@prabhjyotsingh
Copy link
Contributor

LGTM!

@prabhjyotsingh
Copy link
Contributor

Will merge this to master if no more discussion.

@asfgit asfgit closed this in 62aec9f May 3, 2017
prabhjyotsingh added a commit to prabhjyotsingh/zeppelin that referenced this pull request Aug 15, 2017
…arameter

### What is this PR for?
Security conscious organisations does not want to reveal the Application Server name and version to prevent Script-kiddies from finding the information easily when fingerprinting the Application. The exact version number can tell an Attacker if the current Application Server is patched for or vulnerable to certain publicly known CVE associated to it.

### What type of PR is it?
[Improvement | Feature]

### What is the Jira issue?
* [ZEPPELIN-2461](https://issues.apache.org/jira/browse/ZEPPELIN-2461)

### How should this be tested?
Providing a value in zeppelin-site.xml will replace the actual Jetty server version found in HTTP Header with provided value. E.g.
 - edit zeppelin-site.xml and add a property `zeppelin.server.jetty.name` and with value say `TOMCAT`
 - restart the server
 - open the app in browser then observe the Response Headers for the key "Server"  this should now reflect "TOMCAT"

### Screenshots (if appropriate)

### Questions:
* Does the licenses files need update? N/A
* Is there breaking changes for older versions? N/A
* Does this needs documentation? N/A

Author: krishna-pandey <[email protected]>

Closes apache#2293 from krishna-pandey/ZEPPELIN-2461 and squashes the following commits:

b071f7a [krishna-pandey] Set App Server name to config value
prabhjyotsingh pushed a commit to prabhjyotsingh/zeppelin that referenced this pull request Aug 15, 2017
…arameter

### What is this PR for?
Security conscious organisations does not want to reveal the Application Server name and version to prevent Script-kiddies from finding the information easily when fingerprinting the Application. The exact version number can tell an Attacker if the current Application Server is patched for or vulnerable to certain publicly known CVE associated to it.

### What type of PR is it?
[Improvement | Feature]

### What is the Jira issue?
* [ZEPPELIN-2461](https://issues.apache.org/jira/browse/ZEPPELIN-2461)

### How should this be tested?
Providing a value in zeppelin-site.xml will replace the actual Jetty server version found in HTTP Header with provided value. E.g.
 - edit zeppelin-site.xml and add a property `zeppelin.server.jetty.name` and with value say `TOMCAT`
 - restart the server
 - open the app in browser then observe the Response Headers for the key "Server"  this should now reflect "TOMCAT"

### Screenshots (if appropriate)

### Questions:
* Does the licenses files need update? N/A
* Is there breaking changes for older versions? N/A
* Does this needs documentation? N/A

Author: krishna-pandey <[email protected]>

Closes apache#2293 from krishna-pandey/ZEPPELIN-2461 and squashes the following commits:

b071f7a [krishna-pandey] Set App Server name to config value
prabhjyotsingh pushed a commit to prabhjyotsingh/zeppelin that referenced this pull request Sep 1, 2017
…arameter

### What is this PR for?
Security conscious organisations does not want to reveal the Application Server name and version to prevent Script-kiddies from finding the information easily when fingerprinting the Application. The exact version number can tell an Attacker if the current Application Server is patched for or vulnerable to certain publicly known CVE associated to it.

### What type of PR is it?
[Improvement | Feature]

### What is the Jira issue?
* [ZEPPELIN-2461](https://issues.apache.org/jira/browse/ZEPPELIN-2461)

### How should this be tested?
Providing a value in zeppelin-site.xml will replace the actual Jetty server version found in HTTP Header with provided value. E.g.
 - edit zeppelin-site.xml and add a property `zeppelin.server.jetty.name` and with value say `TOMCAT`
 - restart the server
 - open the app in browser then observe the Response Headers for the key "Server"  this should now reflect "TOMCAT"

### Screenshots (if appropriate)

### Questions:
* Does the licenses files need update? N/A
* Is there breaking changes for older versions? N/A
* Does this needs documentation? N/A

Author: krishna-pandey <[email protected]>

Closes apache#2293 from krishna-pandey/ZEPPELIN-2461 and squashes the following commits:

b071f7a [krishna-pandey] Set App Server name to config value
@krishna-pandey krishna-pandey deleted the ZEPPELIN-2461 branch February 12, 2022 16:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants