Completed
Push — add/changelog-77 ( fc32a5...198265 )
by Jeremy
26:28 queued 19:02
created

Manager::initialize_server()   A

Complexity

Conditions 1
Paths 1

Size

Total Lines 3

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
cc 1
nc 1
nop 0
dl 0
loc 3
rs 10
c 0
b 0
f 0
1
<?php
2
/**
3
 * The Jetpack Connection manager class file.
4
 *
5
 * @package jetpack-connection
6
 */
7
8
namespace Automattic\Jetpack\Connection;
9
10
use Automattic\Jetpack\Constants;
11
use Automattic\Jetpack\Tracking;
12
13
/**
14
 * The Jetpack Connection Manager class that is used as a single gateway between WordPress.com
15
 * and Jetpack.
16
 */
17
class Manager implements Manager_Interface {
18
19
	const SECRETS_MISSING        = 'secrets_missing';
20
	const SECRETS_EXPIRED        = 'secrets_expired';
21
	const SECRETS_OPTION_NAME    = 'jetpack_secrets';
22
	const MAGIC_NORMAL_TOKEN_KEY = ';normal;';
23
	const JETPACK_MASTER_USER    = true;
24
25
	/**
26
	 * The procedure that should be run to generate secrets.
27
	 *
28
	 * @var Callable
29
	 */
30
	protected $secret_callable;
31
32
	/**
33
	 * A copy of the raw POST data for signature verification purposes.
34
	 *
35
	 * @var String
36
	 */
37
	protected $raw_post_data;
38
39
	/**
40
	 * Verification data needs to be stored to properly verify everything.
41
	 *
42
	 * @var Object
43
	 */
44
	private $xmlrpc_verification = null;
45
46
	/**
47
	 * Initializes required listeners. This is done separately from the constructors
48
	 * because some objects sometimes need to instantiate separate objects of this class.
49
	 *
50
	 * @todo Implement a proper nonce verification.
51
	 */
52
	public function init() {
53
		$this->setup_xmlrpc_handlers(
54
			$_GET, // phpcs:ignore WordPress.Security.NonceVerification.Recommended
55
			$this->is_active(),
56
			$this->verify_xml_rpc_signature()
0 ignored issues
show
Bug introduced by
It seems like $this->verify_xml_rpc_signature() targeting Automattic\Jetpack\Conne...ify_xml_rpc_signature() can also be of type array; however, Automattic\Jetpack\Conne...setup_xmlrpc_handlers() does only seem to accept boolean, maybe add an additional type check?

This check looks at variables that are passed out again to other methods.

If the outgoing method call has stricter type requirements than the method itself, an issue is raised.

An additional type check may prevent trouble.

Loading history...
57
		);
58
59
		if ( $this->is_active() ) {
60
			add_filter( 'xmlrpc_methods', array( $this, 'public_xmlrpc_methods' ) );
61
		} else {
62
			add_action( 'rest_api_init', array( $this, 'initialize_rest_api_registration_connector' ) );
63
		}
64
	}
65
66
	/**
67
	 * Sets up the XMLRPC request handlers.
68
	 *
69
	 * @param Array                  $request_params incoming request parameters.
70
	 * @param Boolean                $is_active whether the connection is currently active.
71
	 * @param Boolean                $is_signed whether the signature check has been successful.
72
	 * @param \Jetpack_XMLRPC_Server $xmlrpc_server (optional) an instance of the server to use instead of instantiating a new one.
0 ignored issues
show
Documentation introduced by
Should the type for parameter $xmlrpc_server not be null|\Jetpack_XMLRPC_Server?

This check looks for @param annotations where the type inferred by our type inference engine differs from the declared type.

It makes a suggestion as to what type it considers more descriptive.

Most often this is a case of a parameter that can be null in addition to its declared types.

Loading history...
73
	 */
74
	public function setup_xmlrpc_handlers(
75
		$request_params,
76
		$is_active,
77
		$is_signed,
78
		\Jetpack_XMLRPC_Server $xmlrpc_server = null
79
	) {
80
		if (
81
			! isset( $request_params['for'] )
82
			|| 'jetpack' !== $request_params['for']
83
		) {
84
			return false;
85
		}
86
87
		// Alternate XML-RPC, via ?for=jetpack&jetpack=comms.
88
		if (
89
			isset( $request_params['jetpack'] )
90
			&& 'comms' === $request_params['jetpack']
91
		) {
92
			if ( ! Constants::is_defined( 'XMLRPC_REQUEST' ) ) {
93
				// Use the real constant here for WordPress' sake.
94
				define( 'XMLRPC_REQUEST', true );
95
			}
96
97
			add_action( 'template_redirect', array( $this, 'alternate_xmlrpc' ) );
98
99
			add_filter( 'xmlrpc_methods', array( $this, 'remove_non_jetpack_xmlrpc_methods' ), 1000 );
100
		}
101
102
		if ( ! Constants::get_constant( 'XMLRPC_REQUEST' ) ) {
103
			return false;
104
		}
105
		// Display errors can cause the XML to be not well formed.
106
		@ini_set( 'display_errors', false ); // phpcs:ignore
0 ignored issues
show
Security Best Practice introduced by
It seems like you do not handle an error condition here. This can introduce security issues, and is generally not recommended.

If you suppress an error, we recommend checking for the error condition explicitly:

// For example instead of
@mkdir($dir);

// Better use
if (@mkdir($dir) === false) {
    throw new \RuntimeException('The directory '.$dir.' could not be created.');
}
Loading history...
107
108
		if ( $xmlrpc_server ) {
109
			$this->xmlrpc_server = $xmlrpc_server;
0 ignored issues
show
Bug introduced by
The property xmlrpc_server does not exist. Did you maybe forget to declare it?

In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code:

class MyClass { }

$x = new MyClass();
$x->foo = true;

Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion:

class MyClass {
    public $foo;
}

$x = new MyClass();
$x->foo = true;
Loading history...
110
		} else {
111
			$this->xmlrpc_server = new \Jetpack_XMLRPC_Server();
112
		}
113
114
		$this->require_jetpack_authentication();
115
116
		if ( $is_active ) {
117
			// Hack to preserve $HTTP_RAW_POST_DATA.
118
			add_filter( 'xmlrpc_methods', array( $this, 'xmlrpc_methods' ) );
119
120
			if ( $is_signed ) {
121
				// The actual API methods.
122
				add_filter( 'xmlrpc_methods', array( $this->xmlrpc_server, 'xmlrpc_methods' ) );
123
			} else {
124
				// The jetpack.authorize method should be available for unauthenticated users on a site with an
125
				// active Jetpack connection, so that additional users can link their account.
126
				add_filter( 'xmlrpc_methods', array( $this->xmlrpc_server, 'authorize_xmlrpc_methods' ) );
127
			}
128
		} else {
129
			// The bootstrap API methods.
130
			add_filter( 'xmlrpc_methods', array( $this->xmlrpc_server, 'bootstrap_xmlrpc_methods' ) );
131
132
			if ( $is_signed ) {
133
				// The jetpack Provision method is available for blog-token-signed requests.
134
				add_filter( 'xmlrpc_methods', array( $this->xmlrpc_server, 'provision_xmlrpc_methods' ) );
135
			} else {
136
				new XMLRPC_Connector( $this );
137
			}
138
		}
139
140
		add_filter( 'xmlrpc_blog_options', array( $this, 'xmlrpc_options' ) );
141
142
		add_action( 'jetpack_clean_nonces', array( $this, 'clean_nonces' ) );
143
		if ( ! wp_next_scheduled( 'jetpack_clean_nonces' ) ) {
144
			wp_schedule_event( time(), 'hourly', 'jetpack_clean_nonces' );
145
		}
146
147
		// Now that no one can authenticate, and we're whitelisting all XML-RPC methods, force enable_xmlrpc on.
148
		add_filter( 'pre_option_enable_xmlrpc', '__return_true' );
149
150
		return true;
151
	}
152
153
	/**
154
	 * Initializes the REST API connector on the init hook.
155
	 */
156
	public function initialize_rest_api_registration_connector() {
157
		new REST_Connector( $this );
158
	}
159
160
	/**
161
	 * Since a lot of hosts use a hammer approach to "protecting" WordPress sites,
162
	 * and just blanket block all requests to /xmlrpc.php, or apply other overly-sensitive
163
	 * security/firewall policies, we provide our own alternate XML RPC API endpoint
164
	 * which is accessible via a different URI. Most of the below is copied directly
165
	 * from /xmlrpc.php so that we're replicating it as closely as possible.
166
	 *
167
	 * @todo Tighten $wp_xmlrpc_server_class a bit to make sure it doesn't do bad things.
168
	 */
169
	public function alternate_xmlrpc() {
170
		// phpcs:disable PHPCompatibility.Variables.RemovedPredefinedGlobalVariables.http_raw_post_dataDeprecatedRemoved
171
		// phpcs:disable WordPress.WP.GlobalVariablesOverride.Prohibited
172
		global $HTTP_RAW_POST_DATA;
173
174
		// Some browser-embedded clients send cookies. We don't want them.
175
		$_COOKIE = array();
176
177
		// A fix for mozBlog and other cases where '<?xml' isn't on the very first line.
178
		if ( isset( $HTTP_RAW_POST_DATA ) ) {
179
			$HTTP_RAW_POST_DATA = trim( $HTTP_RAW_POST_DATA );
180
		}
181
182
		// phpcs:enable
183
184
		include_once ABSPATH . 'wp-admin/includes/admin.php';
185
		include_once ABSPATH . WPINC . '/class-IXR.php';
186
		include_once ABSPATH . WPINC . '/class-wp-xmlrpc-server.php';
187
188
		/**
189
		 * Filters the class used for handling XML-RPC requests.
190
		 *
191
		 * @since 3.1.0
192
		 *
193
		 * @param string $class The name of the XML-RPC server class.
194
		 */
195
		$wp_xmlrpc_server_class = apply_filters( 'wp_xmlrpc_server_class', 'wp_xmlrpc_server' );
196
		$wp_xmlrpc_server       = new $wp_xmlrpc_server_class();
197
198
		// Fire off the request.
199
		nocache_headers();
200
		$wp_xmlrpc_server->serve_request();
201
202
		exit;
203
	}
204
205
	/**
206
	 * Removes all XML-RPC methods that are not `jetpack.*`.
207
	 * Only used in our alternate XML-RPC endpoint, where we want to
208
	 * ensure that Core and other plugins' methods are not exposed.
209
	 *
210
	 * @param array $methods a list of registered WordPress XMLRPC methods.
211
	 * @return array filtered $methods
212
	 */
213
	public function remove_non_jetpack_xmlrpc_methods( $methods ) {
214
		$jetpack_methods = array();
215
216
		foreach ( $methods as $method => $callback ) {
217
			if ( 0 === strpos( $method, 'jetpack.' ) ) {
218
				$jetpack_methods[ $method ] = $callback;
219
			}
220
		}
221
222
		return $jetpack_methods;
223
	}
224
225
	/**
226
	 * Removes all other authentication methods not to allow other
227
	 * methods to validate unauthenticated requests.
228
	 */
229
	public function require_jetpack_authentication() {
230
		// Don't let anyone authenticate.
231
		$_COOKIE = array();
232
		remove_all_filters( 'authenticate' );
233
		remove_all_actions( 'wp_login_failed' );
234
235
		if ( $this->is_active() ) {
236
			// Allow Jetpack authentication.
237
			add_filter( 'authenticate', array( $this, 'authenticate_jetpack' ), 10, 3 );
238
		}
239
	}
240
241
	/**
242
	 * Authenticates XML-RPC and other requests from the Jetpack Server
243
	 *
244
	 * @param WP_User|Mixed $user user object if authenticated.
245
	 * @param String        $username username.
246
	 * @param String        $password password string.
247
	 * @return WP_User|Mixed authenticated user or error.
248
	 */
249
	public function authenticate_jetpack( $user, $username, $password ) {
250
		if ( is_a( $user, '\\WP_User' ) ) {
251
			return $user;
252
		}
253
254
		$token_details = $this->verify_xml_rpc_signature();
255
256
		if ( ! $token_details ) {
257
			return $user;
258
		}
259
260
		if ( 'user' !== $token_details['type'] ) {
261
			return $user;
262
		}
263
264
		if ( ! $token_details['user_id'] ) {
265
			return $user;
266
		}
267
268
		nocache_headers();
269
270
		return new \WP_User( $token_details['user_id'] );
271
	}
272
273
	/**
274
	 * Verifies the signature of the current request.
275
	 *
276
	 * @return false|array
277
	 */
278
	public function verify_xml_rpc_signature() {
279
		if ( is_null( $this->xmlrpc_verification ) ) {
280
			$this->xmlrpc_verification = $this->internal_verify_xml_rpc_signature();
281
282
			if ( is_wp_error( $this->xmlrpc_verification ) ) {
283
				/**
284
				 * Action for logging XMLRPC signature verification errors. This data is sensitive.
285
				 *
286
				 * Error codes:
287
				 * - malformed_token
288
				 * - malformed_user_id
289
				 * - unknown_token
290
				 * - could_not_sign
291
				 * - invalid_nonce
292
				 * - signature_mismatch
293
				 *
294
				 * @since 7.5.0
295
				 *
296
				 * @param WP_Error $signature_verification_error The verification error
297
				 */
298
				do_action( 'jetpack_verify_signature_error', $this->xmlrpc_verification );
299
			}
300
		}
301
302
		return is_wp_error( $this->xmlrpc_verification ) ? false : $this->xmlrpc_verification;
303
	}
304
305
	/**
306
	 * Verifies the signature of the current request.
307
	 *
308
	 * This function has side effects and should not be used. Instead,
309
	 * use the memoized version `->verify_xml_rpc_signature()`.
310
	 *
311
	 * @internal
312
	 */
313
	private function internal_verify_xml_rpc_signature() {
314
		// It's not for us.
315
		if ( ! isset( $_GET['token'] ) || empty( $_GET['signature'] ) ) {
316
			return false;
317
		}
318
319
		$signature_details = array(
320
			'token'     => isset( $_GET['token'] ) ? wp_unslash( $_GET['token'] ) : '',
321
			'timestamp' => isset( $_GET['timestamp'] ) ? wp_unslash( $_GET['timestamp'] ) : '',
322
			'nonce'     => isset( $_GET['nonce'] ) ? wp_unslash( $_GET['nonce'] ) : '',
323
			'body_hash' => isset( $_GET['body-hash'] ) ? wp_unslash( $_GET['body-hash'] ) : '',
324
			'method'    => wp_unslash( $_SERVER['REQUEST_METHOD'] ),
325
			'url'       => wp_unslash( $_SERVER['HTTP_HOST'] . $_SERVER['REQUEST_URI'] ), // Temp - will get real signature URL later.
326
			'signature' => isset( $_GET['signature'] ) ? wp_unslash( $_GET['signature'] ) : '',
327
		);
328
329
		@list( $token_key, $version, $user_id ) = explode( ':', wp_unslash( $_GET['token'] ) );
0 ignored issues
show
Security Best Practice introduced by
It seems like you do not handle an error condition here. This can introduce security issues, and is generally not recommended.

If you suppress an error, we recommend checking for the error condition explicitly:

// For example instead of
@mkdir($dir);

// Better use
if (@mkdir($dir) === false) {
    throw new \RuntimeException('The directory '.$dir.' could not be created.');
}
Loading history...
330
		if (
331
			empty( $token_key )
332
		||
333
			empty( $version ) || strval( JETPACK__API_VERSION ) !== $version
334
		) {
335
			return new \WP_Error( 'malformed_token', 'Malformed token in request', compact( 'signature_details' ) );
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'malformed_token'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
336
		}
337
338
		if ( '0' === $user_id ) {
339
			$token_type = 'blog';
340
			$user_id    = 0;
341
		} else {
342
			$token_type = 'user';
343
			if ( empty( $user_id ) || ! ctype_digit( $user_id ) ) {
344
				return new \WP_Error(
345
					'malformed_user_id',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'malformed_user_id'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
346
					'Malformed user_id in request',
347
					compact( 'signature_details' )
348
				);
349
			}
350
			$user_id = (int) $user_id;
351
352
			$user = new \WP_User( $user_id );
353
			if ( ! $user || ! $user->exists() ) {
354
				return new \WP_Error(
355
					'unknown_user',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'unknown_user'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
356
					sprintf( 'User %d does not exist', $user_id ),
357
					compact( 'signature_details' )
358
				);
359
			}
360
		}
361
362
		$token = $this->get_access_token( $user_id, $token_key, false );
363
		if ( is_wp_error( $token ) ) {
364
			$token->add_data( compact( 'signature_details' ) );
365
			return $token;
366
		} elseif ( ! $token ) {
367
			return new \WP_Error(
368
				'unknown_token',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'unknown_token'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
369
				sprintf( 'Token %s:%s:%d does not exist', $token_key, $version, $user_id ),
370
				compact( 'signature_details' )
371
			);
372
		}
373
374
		$jetpack_signature = new \Jetpack_Signature( $token->secret, (int) \Jetpack_Options::get_option( 'time_diff' ) );
375
		// phpcs:disable WordPress.Security.NonceVerification.Missing
376
		if ( isset( $_POST['_jetpack_is_multipart'] ) ) {
377
			$post_data   = $_POST;
378
			$file_hashes = array();
379
			foreach ( $post_data as $post_data_key => $post_data_value ) {
380
				if ( 0 !== strpos( $post_data_key, '_jetpack_file_hmac_' ) ) {
381
					continue;
382
				}
383
				$post_data_key                 = substr( $post_data_key, strlen( '_jetpack_file_hmac_' ) );
384
				$file_hashes[ $post_data_key ] = $post_data_value;
385
			}
386
387
			foreach ( $file_hashes as $post_data_key => $post_data_value ) {
388
				unset( $post_data[ "_jetpack_file_hmac_{$post_data_key}" ] );
389
				$post_data[ $post_data_key ] = $post_data_value;
390
			}
391
392
			ksort( $post_data );
393
394
			$body = http_build_query( stripslashes_deep( $post_data ) );
395
		} elseif ( is_null( $this->raw_post_data ) ) {
396
			$body = file_get_contents( 'php://input' );
397
		} else {
398
			$body = null;
399
		}
400
		// phpcs:enable
401
402
		$signature = $jetpack_signature->sign_current_request(
403
			array( 'body' => is_null( $body ) ? $this->raw_post_data : $body )
404
		);
405
406
		$signature_details['url'] = $jetpack_signature->current_request_url;
407
408
		if ( ! $signature ) {
409
			return new \WP_Error(
410
				'could_not_sign',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'could_not_sign'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
411
				'Unknown signature error',
412
				compact( 'signature_details' )
413
			);
414
		} elseif ( is_wp_error( $signature ) ) {
415
			return $signature;
416
		}
417
418
		$timestamp = (int) $_GET['timestamp'];
419
		$nonce     = stripslashes( (string) $_GET['nonce'] );
420
421
		// Use up the nonce regardless of whether the signature matches.
422
		if ( ! $this->add_nonce( $timestamp, $nonce ) ) {
423
			return new \WP_Error(
424
				'invalid_nonce',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'invalid_nonce'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
425
				'Could not add nonce',
426
				compact( 'signature_details' )
427
			);
428
		}
429
430
		// Be careful about what you do with this debugging data.
431
		// If a malicious requester has access to the expected signature,
432
		// bad things might be possible.
433
		$signature_details['expected'] = $signature;
434
435
		if ( ! hash_equals( $signature, $_GET['signature'] ) ) {
436
			return new \WP_Error(
437
				'signature_mismatch',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'signature_mismatch'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
438
				'Signature mismatch',
439
				compact( 'signature_details' )
440
			);
441
		}
442
443
		/**
444
		 * Action for additional token checking.
445
		 *
446
		 * @since 7.7.0
447
		 *
448
		 * @param Array $post_data request data.
449
		 * @param Array $token_data token data.
450
		 */
451
		return apply_filters(
452
			'jetpack_signature_check_token',
453
			array(
454
				'type'      => $token_type,
455
				'token_key' => $token_key,
456
				'user_id'   => $token->external_user_id,
457
			),
458
			$token,
459
			$this->raw_post_data
460
		);
461
	}
462
463
	/**
464
	 * Returns true if the current site is connected to WordPress.com.
465
	 *
466
	 * @return Boolean is the site connected?
467
	 */
468
	public function is_active() {
469
		return (bool) $this->get_access_token( self::JETPACK_MASTER_USER );
0 ignored issues
show
Documentation introduced by
self::JETPACK_MASTER_USER is of type boolean, but the function expects a false|integer.

It seems like the type of the argument is not accepted by the function/method which you are calling.

In some cases, in particular if PHP’s automatic type-juggling kicks in this might be fine. In other cases, however this might be a bug.

We suggest to add an explicit type cast like in the following example:

function acceptsInteger($int) { }

$x = '123'; // string "123"

// Instead of
acceptsInteger($x);

// we recommend to use
acceptsInteger((integer) $x);
Loading history...
470
	}
471
472
	/**
473
	 * Returns true if the site has both a token and a blog id, which indicates a site has been registered.
474
	 *
475
	 * @access public
476
	 *
477
	 * @return bool
478
	 */
479
	public function is_registered() {
480
		$blog_id   = \Jetpack_Options::get_option( 'id' );
481
		$has_token = $this->is_active();
482
		return $blog_id && $has_token;
483
	}
484
485
	/**
486
	 * Returns true if the user with the specified identifier is connected to
487
	 * WordPress.com.
488
	 *
489
	 * @param Integer|Boolean $user_id the user identifier.
490
	 * @return Boolean is the user connected?
491
	 */
492
	public function is_user_connected( $user_id = false ) {
493
		$user_id = false === $user_id ? get_current_user_id() : absint( $user_id );
494
		if ( ! $user_id ) {
495
			return false;
496
		}
497
498
		return (bool) $this->get_access_token( $user_id );
499
	}
500
501
	/**
502
	 * Get the wpcom user data of the current|specified connected user.
503
	 *
504
	 * @todo Refactor to properly load the XMLRPC client independently.
505
	 *
506
	 * @param Integer $user_id the user identifier.
0 ignored issues
show
Documentation introduced by
Should the type for parameter $user_id not be integer|null?

This check looks for @param annotations where the type inferred by our type inference engine differs from the declared type.

It makes a suggestion as to what type it considers more descriptive.

Most often this is a case of a parameter that can be null in addition to its declared types.

Loading history...
507
	 * @return Object the user object.
508
	 */
509 View Code Duplication
	public function get_connected_user_data( $user_id = null ) {
510
		if ( ! $user_id ) {
0 ignored issues
show
Bug Best Practice introduced by
The expression $user_id of type integer|null is loosely compared to false; this is ambiguous if the integer can be zero. You might want to explicitly use === null instead.

In PHP, under loose comparison (like ==, or !=, or switch conditions), values of different types might be equal.

For integer values, zero is a special case, in particular the following results might be unexpected:

0   == false // true
0   == null  // true
123 == false // false
123 == null  // false

// It is often better to use strict comparison
0 === false // false
0 === null  // false
Loading history...
511
			$user_id = get_current_user_id();
512
		}
513
514
		$transient_key    = "jetpack_connected_user_data_$user_id";
515
		$cached_user_data = get_transient( $transient_key );
516
517
		if ( $cached_user_data ) {
518
			return $cached_user_data;
519
		}
520
521
		$xml = new \Jetpack_IXR_Client(
522
			array(
523
				'user_id' => $user_id,
524
			)
525
		);
526
		$xml->query( 'wpcom.getUser' );
527
		if ( ! $xml->isError() ) {
528
			$user_data = $xml->getResponse();
529
			set_transient( $transient_key, $xml->getResponse(), DAY_IN_SECONDS );
530
			return $user_data;
531
		}
532
533
		return false;
534
	}
535
536
	/**
537
	 * Returns true if the provided user is the Jetpack connection owner.
538
	 * If user ID is not specified, the current user will be used.
539
	 *
540
	 * @param Integer|Boolean $user_id the user identifier. False for current user.
541
	 * @return Boolean True the user the connection owner, false otherwise.
542
	 */
543
	public function is_connection_owner( $user_id = false ) {
544
		if ( ! $user_id ) {
545
			$user_id = get_current_user_id();
546
		}
547
548
		$user_token = $this->get_access_token( JETPACK_MASTER_USER );
0 ignored issues
show
Documentation introduced by
JETPACK_MASTER_USER is of type boolean, but the function expects a false|integer.

It seems like the type of the argument is not accepted by the function/method which you are calling.

In some cases, in particular if PHP’s automatic type-juggling kicks in this might be fine. In other cases, however this might be a bug.

We suggest to add an explicit type cast like in the following example:

function acceptsInteger($int) { }

$x = '123'; // string "123"

// Instead of
acceptsInteger($x);

// we recommend to use
acceptsInteger((integer) $x);
Loading history...
549
550
		return $user_token && is_object( $user_token ) && isset( $user_token->external_user_id ) && $user_id === $user_token->external_user_id;
551
	}
552
553
	/**
554
	 * Unlinks the current user from the linked WordPress.com user.
555
	 *
556
	 * @access public
557
	 * @static
558
	 *
559
	 * @todo Refactor to properly load the XMLRPC client independently.
560
	 *
561
	 * @param Integer $user_id the user identifier.
0 ignored issues
show
Documentation introduced by
Should the type for parameter $user_id not be integer|null?

This check looks for @param annotations where the type inferred by our type inference engine differs from the declared type.

It makes a suggestion as to what type it considers more descriptive.

Most often this is a case of a parameter that can be null in addition to its declared types.

Loading history...
562
	 * @return Boolean Whether the disconnection of the user was successful.
563
	 */
564
	public static function disconnect_user( $user_id = null ) {
565
		$tokens = \Jetpack_Options::get_option( 'user_tokens' );
566
		if ( ! $tokens ) {
567
			return false;
568
		}
569
570
		$user_id = empty( $user_id ) ? get_current_user_id() : intval( $user_id );
571
572
		if ( \Jetpack_Options::get_option( 'master_user' ) === $user_id ) {
573
			return false;
574
		}
575
576
		if ( ! isset( $tokens[ $user_id ] ) ) {
577
			return false;
578
		}
579
580
		$xml = new \Jetpack_IXR_Client( compact( 'user_id' ) );
581
		$xml->query( 'jetpack.unlink_user', $user_id );
582
583
		unset( $tokens[ $user_id ] );
584
585
		\Jetpack_Options::update_option( 'user_tokens', $tokens );
586
587
		/**
588
		 * Fires after the current user has been unlinked from WordPress.com.
589
		 *
590
		 * @since 4.1.0
591
		 *
592
		 * @param int $user_id The current user's ID.
593
		 */
594
		do_action( 'jetpack_unlinked_user', $user_id );
595
596
		return true;
597
	}
598
599
	/**
600
	 * Returns the requested Jetpack API URL.
601
	 *
602
	 * @param String $relative_url the relative API path.
603
	 * @return String API URL.
604
	 */
605
	public function api_url( $relative_url ) {
606
		$api_base = Constants::get_constant( 'JETPACK__API_BASE' );
607
		$version  = Constants::get_constant( 'JETPACK__API_VERSION' );
608
609
		$api_base = $api_base ? $api_base : 'https://jetpack.wordpress.com/jetpack.';
610
		$version  = $version ? '/' . $version . '/' : '/1/';
611
612
		return rtrim( $api_base . $relative_url, '/\\' ) . $version;
613
	}
614
615
	/**
616
	 * Attempts Jetpack registration which sets up the site for connection. Should
617
	 * remain public because the call to action comes from the current site, not from
618
	 * WordPress.com.
619
	 *
620
	 * @param String $api_endpoint (optional) an API endpoint to use, defaults to 'register'.
621
	 * @return Integer zero on success, or a bitmask on failure.
622
	 */
623
	public function register( $api_endpoint = 'register' ) {
624
		add_action( 'pre_update_jetpack_option_register', array( '\\Jetpack_Options', 'delete_option' ) );
625
		$secrets = $this->generate_secrets( 'register', get_current_user_id(), 600 );
626
627
		if (
628
			empty( $secrets['secret_1'] ) ||
629
			empty( $secrets['secret_2'] ) ||
630
			empty( $secrets['exp'] )
631
		) {
632
			return new \WP_Error( 'missing_secrets' );
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'missing_secrets'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
633
		}
634
635
		// Better to try (and fail) to set a higher timeout than this system
636
		// supports than to have register fail for more users than it should.
637
		$timeout = $this->set_min_time_limit( 60 ) / 2;
638
639
		$gmt_offset = get_option( 'gmt_offset' );
640
		if ( ! $gmt_offset ) {
641
			$gmt_offset = 0;
642
		}
643
644
		$stats_options = get_option( 'stats_options' );
645
		$stats_id      = isset( $stats_options['blog_id'] )
646
			? $stats_options['blog_id']
647
			: null;
648
649
		/**
650
		 * Filters the request body for additional property addition.
651
		 *
652
		 * @since 7.7.0
653
		 *
654
		 * @param Array $post_data request data.
655
		 * @param Array $token_data token data.
656
		 */
657
		$body = apply_filters(
658
			'jetpack_register_request_body',
659
			array(
660
				'siteurl'         => site_url(),
661
				'home'            => home_url(),
662
				'gmt_offset'      => $gmt_offset,
663
				'timezone_string' => (string) get_option( 'timezone_string' ),
664
				'site_name'       => (string) get_option( 'blogname' ),
665
				'secret_1'        => $secrets['secret_1'],
666
				'secret_2'        => $secrets['secret_2'],
667
				'site_lang'       => get_locale(),
668
				'timeout'         => $timeout,
669
				'stats_id'        => $stats_id,
670
				'state'           => get_current_user_id(),
671
				'site_created'    => $this->get_assumed_site_creation_date(),
672
				'jetpack_version' => Constants::get_constant( 'JETPACK__VERSION' ),
673
			)
674
		);
675
676
		$args = array(
677
			'method'  => 'POST',
678
			'body'    => $body,
679
			'headers' => array(
680
				'Accept' => 'application/json',
681
			),
682
			'timeout' => $timeout,
683
		);
684
685
		$args['body'] = $this->apply_activation_source_to_args( $args['body'] );
686
687
		// TODO: fix URLs for bad hosts.
688
		$response = Client::_wp_remote_request(
689
			$this->api_url( $api_endpoint ),
690
			$args,
691
			true
692
		);
693
694
		// Make sure the response is valid and does not contain any Jetpack errors.
695
		$registration_details = $this->validate_remote_register_response( $response );
696
697
		if ( is_wp_error( $registration_details ) ) {
698
			return $registration_details;
699
		} elseif ( ! $registration_details ) {
700
			return new \WP_Error(
701
				'unknown_error',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'unknown_error'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
702
				'Unknown error registering your Jetpack site.',
703
				wp_remote_retrieve_response_code( $response )
704
			);
705
		}
706
707
		if ( empty( $registration_details->jetpack_secret ) || ! is_string( $registration_details->jetpack_secret ) ) {
708
			return new \WP_Error(
709
				'jetpack_secret',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'jetpack_secret'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
710
				'Unable to validate registration of your Jetpack site.',
711
				wp_remote_retrieve_response_code( $response )
712
			);
713
		}
714
715
		if ( isset( $registration_details->jetpack_public ) ) {
716
			$jetpack_public = (int) $registration_details->jetpack_public;
717
		} else {
718
			$jetpack_public = false;
719
		}
720
721
		\Jetpack_Options::update_options(
722
			array(
723
				'id'         => (int) $registration_details->jetpack_id,
724
				'blog_token' => (string) $registration_details->jetpack_secret,
725
				'public'     => $jetpack_public,
726
			)
727
		);
728
729
		/**
730
		 * Fires when a site is registered on WordPress.com.
731
		 *
732
		 * @since 3.7.0
733
		 *
734
		 * @param int $json->jetpack_id Jetpack Blog ID.
735
		 * @param string $json->jetpack_secret Jetpack Blog Token.
736
		 * @param int|bool $jetpack_public Is the site public.
737
		 */
738
		do_action(
739
			'jetpack_site_registered',
740
			$registration_details->jetpack_id,
741
			$registration_details->jetpack_secret,
742
			$jetpack_public
743
		);
744
745
		if ( isset( $registration_details->token ) ) {
746
			/**
747
			 * Fires when a user token is sent along with the registration data.
748
			 *
749
			 * @since 7.6.0
750
			 *
751
			 * @param object $token the administrator token for the newly registered site.
752
			 */
753
			do_action( 'jetpack_site_registered_user_token', $registration_details->token );
754
		}
755
756
		return true;
757
	}
758
759
	/**
760
	 * Takes the response from the Jetpack register new site endpoint and
761
	 * verifies it worked properly.
762
	 *
763
	 * @since 2.6
764
	 *
765
	 * @param Mixed $response the response object, or the error object.
766
	 * @return string|WP_Error A JSON object on success or Jetpack_Error on failures
767
	 **/
768
	protected function validate_remote_register_response( $response ) {
769
		if ( is_wp_error( $response ) ) {
770
			return new \WP_Error(
771
				'register_http_request_failed',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'register_http_request_failed'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
772
				$response->get_error_message()
773
			);
774
		}
775
776
		$code   = wp_remote_retrieve_response_code( $response );
777
		$entity = wp_remote_retrieve_body( $response );
778
779
		if ( $entity ) {
780
			$registration_response = json_decode( $entity );
781
		} else {
782
			$registration_response = false;
783
		}
784
785
		$code_type = intval( $code / 100 );
786
		if ( 5 === $code_type ) {
787
			return new \WP_Error( 'wpcom_5??', $code );
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'wpcom_5??'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
788
		} elseif ( 408 === $code ) {
789
			return new \WP_Error( 'wpcom_408', $code );
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'wpcom_408'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
790
		} elseif ( ! empty( $registration_response->error ) ) {
791
			if (
792
				'xml_rpc-32700' === $registration_response->error
793
				&& ! function_exists( 'xml_parser_create' )
794
			) {
795
				$error_description = __( "PHP's XML extension is not available. Jetpack requires the XML extension to communicate with WordPress.com. Please contact your hosting provider to enable PHP's XML extension.", 'jetpack' );
796
			} else {
797
				$error_description = isset( $registration_response->error_description )
798
					? (string) $registration_response->error_description
799
					: '';
800
			}
801
802
			return new \WP_Error(
803
				(string) $registration_response->error,
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with (string) $registration_response->error.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
804
				$error_description,
805
				$code
806
			);
807
		} elseif ( 200 !== $code ) {
808
			return new \WP_Error( 'wpcom_bad_response', $code );
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'wpcom_bad_response'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
809
		}
810
811
		// Jetpack ID error block.
812
		if ( empty( $registration_response->jetpack_id ) ) {
813
			return new \WP_Error(
814
				'jetpack_id',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'jetpack_id'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
815
				/* translators: %s is an error message string */
816
				sprintf( __( 'Error Details: Jetpack ID is empty. Do not publicly post this error message! %s', 'jetpack' ), $entity ),
817
				$entity
818
			);
819
		} elseif ( ! is_scalar( $registration_response->jetpack_id ) ) {
820
			return new \WP_Error(
821
				'jetpack_id',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'jetpack_id'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
822
				/* translators: %s is an error message string */
823
				sprintf( __( 'Error Details: Jetpack ID is not a scalar. Do not publicly post this error message! %s', 'jetpack' ), $entity ),
824
				$entity
825
			);
826
		} elseif ( preg_match( '/[^0-9]/', $registration_response->jetpack_id ) ) {
827
			return new \WP_Error(
828
				'jetpack_id',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'jetpack_id'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
829
				/* translators: %s is an error message string */
830
				sprintf( __( 'Error Details: Jetpack ID begins with a numeral. Do not publicly post this error message! %s', 'jetpack' ), $entity ),
831
				$entity
832
			);
833
		}
834
835
		return $registration_response;
836
	}
837
838
	/**
839
	 * Adds a used nonce to a list of known nonces.
840
	 *
841
	 * @param int    $timestamp the current request timestamp.
842
	 * @param string $nonce the nonce value.
843
	 * @return bool whether the nonce is unique or not.
844
	 */
845
	public function add_nonce( $timestamp, $nonce ) {
846
		global $wpdb;
847
		static $nonces_used_this_request = array();
848
849
		if ( isset( $nonces_used_this_request[ "$timestamp:$nonce" ] ) ) {
850
			return $nonces_used_this_request[ "$timestamp:$nonce" ];
851
		}
852
853
		// This should always have gone through Jetpack_Signature::sign_request() first to check $timestamp an $nonce.
854
		$timestamp = (int) $timestamp;
855
		$nonce     = esc_sql( $nonce );
856
857
		// Raw query so we can avoid races: add_option will also update.
858
		$show_errors = $wpdb->show_errors( false );
859
860
		$old_nonce = $wpdb->get_row(
861
			$wpdb->prepare( "SELECT * FROM `$wpdb->options` WHERE option_name = %s", "jetpack_nonce_{$timestamp}_{$nonce}" )
862
		);
863
864
		if ( is_null( $old_nonce ) ) {
865
			$return = $wpdb->query(
866
				$wpdb->prepare(
867
					"INSERT INTO `$wpdb->options` (`option_name`, `option_value`, `autoload`) VALUES (%s, %s, %s)",
868
					"jetpack_nonce_{$timestamp}_{$nonce}",
869
					time(),
870
					'no'
871
				)
872
			);
873
		} else {
874
			$return = false;
875
		}
876
877
		$wpdb->show_errors( $show_errors );
878
879
		$nonces_used_this_request[ "$timestamp:$nonce" ] = $return;
880
881
		return $return;
882
	}
883
884
	/**
885
	 * Cleans nonces that were saved when calling ::add_nonce.
886
	 *
887
	 * @todo Properly prepare the query before executing it.
888
	 *
889
	 * @param bool $all whether to clean even non-expired nonces.
890
	 */
891
	public function clean_nonces( $all = false ) {
892
		global $wpdb;
893
894
		$sql      = "DELETE FROM `$wpdb->options` WHERE `option_name` LIKE %s";
895
		$sql_args = array( $wpdb->esc_like( 'jetpack_nonce_' ) . '%' );
896
897
		if ( true !== $all ) {
898
			$sql       .= ' AND CAST( `option_value` AS UNSIGNED ) < %d';
899
			$sql_args[] = time() - 3600;
900
		}
901
902
		$sql .= ' ORDER BY `option_id` LIMIT 100';
903
904
		$sql = $wpdb->prepare( $sql, $sql_args ); // phpcs:ignore WordPress.DB.PreparedSQL.NotPrepared
905
906
		for ( $i = 0; $i < 1000; $i++ ) {
907
			if ( ! $wpdb->query( $sql ) ) { // phpcs:ignore WordPress.DB.PreparedSQL.NotPrepared
908
				break;
909
			}
910
		}
911
	}
912
913
	/**
914
	 * Builds the timeout limit for queries talking with the wpcom servers.
915
	 *
916
	 * Based on local php max_execution_time in php.ini
917
	 *
918
	 * @since 5.4
919
	 * @return int
920
	 **/
921
	public function get_max_execution_time() {
922
		$timeout = (int) ini_get( 'max_execution_time' );
923
924
		// Ensure exec time set in php.ini.
925
		if ( ! $timeout ) {
926
			$timeout = 30;
927
		}
928
		return $timeout;
929
	}
930
931
	/**
932
	 * Sets a minimum request timeout, and returns the current timeout
933
	 *
934
	 * @since 5.4
935
	 * @param Integer $min_timeout the minimum timeout value.
936
	 **/
937 View Code Duplication
	public function set_min_time_limit( $min_timeout ) {
938
		$timeout = $this->get_max_execution_time();
939
		if ( $timeout < $min_timeout ) {
940
			$timeout = $min_timeout;
941
			set_time_limit( $timeout );
942
		}
943
		return $timeout;
944
	}
945
946
	/**
947
	 * Get our assumed site creation date.
948
	 * Calculated based on the earlier date of either:
949
	 * - Earliest admin user registration date.
950
	 * - Earliest date of post of any post type.
951
	 *
952
	 * @since 7.2.0
953
	 *
954
	 * @return string Assumed site creation date and time.
955
	 */
956 View Code Duplication
	public function get_assumed_site_creation_date() {
957
		$earliest_registered_users  = get_users(
958
			array(
959
				'role'    => 'administrator',
960
				'orderby' => 'user_registered',
961
				'order'   => 'ASC',
962
				'fields'  => array( 'user_registered' ),
963
				'number'  => 1,
964
			)
965
		);
966
		$earliest_registration_date = $earliest_registered_users[0]->user_registered;
967
968
		$earliest_posts = get_posts(
969
			array(
970
				'posts_per_page' => 1,
971
				'post_type'      => 'any',
972
				'post_status'    => 'any',
973
				'orderby'        => 'date',
974
				'order'          => 'ASC',
975
			)
976
		);
977
978
		// If there are no posts at all, we'll count only on user registration date.
979
		if ( $earliest_posts ) {
980
			$earliest_post_date = $earliest_posts[0]->post_date;
981
		} else {
982
			$earliest_post_date = PHP_INT_MAX;
983
		}
984
985
		return min( $earliest_registration_date, $earliest_post_date );
986
	}
987
988
	/**
989
	 * Adds the activation source string as a parameter to passed arguments.
990
	 *
991
	 * @param Array $args arguments that need to have the source added.
992
	 * @return Array $amended arguments.
993
	 */
994 View Code Duplication
	public static function apply_activation_source_to_args( $args ) {
995
		list( $activation_source_name, $activation_source_keyword ) = get_option( 'jetpack_activation_source' );
996
997
		if ( $activation_source_name ) {
998
			$args['_as'] = urlencode( $activation_source_name );
999
		}
1000
1001
		if ( $activation_source_keyword ) {
1002
			$args['_ak'] = urlencode( $activation_source_keyword );
1003
		}
1004
1005
		return $args;
1006
	}
1007
1008
	/**
1009
	 * Returns the callable that would be used to generate secrets.
1010
	 *
1011
	 * @return Callable a function that returns a secure string to be used as a secret.
1012
	 */
1013
	protected function get_secret_callable() {
1014
		if ( ! isset( $this->secret_callable ) ) {
1015
			/**
1016
			 * Allows modification of the callable that is used to generate connection secrets.
1017
			 *
1018
			 * @param Callable a function or method that returns a secret string.
1019
			 */
1020
			$this->secret_callable = apply_filters( 'jetpack_connection_secret_generator', 'wp_generate_password' );
1021
		}
1022
1023
		return $this->secret_callable;
1024
	}
1025
1026
	/**
1027
	 * Generates two secret tokens and the end of life timestamp for them.
1028
	 *
1029
	 * @param String  $action  The action name.
1030
	 * @param Integer $user_id The user identifier.
0 ignored issues
show
Documentation introduced by
Should the type for parameter $user_id not be false|integer?

This check looks for @param annotations where the type inferred by our type inference engine differs from the declared type.

It makes a suggestion as to what type it considers more descriptive.

Most often this is a case of a parameter that can be null in addition to its declared types.

Loading history...
1031
	 * @param Integer $exp     Expiration time in seconds.
1032
	 */
1033
	public function generate_secrets( $action, $user_id = false, $exp = 600 ) {
1034
		$callable = $this->get_secret_callable();
1035
1036
		$secrets = \Jetpack_Options::get_raw_option(
1037
			self::SECRETS_OPTION_NAME,
1038
			array()
1039
		);
1040
1041
		$secret_name = 'jetpack_' . $action . '_' . $user_id;
1042
1043
		if (
1044
			isset( $secrets[ $secret_name ] ) &&
1045
			$secrets[ $secret_name ]['exp'] > time()
1046
		) {
1047
			return $secrets[ $secret_name ];
1048
		}
1049
1050
		$secret_value = array(
1051
			'secret_1' => call_user_func( $callable ),
1052
			'secret_2' => call_user_func( $callable ),
1053
			'exp'      => time() + $exp,
1054
		);
1055
1056
		$secrets[ $secret_name ] = $secret_value;
1057
1058
		\Jetpack_Options::update_raw_option( self::SECRETS_OPTION_NAME, $secrets );
1059
		return $secrets[ $secret_name ];
1060
	}
1061
1062
	/**
1063
	 * Returns two secret tokens and the end of life timestamp for them.
1064
	 *
1065
	 * @param String  $action  The action name.
1066
	 * @param Integer $user_id The user identifier.
1067
	 * @return string|array an array of secrets or an error string.
1068
	 */
1069
	public function get_secrets( $action, $user_id ) {
1070
		$secret_name = 'jetpack_' . $action . '_' . $user_id;
1071
		$secrets     = \Jetpack_Options::get_raw_option(
1072
			self::SECRETS_OPTION_NAME,
1073
			array()
1074
		);
1075
1076
		if ( ! isset( $secrets[ $secret_name ] ) ) {
1077
			return self::SECRETS_MISSING;
1078
		}
1079
1080
		if ( $secrets[ $secret_name ]['exp'] < time() ) {
1081
			$this->delete_secrets( $action, $user_id );
1082
			return self::SECRETS_EXPIRED;
1083
		}
1084
1085
		return $secrets[ $secret_name ];
1086
	}
1087
1088
	/**
1089
	 * Deletes secret tokens in case they, for example, have expired.
1090
	 *
1091
	 * @param String  $action  The action name.
1092
	 * @param Integer $user_id The user identifier.
1093
	 */
1094
	public function delete_secrets( $action, $user_id ) {
1095
		$secret_name = 'jetpack_' . $action . '_' . $user_id;
1096
		$secrets     = \Jetpack_Options::get_raw_option(
1097
			self::SECRETS_OPTION_NAME,
1098
			array()
1099
		);
1100
		if ( isset( $secrets[ $secret_name ] ) ) {
1101
			unset( $secrets[ $secret_name ] );
1102
			\Jetpack_Options::update_raw_option( self::SECRETS_OPTION_NAME, $secrets );
1103
		}
1104
	}
1105
1106
	/**
1107
	 * Responds to a WordPress.com call to register the current site.
1108
	 * Should be changed to protected.
1109
	 *
1110
	 * @param array $registration_data Array of [ secret_1, user_id ].
1111
	 */
1112
	public function handle_registration( array $registration_data ) {
1113
		list( $registration_secret_1, $registration_user_id ) = $registration_data;
1114
		if ( empty( $registration_user_id ) ) {
1115
			return new \WP_Error( 'registration_state_invalid', __( 'Invalid Registration State', 'jetpack' ), 400 );
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'registration_state_invalid'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
1116
		}
1117
1118
		return $this->verify_secrets( 'register', $registration_secret_1, (int) $registration_user_id );
1119
	}
1120
1121
	/**
1122
	 * Verify a Previously Generated Secret.
1123
	 *
1124
	 * @param string $action   The type of secret to verify.
1125
	 * @param string $secret_1 The secret string to compare to what is stored.
1126
	 * @param int    $user_id  The user ID of the owner of the secret.
1127
	 */
1128
	protected function verify_secrets( $action, $secret_1, $user_id ) {
1129
		$allowed_actions = array( 'register', 'authorize', 'publicize' );
1130
		if ( ! in_array( $action, $allowed_actions, true ) ) {
1131
			return new \WP_Error( 'unknown_verification_action', 'Unknown Verification Action', 400 );
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'unknown_verification_action'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
1132
		}
1133
1134
		$user = get_user_by( 'id', $user_id );
1135
1136
		/**
1137
		 * We've begun verifying the previously generated secret.
1138
		 *
1139
		 * @since 7.5.0
1140
		 *
1141
		 * @param string   $action The type of secret to verify.
1142
		 * @param \WP_User $user The user object.
1143
		 */
1144
		do_action( 'jetpack_verify_secrets_begin', $action, $user );
1145
1146
		$return_error = function( \WP_Error $error ) use ( $action, $user ) {
1147
			/**
1148
			 * Verifying of the previously generated secret has failed.
1149
			 *
1150
			 * @since 7.5.0
1151
			 *
1152
			 * @param string    $action  The type of secret to verify.
1153
			 * @param \WP_User  $user The user object.
1154
			 * @param \WP_Error $error The error object.
1155
			 */
1156
			do_action( 'jetpack_verify_secrets_fail', $action, $user, $error );
1157
1158
			return $error;
1159
		};
1160
1161
		$stored_secrets = $this->get_secrets( $action, $user_id );
1162
		$this->delete_secrets( $action, $user_id );
1163
1164
		if ( empty( $secret_1 ) ) {
1165
			return $return_error(
1166
				new \WP_Error(
1167
					'verify_secret_1_missing',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'verify_secret_1_missing'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
1168
					/* translators: "%s" is the name of a paramter. It can be either "secret_1" or "state". */
1169
					sprintf( __( 'The required "%s" parameter is missing.', 'jetpack' ), 'secret_1' ),
1170
					400
1171
				)
1172
			);
1173
		} elseif ( ! is_string( $secret_1 ) ) {
1174
			return $return_error(
1175
				new \WP_Error(
1176
					'verify_secret_1_malformed',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'verify_secret_1_malformed'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
1177
					/* translators: "%s" is the name of a paramter. It can be either "secret_1" or "state". */
1178
					sprintf( __( 'The required "%s" parameter is malformed.', 'jetpack' ), 'secret_1' ),
1179
					400
1180
				)
1181
			);
1182
		} elseif ( empty( $user_id ) ) {
1183
			// $user_id is passed around during registration as "state".
1184
			return $return_error(
1185
				new \WP_Error(
1186
					'state_missing',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'state_missing'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
1187
					/* translators: "%s" is the name of a paramter. It can be either "secret_1" or "state". */
1188
					sprintf( __( 'The required "%s" parameter is missing.', 'jetpack' ), 'state' ),
1189
					400
1190
				)
1191
			);
1192
		} elseif ( ! ctype_digit( (string) $user_id ) ) {
1193
			return $return_error(
1194
				new \WP_Error(
1195
					'verify_secret_1_malformed',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'verify_secret_1_malformed'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
1196
					/* translators: "%s" is the name of a paramter. It can be either "secret_1" or "state". */
1197
					sprintf( __( 'The required "%s" parameter is malformed.', 'jetpack' ), 'state' ),
1198
					400
1199
				)
1200
			);
1201
		}
1202
1203
		if ( self::SECRETS_MISSING === $stored_secrets ) {
1204
			return $return_error(
1205
				new \WP_Error(
1206
					'verify_secrets_missing',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'verify_secrets_missing'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
1207
					__( 'Verification secrets not found', 'jetpack' ),
1208
					400
1209
				)
1210
			);
1211
		} elseif ( self::SECRETS_EXPIRED === $stored_secrets ) {
1212
			return $return_error(
1213
				new \WP_Error(
1214
					'verify_secrets_expired',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'verify_secrets_expired'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
1215
					__( 'Verification took too long', 'jetpack' ),
1216
					400
1217
				)
1218
			);
1219
		} elseif ( ! $stored_secrets ) {
1220
			return $return_error(
1221
				new \WP_Error(
1222
					'verify_secrets_empty',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'verify_secrets_empty'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
1223
					__( 'Verification secrets are empty', 'jetpack' ),
1224
					400
1225
				)
1226
			);
1227
		} elseif ( is_wp_error( $stored_secrets ) ) {
1228
			$stored_secrets->add_data( 400 );
0 ignored issues
show
Bug introduced by
The method add_data cannot be called on $stored_secrets (of type string|array).

Methods can only be called on objects. This check looks for methods being called on variables that have been inferred to never be objects.

Loading history...
1229
			return $return_error( $stored_secrets );
1230
		} elseif ( empty( $stored_secrets['secret_1'] ) || empty( $stored_secrets['secret_2'] ) || empty( $stored_secrets['exp'] ) ) {
1231
			return $return_error(
1232
				new \WP_Error(
1233
					'verify_secrets_incomplete',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'verify_secrets_incomplete'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
1234
					__( 'Verification secrets are incomplete', 'jetpack' ),
1235
					400
1236
				)
1237
			);
1238
		} elseif ( ! hash_equals( $secret_1, $stored_secrets['secret_1'] ) ) {
1239
			return $return_error(
1240
				new \WP_Error(
1241
					'verify_secrets_mismatch',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'verify_secrets_mismatch'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
1242
					__( 'Secret mismatch', 'jetpack' ),
1243
					400
1244
				)
1245
			);
1246
		}
1247
1248
		/**
1249
		 * We've succeeded at verifying the previously generated secret.
1250
		 *
1251
		 * @since 7.5.0
1252
		 *
1253
		 * @param string   $action The type of secret to verify.
1254
		 * @param \WP_User $user The user object.
1255
		 */
1256
		do_action( 'jetpack_verify_secrets_success', $action, $user );
1257
1258
		return $stored_secrets['secret_2'];
1259
	}
1260
1261
	/**
1262
	 * Responds to a WordPress.com call to authorize the current user.
1263
	 * Should be changed to protected.
1264
	 */
1265
	public function handle_authorization() {
1266
1267
	}
1268
1269
	/**
1270
	 * Builds a URL to the Jetpack connection auth page.
1271
	 * This needs rethinking.
1272
	 *
1273
	 * @param bool        $raw If true, URL will not be escaped.
1274
	 * @param bool|string $redirect If true, will redirect back to Jetpack wp-admin landing page after connection.
1275
	 *                              If string, will be a custom redirect.
1276
	 * @param bool|string $from If not false, adds 'from=$from' param to the connect URL.
1277
	 * @param bool        $register If true, will generate a register URL regardless of the existing token, since 4.9.0.
1278
	 *
1279
	 * @return string Connect URL
1280
	 */
1281
	public function build_connect_url( $raw, $redirect, $from, $register ) {
1282
		return array( $raw, $redirect, $from, $register );
1283
	}
1284
1285
	/**
1286
	 * Disconnects from the Jetpack servers.
1287
	 * Forgets all connection details and tells the Jetpack servers to do the same.
1288
	 */
1289
	public function disconnect_site() {
1290
1291
	}
1292
1293
	/**
1294
	 * The Base64 Encoding of the SHA1 Hash of the Input.
1295
	 *
1296
	 * @param string $text The string to hash.
1297
	 * @return string
1298
	 */
1299
	public function sha1_base64( $text ) {
1300
		return base64_encode( sha1( $text, true ) ); // phpcs:ignore WordPress.PHP.DiscouragedPHPFunctions.obfuscation_base64_encode
1301
	}
1302
1303
	/**
1304
	 * This function mirrors Jetpack_Data::is_usable_domain() in the WPCOM codebase.
1305
	 *
1306
	 * @param string $domain The domain to check.
1307
	 *
1308
	 * @return bool|WP_Error
1309
	 */
1310
	public function is_usable_domain( $domain ) {
1311
1312
		// If it's empty, just fail out.
1313
		if ( ! $domain ) {
1314
			return new \WP_Error(
1315
				'fail_domain_empty',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'fail_domain_empty'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
1316
				/* translators: %1$s is a domain name. */
1317
				sprintf( __( 'Domain `%1$s` just failed is_usable_domain check as it is empty.', 'jetpack' ), $domain )
1318
			);
1319
		}
1320
1321
		/**
1322
		 * Skips the usuable domain check when connecting a site.
1323
		 *
1324
		 * Allows site administrators with domains that fail gethostname-based checks to pass the request to WP.com
1325
		 *
1326
		 * @since 4.1.0
1327
		 *
1328
		 * @param bool If the check should be skipped. Default false.
1329
		 */
1330
		if ( apply_filters( 'jetpack_skip_usuable_domain_check', false ) ) {
1331
			return true;
1332
		}
1333
1334
		// None of the explicit localhosts.
1335
		$forbidden_domains = array(
1336
			'wordpress.com',
1337
			'localhost',
1338
			'localhost.localdomain',
1339
			'127.0.0.1',
1340
			'local.wordpress.test',         // VVV pattern.
1341
			'local.wordpress-trunk.test',   // VVV pattern.
1342
			'src.wordpress-develop.test',   // VVV pattern.
1343
			'build.wordpress-develop.test', // VVV pattern.
1344
		);
1345 View Code Duplication
		if ( in_array( $domain, $forbidden_domains, true ) ) {
1346
			return new \WP_Error(
1347
				'fail_domain_forbidden',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'fail_domain_forbidden'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
1348
				sprintf(
1349
					/* translators: %1$s is a domain name. */
1350
					__(
1351
						'Domain `%1$s` just failed is_usable_domain check as it is in the forbidden array.',
1352
						'jetpack'
1353
					),
1354
					$domain
1355
				)
1356
			);
1357
		}
1358
1359
		// No .test or .local domains.
1360 View Code Duplication
		if ( preg_match( '#\.(test|local)$#i', $domain ) ) {
1361
			return new \WP_Error(
1362
				'fail_domain_tld',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'fail_domain_tld'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
1363
				sprintf(
1364
					/* translators: %1$s is a domain name. */
1365
					__(
1366
						'Domain `%1$s` just failed is_usable_domain check as it uses an invalid top level domain.',
1367
						'jetpack'
1368
					),
1369
					$domain
1370
				)
1371
			);
1372
		}
1373
1374
		// No WPCOM subdomains.
1375 View Code Duplication
		if ( preg_match( '#\.WordPress\.com$#i', $domain ) ) {
1376
			return new \WP_Error(
1377
				'fail_subdomain_wpcom',
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'fail_subdomain_wpcom'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
1378
				sprintf(
1379
					/* translators: %1$s is a domain name. */
1380
					__(
1381
						'Domain `%1$s` just failed is_usable_domain check as it is a subdomain of WordPress.com.',
1382
						'jetpack'
1383
					),
1384
					$domain
1385
				)
1386
			);
1387
		}
1388
1389
		// If PHP was compiled without support for the Filter module (very edge case).
1390
		if ( ! function_exists( 'filter_var' ) ) {
1391
			// Just pass back true for now, and let wpcom sort it out.
1392
			return true;
1393
		}
1394
1395
		return true;
1396
	}
1397
1398
	/**
1399
	 * Gets the requested token.
1400
	 *
1401
	 * Tokens are one of two types:
1402
	 * 1. Blog Tokens: These are the "main" tokens. Each site typically has one Blog Token,
1403
	 *    though some sites can have multiple "Special" Blog Tokens (see below). These tokens
1404
	 *    are not associated with a user account. They represent the site's connection with
1405
	 *    the Jetpack servers.
1406
	 * 2. User Tokens: These are "sub-"tokens. Each connected user account has one User Token.
1407
	 *
1408
	 * All tokens look like "{$token_key}.{$private}". $token_key is a public ID for the
1409
	 * token, and $private is a secret that should never be displayed anywhere or sent
1410
	 * over the network; it's used only for signing things.
1411
	 *
1412
	 * Blog Tokens can be "Normal" or "Special".
1413
	 * * Normal: The result of a normal connection flow. They look like
1414
	 *   "{$random_string_1}.{$random_string_2}"
1415
	 *   That is, $token_key and $private are both random strings.
1416
	 *   Sites only have one Normal Blog Token. Normal Tokens are found in either
1417
	 *   Jetpack_Options::get_option( 'blog_token' ) (usual) or the JETPACK_BLOG_TOKEN
1418
	 *   constant (rare).
1419
	 * * Special: A connection token for sites that have gone through an alternative
1420
	 *   connection flow. They look like:
1421
	 *   ";{$special_id}{$special_version};{$wpcom_blog_id};.{$random_string}"
1422
	 *   That is, $private is a random string and $token_key has a special structure with
1423
	 *   lots of semicolons.
1424
	 *   Most sites have zero Special Blog Tokens. Special tokens are only found in the
1425
	 *   JETPACK_BLOG_TOKEN constant.
1426
	 *
1427
	 * In particular, note that Normal Blog Tokens never start with ";" and that
1428
	 * Special Blog Tokens always do.
1429
	 *
1430
	 * When searching for a matching Blog Tokens, Blog Tokens are examined in the following
1431
	 * order:
1432
	 * 1. Defined Special Blog Tokens (via the JETPACK_BLOG_TOKEN constant)
1433
	 * 2. Stored Normal Tokens (via Jetpack_Options::get_option( 'blog_token' ))
1434
	 * 3. Defined Normal Tokens (via the JETPACK_BLOG_TOKEN constant)
1435
	 *
1436
	 * @param int|false    $user_id   false: Return the Blog Token. int: Return that user's User Token.
1437
	 * @param string|false $token_key If provided, check that the token matches the provided input.
1438
	 * @param bool|true    $suppress_errors If true, return a falsy value when the token isn't found; When false, return a descriptive WP_Error when the token isn't found.
1439
	 *
1440
	 * @return object|false
1441
	 */
1442
	public function get_access_token( $user_id = false, $token_key = false, $suppress_errors = true ) {
1443
		$possible_special_tokens = array();
1444
		$possible_normal_tokens  = array();
1445
		$user_tokens             = \Jetpack_Options::get_option( 'user_tokens' );
1446
1447
		if ( $user_id ) {
0 ignored issues
show
Bug Best Practice introduced by
The expression $user_id of type false|integer is loosely compared to true; this is ambiguous if the integer can be zero. You might want to explicitly use !== null instead.

In PHP, under loose comparison (like ==, or !=, or switch conditions), values of different types might be equal.

For integer values, zero is a special case, in particular the following results might be unexpected:

0   == false // true
0   == null  // true
123 == false // false
123 == null  // false

// It is often better to use strict comparison
0 === false // false
0 === null  // false
Loading history...
1448
			if ( ! $user_tokens ) {
1449
				return $suppress_errors ? false : new \WP_Error( 'no_user_tokens' );
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'no_user_tokens'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
1450
			}
1451
			if ( self::JETPACK_MASTER_USER === $user_id ) {
1452
				$user_id = \Jetpack_Options::get_option( 'master_user' );
1453
				if ( ! $user_id ) {
1454
					return $suppress_errors ? false : new \WP_Error( 'empty_master_user_option' );
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'empty_master_user_option'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
1455
				}
1456
			}
1457
			if ( ! isset( $user_tokens[ $user_id ] ) || ! $user_tokens[ $user_id ] ) {
1458
				return $suppress_errors ? false : new \WP_Error( 'no_token_for_user', sprintf( 'No token for user %d', $user_id ) );
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'no_token_for_user'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
1459
			}
1460
			$user_token_chunks = explode( '.', $user_tokens[ $user_id ] );
1461
			if ( empty( $user_token_chunks[1] ) || empty( $user_token_chunks[2] ) ) {
1462
				return $suppress_errors ? false : new \WP_Error( 'token_malformed', sprintf( 'Token for user %d is malformed', $user_id ) );
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'token_malformed'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
1463
			}
1464
			if ( $user_token_chunks[2] !== (string) $user_id ) {
1465
				return $suppress_errors ? false : new \WP_Error( 'user_id_mismatch', sprintf( 'Requesting user_id %d does not match token user_id %d', $user_id, $user_token_chunks[2] ) );
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'user_id_mismatch'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
1466
			}
1467
			$possible_normal_tokens[] = "{$user_token_chunks[0]}.{$user_token_chunks[1]}";
1468
		} else {
1469
			$stored_blog_token = \Jetpack_Options::get_option( 'blog_token' );
1470
			if ( $stored_blog_token ) {
1471
				$possible_normal_tokens[] = $stored_blog_token;
1472
			}
1473
1474
			$defined_tokens_string = Constants::get_constant( 'JETPACK_BLOG_TOKEN' );
1475
1476
			if ( $defined_tokens_string ) {
1477
				$defined_tokens = explode( ',', $defined_tokens_string );
1478
				foreach ( $defined_tokens as $defined_token ) {
1479
					if ( ';' === $defined_token[0] ) {
1480
						$possible_special_tokens[] = $defined_token;
1481
					} else {
1482
						$possible_normal_tokens[] = $defined_token;
1483
					}
1484
				}
1485
			}
1486
		}
1487
1488
		if ( self::MAGIC_NORMAL_TOKEN_KEY === $token_key ) {
1489
			$possible_tokens = $possible_normal_tokens;
1490
		} else {
1491
			$possible_tokens = array_merge( $possible_special_tokens, $possible_normal_tokens );
1492
		}
1493
1494
		if ( ! $possible_tokens ) {
0 ignored issues
show
Bug Best Practice introduced by
The expression $possible_tokens of type array is implicitly converted to a boolean; are you sure this is intended? If so, consider using empty($expr) instead to make it clear that you intend to check for an array without elements.

This check marks implicit conversions of arrays to boolean values in a comparison. While in PHP an empty array is considered to be equal (but not identical) to false, this is not always apparent.

Consider making the comparison explicit by using empty(..) or ! empty(...) instead.

Loading history...
1495
			return $suppress_errors ? false : new \WP_Error( 'no_possible_tokens' );
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'no_possible_tokens'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
1496
		}
1497
1498
		$valid_token = false;
1499
1500
		if ( false === $token_key ) {
1501
			// Use first token.
1502
			$valid_token = $possible_tokens[0];
1503
		} elseif ( self::MAGIC_NORMAL_TOKEN_KEY === $token_key ) {
1504
			// Use first normal token.
1505
			$valid_token = $possible_tokens[0]; // $possible_tokens only contains normal tokens because of earlier check.
1506
		} else {
1507
			// Use the token matching $token_key or false if none.
1508
			// Ensure we check the full key.
1509
			$token_check = rtrim( $token_key, '.' ) . '.';
1510
1511
			foreach ( $possible_tokens as $possible_token ) {
1512
				if ( hash_equals( substr( $possible_token, 0, strlen( $token_check ) ), $token_check ) ) {
1513
					$valid_token = $possible_token;
1514
					break;
1515
				}
1516
			}
1517
		}
1518
1519
		if ( ! $valid_token ) {
1520
			return $suppress_errors ? false : new \WP_Error( 'no_valid_token' );
0 ignored issues
show
Unused Code introduced by
The call to WP_Error::__construct() has too many arguments starting with 'no_valid_token'.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
1521
		}
1522
1523
		return (object) array(
1524
			'secret'           => $valid_token,
1525
			'external_user_id' => (int) $user_id,
1526
		);
1527
	}
1528
1529
	/**
1530
	 * In some setups, $HTTP_RAW_POST_DATA can be emptied during some IXR_Server paths
1531
	 * since it is passed by reference to various methods.
1532
	 * Capture it here so we can verify the signature later.
1533
	 *
1534
	 * @param Array $methods an array of available XMLRPC methods.
1535
	 * @return Array the same array, since this method doesn't add or remove anything.
1536
	 */
1537
	public function xmlrpc_methods( $methods ) {
1538
		$this->raw_post_data = $GLOBALS['HTTP_RAW_POST_DATA'];
1539
		return $methods;
1540
	}
1541
1542
	/**
1543
	 * Resets the raw post data parameter for testing purposes.
1544
	 */
1545
	public function reset_raw_post_data() {
1546
		$this->raw_post_data = null;
1547
	}
1548
1549
	/**
1550
	 * Registering an additional method.
1551
	 *
1552
	 * @param Array $methods an array of available XMLRPC methods.
1553
	 * @return Array the amended array in case the method is added.
1554
	 */
1555
	public function public_xmlrpc_methods( $methods ) {
1556
		if ( array_key_exists( 'wp.getOptions', $methods ) ) {
1557
			$methods['wp.getOptions'] = array( $this, 'jetpack_getOptions' );
1558
		}
1559
		return $methods;
1560
	}
1561
1562
	/**
1563
	 * Handles a getOptions XMLRPC method call.
1564
	 *
1565
	 * @param Array $args method call arguments.
1566
	 * @return an amended XMLRPC server options array.
1567
	 */
1568
	public function jetpack_getOptions( $args ) {
1569
		global $wp_xmlrpc_server;
1570
1571
		$wp_xmlrpc_server->escape( $args );
1572
1573
		$username = $args[1];
1574
		$password = $args[2];
1575
1576
		$user = $wp_xmlrpc_server->login( $username, $password );
1577
		if ( ! $user ) {
1578
			return $wp_xmlrpc_server->error;
1579
		}
1580
1581
		$options   = array();
1582
		$user_data = $this->get_connected_user_data();
1583
		if ( is_array( $user_data ) ) {
1584
			$options['jetpack_user_id']         = array(
1585
				'desc'     => __( 'The WP.com user ID of the connected user', 'jetpack' ),
1586
				'readonly' => true,
1587
				'value'    => $user_data['ID'],
1588
			);
1589
			$options['jetpack_user_login']      = array(
1590
				'desc'     => __( 'The WP.com username of the connected user', 'jetpack' ),
1591
				'readonly' => true,
1592
				'value'    => $user_data['login'],
1593
			);
1594
			$options['jetpack_user_email']      = array(
1595
				'desc'     => __( 'The WP.com user email of the connected user', 'jetpack' ),
1596
				'readonly' => true,
1597
				'value'    => $user_data['email'],
1598
			);
1599
			$options['jetpack_user_site_count'] = array(
1600
				'desc'     => __( 'The number of sites of the connected WP.com user', 'jetpack' ),
1601
				'readonly' => true,
1602
				'value'    => $user_data['site_count'],
1603
			);
1604
		}
1605
		$wp_xmlrpc_server->blog_options = array_merge( $wp_xmlrpc_server->blog_options, $options );
1606
		$args                           = stripslashes_deep( $args );
1607
		return $wp_xmlrpc_server->wp_getOptions( $args );
1608
	}
1609
1610
	/**
1611
	 * Adds Jetpack-specific options to the output of the XMLRPC options method.
1612
	 *
1613
	 * @param Array $options standard Core options.
1614
	 * @return Array amended options.
1615
	 */
1616
	public function xmlrpc_options( $options ) {
1617
		$jetpack_client_id = false;
1618
		if ( $this->is_active() ) {
1619
			$jetpack_client_id = \Jetpack_Options::get_option( 'id' );
1620
		}
1621
		$options['jetpack_version'] = array(
1622
			'desc'     => __( 'Jetpack Plugin Version', 'jetpack' ),
1623
			'readonly' => true,
1624
			'value'    => Constants::get_constant( 'JETPACK__VERSION' ),
1625
		);
1626
1627
		$options['jetpack_client_id'] = array(
1628
			'desc'     => __( 'The Client ID/WP.com Blog ID of this site', 'jetpack' ),
1629
			'readonly' => true,
1630
			'value'    => $jetpack_client_id,
1631
		);
1632
		return $options;
1633
	}
1634
1635
	/**
1636
	 * Resets the saved authentication state in between testing requests.
1637
	 */
1638
	public function reset_saved_auth_state() {
1639
		$this->xmlrpc_verification = null;
1640
	}
1641
1642
	/**
1643
	 * Sign a user role with the master access token.
1644
	 * If not specified, will default to the current user.
1645
	 *
1646
	 * @access public
1647
	 *
1648
	 * @param string $role    User role.
1649
	 * @param int    $user_id ID of the user.
0 ignored issues
show
Documentation introduced by
Should the type for parameter $user_id not be integer|null?

This check looks for @param annotations where the type inferred by our type inference engine differs from the declared type.

It makes a suggestion as to what type it considers more descriptive.

Most often this is a case of a parameter that can be null in addition to its declared types.

Loading history...
1650
	 * @return string Signed user role.
1651
	 */
1652
	public function sign_role( $role, $user_id = null ) {
1653
		if ( empty( $user_id ) ) {
1654
			$user_id = (int) get_current_user_id();
1655
		}
1656
1657
		if ( ! $user_id ) {
1658
			return false;
1659
		}
1660
1661
		$token = $this->get_access_token();
1662
		if ( ! $token || is_wp_error( $token ) ) {
1663
			return false;
1664
		}
1665
1666
		return $role . ':' . hash_hmac( 'md5', "{$role}|{$user_id}", $token->secret );
1667
	}
1668
}
1669