Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Cherokee: dev

Issue 438 in cherokee: Feature Request: Server Tokens

 

 

Cherokee dev RSS feed   Index | Next | Previous | View Threaded


codesite-noreply at google

Apr 9, 2009, 10:27 PM

Post #1 of 12 (825 views)
Permalink
Issue 438 in cherokee: Feature Request: Server Tokens

Status: New
Owner: ----

New issue 438 by paulbatis: Feature Request: Server Tokens
http://code.google.com/p/cherokee/issues/detail?id=438

This feature request is to append another value to the default selections
for Server Tokens.

Would like for one of the options to be NONE. Where Cherokee doesn't report
what server or version or anything about what is serving the request.

This can be done manually by filtering out the information in Cherokee, but
I suspect that wastes more resources.

This is needed by many folks who are paranoid, involved in security,
attempting to reduce server hack attempts.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev


cherokee at googlecode

May 20, 2010, 11:01 AM

Post #2 of 12 (587 views)
Permalink
Re: Issue 438 in cherokee: Feature Request: Server Tokens [In reply to]

Comment #6 on issue 438 by Kissaki0: Feature Request: Server Tokens
http://code.google.com/p/cherokee/issues/detail?id=438

I second this.
From a security point of perspective, this should at least be an option.

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev


cherokee at googlecode

May 21, 2010, 10:22 AM

Post #3 of 12 (579 views)
Permalink
Re: Issue 438 in cherokee: Feature Request: Server Tokens [In reply to]

Comment #7 on issue 438 by remkade: Feature Request: Server Tokens
http://code.google.com/p/cherokee/issues/detail?id=438

I've updated the patch to work with 1.0.1.

Builds and runs well for me.

Attachments:
void-version-1.0.1.patch 3.3 KB

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev


cherokee at googlecode

May 21, 2010, 10:51 AM

Post #4 of 12 (585 views)
Permalink
Re: Issue 438 in cherokee: Feature Request: Server Tokens [In reply to]

Comment #8 on issue 438 by alobbs: Feature Request: Server Tokens
http://code.google.com/p/cherokee/issues/detail?id=438

Thanks remkade.
I'm afraid, the patch breaks the rest of the cases where the Server header
is used.

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev


cherokee at googlecode

Oct 26, 2010, 4:19 PM

Post #5 of 12 (466 views)
Permalink
Re: Issue 438 in cherokee: Feature Request: Server Tokens [In reply to]

Comment #9 on issue 438 by jrabbit.tth: Feature Request: Server Tokens
http://code.google.com/p/cherokee/issues/detail?id=438

I'd like to see this implemented. Although of little real-world value, this
is a guaranteed appearance on any penetration testing audit and senior
managers much prefer all issues to be addressed than to be told "this
really isn't important"

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev


cherokee at googlecode

Oct 26, 2010, 4:45 PM

Post #6 of 12 (447 views)
Permalink
Re: Issue 438 in cherokee: Feature Request: Server Tokens [In reply to]

Comment #10 on issue 438 by ste...@konink.de: Feature Request: Server Tokens
http://code.google.com/p/cherokee/issues/detail?id=438

So I understand it as: will appear on any security by obscurity audit?

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev


cherokee at googlecode

Oct 26, 2010, 6:14 PM

Post #7 of 12 (448 views)
Permalink
Re: Issue 438 in cherokee: Feature Request: Server Tokens [In reply to]

Comment #11 on issue 438 by remkade: Feature Request: Server Tokens
http://code.google.com/p/cherokee/issues/detail?id=438

Yeah its more of a cosmetic issue, but does have a small security benefit.

As trivial as it sounds this is one of the major issues that my corporation
cares about and due to corporate bureaucracy I can't use Cherokee without
manually editing the code to appear to be Apache or not respond at all.

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev


cherokee at googlecode

Oct 27, 2010, 12:34 AM

Post #8 of 12 (446 views)
Permalink
Re: Issue 438 in cherokee: Feature Request: Server Tokens [In reply to]

Comment #12 on issue 438 by Kissaki0: Feature Request: Server Tokens
http://code.google.com/p/cherokee/issues/detail?id=438

It’s not about security by obscurity being a bad security concept (which is
only if that’s the only action anyway).

