大网数据广告活动
服务器运维问答

Set up tinyproxy to only allow CONNECT to specific host

· 52CE 我爱测

At $DAYJOB, we produce several embedded devices, with access to a management network that often is not connected to the Internet. We also have a management console, running on a stadnard Red Hat or CentOS Linux, which has access …

问题原文

原帖链接 · nafmo · CC BY-SA 3.0

At $DAYJOB, we produce several embedded devices, with access to a management network that often is not connected to the Internet. We also have a management console, running on a stadnard Red Hat or CentOS Linux, which has access to both the management network and the Internet.

I am trying to get the embdded devices to authenticate themselves over the Internet towards a machine that we control over HTTPS, and am evaluating tinyproxy as a possible solution, but I am at a bit of a loss how to configure it.

In this setup, I want

  • to only allow the CONNECT method; and
  • to only allow the requests to terminate at a specific host (DNS resolvable).

Is it possible to use tinyproxy for this scenario using the standard configuration options? Hacking the sources is of course always an option, but using the standard RPMs is a lot easier.

已采纳解答

原帖链接 · nafmo · CC BY-SA 3.0

It doesn't seem to be possible to only allow CONNECT, but by using the Filter keyword to list the single domain I want to be able to access and using FilterDefaultDeny Yes, I can have it restrict forwarding requests to a single host, which is good enough for me.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2017-09-05)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。