All Projects → fffonion → lua-resty-sniproxy

fffonion / lua-resty-sniproxy

Licence: other
SNI Proxy based on stream-lua-nginx-module

Programming Languages

lua
6591 projects

Projects that are alternatives of or similar to lua-resty-sniproxy

lua-resty-http2
The HTTP/2 Protocol (Client Side) Implementation for OpenResty.
Stars: ✭ 73 (-6.41%)
Mutual labels:  openresty
resty-marathon-lb
基于 OpenResty 的 Marathon 服务发现 & 路由
Stars: ✭ 13 (-83.33%)
Mutual labels:  openresty
docker-lapis
Dockerized Lapis
Stars: ✭ 20 (-74.36%)
Mutual labels:  openresty
z-blog-openresty
程序员技术之旅-OpenResty
Stars: ✭ 25 (-67.95%)
Mutual labels:  openresty
openresty-project-v0.01
🌹 基于OpenResty编写一个MVC模式的WEB项目 V0.01
Stars: ✭ 40 (-48.72%)
Mutual labels:  openresty
lua-resty-eureka-client
A Netflix Eureka client for OpenResty/ngx_lua
Stars: ✭ 18 (-76.92%)
Mutual labels:  openresty
wired-vpn
WireGuard behind OIDC
Stars: ✭ 21 (-73.08%)
Mutual labels:  openresty
httpdump
A complete openresty-based tool for dumping http request & response in json format log.
Stars: ✭ 15 (-80.77%)
Mutual labels:  openresty
lua-resty-pyf
Lua 汉字拼音首字母提取
Stars: ✭ 30 (-61.54%)
Mutual labels:  openresty
openresty dev
Code for OpenResty Development Guide
Stars: ✭ 85 (+8.97%)
Mutual labels:  openresty
lua-casbin
An authorization library that supports access control models like ACL, RBAC, ABAC in Lua (OpenResty)
Stars: ✭ 43 (-44.87%)
Mutual labels:  openresty
lua-resty-feishu-auth
适用于 OpenResty / ngx_lua 的基于飞书组织架构的登录认证
Stars: ✭ 28 (-64.1%)
Mutual labels:  openresty
lua-resty-openssl
FFI-based OpenSSL binding for OpenResty
Stars: ✭ 76 (-2.56%)
Mutual labels:  openresty
spacer
🚀Serverless function platform for Lua
Stars: ✭ 50 (-35.9%)
Mutual labels:  openresty
lua-mailgun
Lua bindings to Mailgun HTTP API
Stars: ✭ 25 (-67.95%)
Mutual labels:  openresty
casper
Yelp's internal caching proxy, powered by Nginx and OpenResty at its core
Stars: ✭ 81 (+3.85%)
Mutual labels:  openresty
lua-resty-timer
Extended timers for OpenResty
Stars: ✭ 20 (-74.36%)
Mutual labels:  openresty
lua-resty-ipcidr
A simple and very fast function to check against CIDR
Stars: ✭ 17 (-78.21%)
Mutual labels:  openresty
alpine-kong
alpine-kong
Stars: ✭ 15 (-80.77%)
Mutual labels:  openresty
docker-orange
Docker distribution for Orange.
Stars: ✭ 41 (-47.44%)
Mutual labels:  openresty

Name

lua-resty-sniproxy - SNI Proxy based on the ngx_lua cosocket API

Table of Contents

Description

This library is an SNI proxy written in Lua. TLS parsing part is rewritten from dlundquist/sniproxy

Note that nginx stream module and ngx_stream_lua_module is required.

Tested on Openresty >= 1.9.15.1.

Back to TOC

Status

Experimental.

Synopsis

stream {
    init_by_lua_block {
        local sni = require("resty.sniproxy")
        sni.rules = { 
            {"www.google.com", "www.google.com", 443},
            {"www.facebook.com", "9.8.7.6", 443},
            {"api.twitter.com", "1.2.3.4"},
            {".+.twitter.com", nil, 443},
            -- to activate this rule, you must use Lua land proxying
            -- {"some.service.svc", "unix:/var/run/nginx-proxy-proto.sock", nil, sni.SNI_PROXY_PROTOCOL_UPSTREAM},
            -- {"some2.service.svc", "unix:/var/run/nginx-proxy-proto.sock", nil,
            --                            sni.SNI_PROXY_PROTOCOL_UPSTREAM + sni.SNI_PROXY_PROTOCOL},
            {".", "unix:/var/run/nginx-default.sock"}
        }   
    }

    # for OpenResty >= 1.13.6.1, native Nginx proxying
    lua_add_variable $sniproxy_upstream;
    server {
            error_log /var/log/nginx/sniproxy-error.log error;
            listen 443;

            resolver 8.8.8.8;

            preread_by_lua_block {
                    local sni = require("resty.sniproxy")
                    local sp = sni:new()
                    sp:preread_by()
            }
            proxy_pass $sniproxy_upstream;
    }

    # for OpenResty < 1.13.6.1 or `flags` are configured, Lua land proxying
    server {
            error_log /var/log/nginx/sniproxy-error.log error;
            listen 443;

            resolver 8.8.8.8;

            content_by_lua_block {
                    local sni = require("resty.sniproxy")
                    local sp = sni:new()
                    sp:content_by()
            }
    }
}

A Lua array table sni_rules should be defined in the init_worker_by_lua_block directive.

The first value can be either whole host name or regular expression. Use . for a default host name. If no entry is matched, connection will be closed.

The second and third values are target host name and port. A host can be DNS name, IP address or UNIX domain socket path. If host is not defined or set to nil, server_name in SNI will be used. If the port is not defined or set to nil , 443 will be used.

The forth value is the flags to use. Available flags are:

    sni.SNI_PROXY_PROTOCOL -- use client address received from proxy protocol to send to upstream
    sni.SNI_PROXY_PROTOCOL_UPSTREAM -- send proxy protocol v1 handshake to upstream

To use flags, the server must be configured to do Lua land proxying (see above example).

Rules are applied with the priority as its occurrence sequence in the table. In the example above, api.twitter.com will match the third rule api.twitter.com rather than the fourth .+.twitter.com.

If the protocol version is less than TLSv1 (eg. SSLv3, SSLv2), connection will be closed, since SNI extension is not supported in these versions.

Back to TOC

TODO

  • stress and performance test

Back to TOC

Copyright and License

This module is licensed under the BSD license.

Copyright (C) 2016, by fffonion [email protected].

All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

  • Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Back to TOC

See Also

Back to TOC

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].