nihilist/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-11-11 13:43:47 +01:00
Code Issues Packages Projects Releases Wiki Activity
e253e9577f
tor/src/or/connection_or.h

62 lines
2.6 KiB
C
Raw Normal View History

Create connection_or.h
2010-07-22 10:50:34 +02:00
/* Copyright (c) 2001 Matej Pfajfar.
* Copyright (c) 2001-2004, Roger Dingledine.
* Copyright (c) 2004-2006, Roger Dingledine, Nick Mathewson.
Bump copyright statements to 2011 (0.2.2)
2011-01-03 17:52:09 +01:00
* Copyright (c) 2007-2011, The Tor Project, Inc. */
Create connection_or.h
2010-07-22 10:50:34 +02:00
/* See LICENSE for licensing information */
/**
* \file connection_or.h
* \brief Header file for connection_or.c.
**/
#ifndef _TOR_CONNECTION_OR_H
#define _TOR_CONNECTION_OR_H
void connection_or_remove_from_identity_map(or_connection_t *conn);
void connection_or_clear_identity_map(void);
Record the states of failing OR connections This code lets us record the state of any outgoing OR connection that fails before it becomes open, so we can notice if they're all dying in the same SSL state or the same OR handshake state. More work is still needed: - We need documentation - We need to actually call the code that reports the failure when we realize that we're having a hard time connecting out or making circuits. - We need to periodically clear out all this data -- perhaps, whenever we build a circuit successfully? - We'll eventually want to expose it to controllers, perhaps. Partial implementation of feature 3116.
2011-06-22 21:29:30 +02:00
void clear_broken_connection_map(void);
Create connection_or.h
2010-07-22 10:50:34 +02:00
or_connection_t *connection_or_get_for_extend(const char *digest,
const tor_addr_t *target_addr,
const char **msg_out,
int *launch_out);
handle ugly edge case in retrying entrynodes Specifically, a circ attempt that we'd launched while the network was down could timeout after we've marked our entrynodes up, marking them back down again. The fix is to annotate as bad the OR conns that were around before we did the retry, so if a circuit that's attached to them times out we don't do anything about it.
2010-09-29 04:32:38 +02:00
void connection_or_set_bad_connections(const char *digest, int force);
Create connection_or.h
2010-07-22 10:50:34 +02:00
int connection_or_reached_eof(or_connection_t *conn);
int connection_or_process_inbuf(or_connection_t *conn);
int connection_or_flushed_some(or_connection_t *conn);
int connection_or_finished_flushing(or_connection_t *conn);
int connection_or_finished_connecting(or_connection_t *conn);
Split connection_about_to_close_connection into separate functions This patch does NOTHING but: - move code - add declarations and includes as needed to make the new code work - declare the new functions.
2011-06-22 19:57:19 +02:00
void connection_or_about_to_close(or_connection_t *conn);
Create connection_or.h
2010-07-22 10:50:34 +02:00
int connection_or_digest_is_known_relay(const char *id_digest);
reinit per-conn token buckets on config or consensus change
2010-08-15 10:01:42 +02:00
void connection_or_update_token_buckets(smartlist_t *conns,
Make the get_options() return const This lets us make a lot of other stuff const, allows the compiler to generate (slightly) better code, and will make me get slightly fewer patches from folks who stick mutable stuff into or_options_t. const: because not every input is an output!
2011-06-14 19:01:38 +02:00
const or_options_t *options);
Create connection_or.h
2010-07-22 10:50:34 +02:00
void connection_or_connect_failed(or_connection_t *conn,
int reason, const char *msg);
or_connection_t *connection_or_connect(const tor_addr_t *addr, uint16_t port,
const char *id_digest);
Record the states of failing OR connections This code lets us record the state of any outgoing OR connection that fails before it becomes open, so we can notice if they're all dying in the same SSL state or the same OR handshake state. More work is still needed: - We need documentation - We need to actually call the code that reports the failure when we realize that we're having a hard time connecting out or making circuits. - We need to periodically clear out all this data -- perhaps, whenever we build a circuit successfully? - We'll eventually want to expose it to controllers, perhaps. Partial implementation of feature 3116.
2011-06-22 21:29:30 +02:00
void connection_or_report_broken_states(int severity, int domain);
Create connection_or.h
2010-07-22 10:50:34 +02:00
int connection_tls_start_handshake(or_connection_t *conn, int receiving);
int connection_tls_continue_handshake(or_connection_t *conn);
void or_handshake_state_free(or_handshake_state_t *state);
int connection_or_set_state_open(or_connection_t *conn);
void connection_or_write_cell_to_buf(const cell_t *cell,
or_connection_t *conn);
void connection_or_write_var_cell_to_buf(const var_cell_t *cell,
or_connection_t *conn);
int connection_or_send_destroy(circid_t circ_id, or_connection_t *conn,
int reason);
int connection_or_send_netinfo(or_connection_t *conn);
int is_or_protocol_version_known(uint16_t version);
void cell_pack(packed_cell_t *dest, const cell_t *src);
void var_cell_pack_header(const var_cell_t *cell, char *hdr_out);
var_cell_t *var_cell_new(uint16_t payload_len);
void var_cell_free(var_cell_t *cell);
#endif
Reference in New Issue Copy Permalink