# Recent nginx security issue announce

**URL:** <https://www.ruby-forum.com/t/recent-nginx-security-issue-announce/228532>\
**Category:** NGINX\
**Created:** [April 26, 2013, 10:29am UTC](https://www.ruby-forum.com/t/recent-nginx-security-issue-announce/228532 "2013-04-26T10:29:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![xamdam](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/x/d78d45/32.png) [@xamdam](https://www.ruby-forum.com/u/xamdam)\
**Post date:** [April 26, 2013, 10:29am UTC](https://www.ruby-forum.com/t/recent-nginx-security-issue-announce/228532/1 "2013-04-26T10:29:12Z")

</div>

Hello,

On behalf of the nginx team I want to let the community know that we  
are aware of the recent security announce[\*] and working on the  
issue. We will share our conclusion when get more details about its  
nature and impact.

- [http://www.securityfocus.com/archive/1/526439/30/0/threaded](http://www.securityfocus.com/archive/1/526439/30/0/threaded)

–  
Maxim K.  
+7 (910) 4293178

> **[Professional Services | NGINX](https://www.nginx.com/services/)**
>
> NGINX's Professional Services team will help you take your application infrastructure to a new level of performance, scalability, and security

---

<div class="post-metadata">

**Author:** ![xamdam](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/x/d78d45/32.png) [@xamdam](https://www.ruby-forum.com/u/xamdam)\
**Post date:** [April 26, 2013, 11:13am UTC](https://www.ruby-forum.com/t/recent-nginx-security-issue-announce/228532/2 "2013-04-26T11:13:35Z")

</div>

It seems that they don’t know the meaning of responsible disclosure.  
They  
should have given you some time  
before going public. Unfortunately there are plenty of drama queens in  
the  
IT security field.

All responsible disclosure be gone, for I want to have the attribution:  
first post is all that matters.  
It builds cred among the “customer base”.

----appa