openSUSE Build Service

Overview Repositories Revisions Requests Users Attributes Meta

File mmproxy.spec of Package mmproxy

#
# spec file for package mmproxy
#
# Copyright (c) 2018 SUSE LINUX GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
# upon. The license for this file, and modifications and additions to the
# file, is the same license as for the pristine package itself (unless the
# license for the pristine package is not an Open Source License, in which
# case the license is the MIT License). An "Open Source License" is a
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative.

# Please submit bugfixes or comments via http://bugs.opensuse.org/
#

Name:           mmproxy
Version:        2018.7.0
Release:        0
Summary:        The magical PROXY protocol gateway
License:        BSD-3-Clause
Group:          Productivity/Networking/Security
Url:            https://github.com/cloudflare/mmproxy/releases
Source:         %{name}-%{version}.tar.gz
Source1:        meson.build
Patch:          fix-help.patch
BuildRoot:      %{_tmppath}/%{name}-%{version}-build
BuildRequires:  pkgconfig(libmill)
BuildRequires:  pkgconfig(libseccomp)
BuildRequires:  clang-devel
BuildRequires:  llvm-devel
BuildRequires:  meson
BuildRequires:  ninja

%description
mmproxy is a lightweight TCP proxy that serves exactly one purpose: to smooth
the transition of TCP servers to use proxy-protocol.

Usually, introducing TCP level load balancing introduces a significant problem
- the client source IP gets lost. From the application point of view the
inbound TCP connection is originated by load-balancer, not the real client.

Proxy-protocol is an invention from Haproxy, that aims to solve this:

https://www.haproxy.com/blog/haproxy/proxy-protocol/ Proxy-protocol defines an
exchange in which the first bytes transmitted from the load balancer will
describe the Client Source IP. This is great, but applications must explicitly
support proxy-protocol to use it.

For many mature applications introducing proxy-protocol support is hard.
"mmproxy" is a workaround to help in this case.

mmproxy sits near the application, receives the proxy-protocol enabled
connections from the load balancer, spoofs the client IP addresses, and sends
traffic directly to the application. From application point of view the traffic
look identically like it would have originated from the remote client.

%prep
%setup
%patch -p1
cp %{S:1} .

%build
%if %{with clang}
export CC=clang
%endif
%meson
%meson_build

%install
%meson_install

%files
%defattr(-,root,root)
%{_bindir}/mmproxy

%changelog

Places

File mmproxy.spec of Package mmproxy

Places