Security is always about the ratio between investment / cost to benefit.
Changing a flag to not display the server name is a small cost, very
simple, and does add security.
It may not be much, and you may say Cherokee tries to be secure in other,
the more basic and more dangerous aspects,
but IF a security flaw is found that is unique to or does work on cherokee
attackers may profit from the info that cherokee is running more than from
no info at all.

Yes it is a small benefit and if you want real security you’ll just have to
stay up to date and use stable versions.
Still, that should be something users should be allowed to decide, just
like they should be allowed to decide on what infos they want to provide.

I can understand that cherokee devs and fans want to promote cherokee and
want themselves as well as others to be able to see that ppl. are using
cherokee,
but in my opinion allowing to not provide info on what webserver is running
to anyone should be something the hoster / admin decides and something that
would even further make cherokee better than webservers which don’t allow
you to decide.

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev


cherokee at googlecode

Oct 27, 2010, 12:38 AM

Post #9 of 12 (449 views)
Permalink
Re: Issue 438 in cherokee: Feature Request: Server Tokens [In reply to]

Comment #13 on issue 438 by Kissaki0: Feature Request: Server Tokens
http://code.google.com/p/cherokee/issues/detail?id=438

It’s not about security by obscurity being a bad security concept (which is
only if that’s the only action anyway).

Security is always about the ratio between investment / cost to benefit.
Changing a flag to not display the server name is a small cost, very
simple, and does add security.
It may not be much, and you may say Cherokee tries to be secure in other,
the more basic and more dangerous aspects,
but IF a security flaw is found that is unique to or does work on cherokee
attackers may profit from the info that cherokee is running more than from
no info at all.

Yes it is a small benefit and if you want real security you’ll just have to
stay up to date and use stable versions.
Still, that should be something users should be allowed to decide, just
like they should be allowed to decide on what infos they want to provide.

I can understand that cherokee devs and fans want to promote cherokee and
want themselves as well as others to be able to see that ppl. are using
cherokee,
but in my opinion allowing to not provide info on what webserver is running
to anyone should be something the hoster / admin decides and something that
would even further make cherokee better than webservers which don’t allow
you to decide.

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev


cherokee at googlecode

Oct 27, 2010, 12:26 PM

Post #10 of 12 (439 views)
Permalink
Re: Issue 438 in cherokee: Feature Request: Server Tokens [In reply to]

Comment #14 on issue 438 by jrabbit.tth: Feature Request: Server Tokens
http://code.google.com/p/cherokee/issues/detail?id=438

Security by obscurity alone is bad practice. However, security by obscurity
+ proper security is better than proper security alone. A good example is
running services like SSH that aren't used by the public to a non-default
port so you aren't hit by random-ip attacks if an exploit is found.

However, I don't think this helps much for the Server header. As an
attacker, why would I write code to sent a normal request to a random IP,
inspect the Server header and then send the attack; I'm sending twice as
many HTTP requests so it takes twice as long - why not just send the attack
straight away?

On the other hand, if the attacker is targeting your site specifically,
then they can use profiling techniques to easily determine what application
is serving the content, even if the server header is absent or lies.

The reason for having the option to remove it is more that corporate
security standards often require it, not because it is a good form of
security through obscurity. There are also cases when a server is used
purely for very small payload webservice hits that removing it could be a
significant bandwidth saving.

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev


cherokee at googlecode

Oct 13, 2011, 10:41 AM

Post #11 of 12 (109 views)
Permalink
Re: Issue 438 in cherokee: Feature Request: Server Tokens [In reply to]

Updates:
Status: Accepted
Owner: ste...@konink.de
Labels: Type-Enhancement Priority-Low Component-Logic Component-Admin
Security OpSys-All

Comment #15 on issue 438 by ste...@konink.de: Feature Request: Server Tokens
http://code.google.com/p/cherokee/issues/detail?id=438

Since we don't forget on you:

https://github.com/skinkie/webserver/commit/1d6ff06b2925b412321a1a778dc78e5585dfb6ee

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev


cherokee at googlecode

Oct 13, 2011, 1:37 PM

Post #12 of 12 (108 views)
Permalink
Re: Issue 438 in cherokee: Feature Request: Server Tokens [In reply to]

Comment #16 on issue 438 by Kissa...@gmail.com: Feature Request: Server
Tokens
http://code.google.com/p/cherokee/issues/detail?id=438

nice!

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

Cherokee dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.