mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-01-08 08:58:00 +00:00
5d718ef64b
The number of people has been steadily increasing who read our source
code with an editor that thinks tab stops are 4 spaces apart, as
opposed to the traditional tty-derived 8 that the PuTTY code expects.
So I've been wondering for ages about just fixing it, and switching to
a spaces-only policy throughout the code. And I recently found out
about 'git blame -w', which should make this change not too disruptive
for the purposes of source-control archaeology; so perhaps now is the
time.
While I'm at it, I've also taken the opportunity to remove all the
trailing spaces from source lines (on the basis that git dislikes
them, and is the only thing that seems to have a strong opinion one
way or the other).
Apologies to anyone downstream of this code who has complicated patch
sets to rebase past this change. I don't intend it to be needed again.
36 lines
894 B
C
36 lines
894 B
C
/*
|
|
* Routines to refuse to do cryptographic interaction with proxies
|
|
* in PuTTY. This is a stub implementation of the same interfaces
|
|
* provided by cproxy.c, for use in PuTTYtel.
|
|
*/
|
|
|
|
#include <assert.h>
|
|
#include <ctype.h>
|
|
#include <string.h>
|
|
|
|
#include "putty.h"
|
|
#include "network.h"
|
|
#include "proxy.h"
|
|
|
|
void proxy_socks5_offerencryptedauth(BinarySink *bs)
|
|
{
|
|
/* For telnet, don't add any new encrypted authentication routines */
|
|
}
|
|
|
|
int proxy_socks5_handlechap (ProxySocket *p)
|
|
{
|
|
|
|
plug_closing(p->plug, "Proxy error: Trying to handle a SOCKS5 CHAP request"
|
|
" in telnet-only build",
|
|
PROXY_ERROR_GENERAL, 0);
|
|
return 1;
|
|
}
|
|
|
|
int proxy_socks5_selectchap(ProxySocket *p)
|
|
{
|
|
plug_closing(p->plug, "Proxy error: Trying to handle a SOCKS5 CHAP request"
|
|
" in telnet-only build",
|
|
PROXY_ERROR_GENERAL, 0);
|
|
return 1;
|
|
}
|