Completed
Push — add/missing-owner-heartbeat ( f3db20 )
by
unknown
06:15
created

Manager::is_missing_connection_owner()   A

Complexity

Conditions 2
Paths 2

Size

Total Lines 8

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
cc 2
nc 2
nop 0
dl 0
loc 8
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
	 * Checks to see if the connection owner of the site is missing.
487
	 *
488
	 * @return bool
489
	 */
490
	public function is_missing_connection_owner() {
491
		$connection_owner = $this->get_connection_owner_id();
492
		if ( ! get_user_by( 'id', $connection_owner ) ) {
493
			return true;
494
		}
495
496
		return false;
497
	}
498
499
	/**
500
	 * Returns true if the user with the specified identifier is connected to
501
	 * WordPress.com.
502
	 *
503
	 * @param Integer|Boolean $user_id the user identifier.
504
	 * @return Boolean is the user connected?
505
	 */
506
	public function is_user_connected( $user_id = false ) {
507
		$user_id = false === $user_id ? get_current_user_id() : absint( $user_id );
508
		if ( ! $user_id ) {
509
			return false;
510
		}
511
512
		return (bool) $this->get_access_token( $user_id );
513
	}
514
515
	/**
516
	 * Returns the local user ID of the connection owner.
517
	 *
518
	 * @return string|int Returns the ID of the connection owner or False if no connection owner found.
519
	 */
520 View Code Duplication
	public function get_connection_owner_id() {
521
		$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...
522
		$connection_owner = false;
523
		if ( $user_token && is_object( $user_token ) && isset( $user_token->external_user_id ) ) {
524
			$connection_owner = $user_token->external_user_id;
525
		}
526
527
		return $connection_owner;
528
	}
529
530
	/**
531
	 * Get the wpcom user data of the current|specified connected user.
532
	 *
533
	 * @todo Refactor to properly load the XMLRPC client independently.
534
	 *
535
	 * @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...
536
	 * @return Object the user object.
537
	 */
538 View Code Duplication
	public function get_connected_user_data( $user_id = null ) {
539
		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...
540
			$user_id = get_current_user_id();
541
		}
542
543
		$transient_key    = "jetpack_connected_user_data_$user_id";
544
		$cached_user_data = get_transient( $transient_key );
545
546
		if ( $cached_user_data ) {
547
			return $cached_user_data;
548
		}
549
550
		$xml = new \Jetpack_IXR_Client(
551
			array(
552
				'user_id' => $user_id,
553
			)
554
		);
555
		$xml->query( 'wpcom.getUser' );
556
		if ( ! $xml->isError() ) {
557
			$user_data = $xml->getResponse();
558
			set_transient( $transient_key, $xml->getResponse(), DAY_IN_SECONDS );
559
			return $user_data;
560
		}
561
562
		return false;
563
	}
564
565
	/**
566
	 * Returns true if the provided user is the Jetpack connection owner.
567
	 * If user ID is not specified, the current user will be used.
568
	 *
569
	 * @param Integer|Boolean $user_id the user identifier. False for current user.
570
	 * @return Boolean True the user the connection owner, false otherwise.
571
	 */
572 View Code Duplication
	public function is_connection_owner( $user_id = false ) {
573
		if ( ! $user_id ) {
574
			$user_id = get_current_user_id();
575
		}
576
577
		$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...
578
579
		return $user_token && is_object( $user_token ) && isset( $user_token->external_user_id ) && $user_id === $user_token->external_user_id;
580
	}
581
582
	/**
583
	 * Unlinks the current user from the linked WordPress.com user.
584
	 *
585
	 * @access public
586
	 * @static
587
	 *
588
	 * @todo Refactor to properly load the XMLRPC client independently.
589
	 *
590
	 * @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...
591
	 * @return Boolean Whether the disconnection of the user was successful.
592
	 */
593
	public static function disconnect_user( $user_id = null ) {
594
		$tokens = \Jetpack_Options::get_option( 'user_tokens' );
595
		if ( ! $tokens ) {
596
			return false;
597
		}
598
599
		$user_id = empty( $user_id ) ? get_current_user_id() : intval( $user_id );
600
601
		if ( \Jetpack_Options::get_option( 'master_user' ) === $user_id ) {
602
			return false;
603
		}
604
605
		if ( ! isset( $tokens[ $user_id ] ) ) {
606
			return false;
607
		}
608
609
		$xml = new \Jetpack_IXR_Client( compact( 'user_id' ) );
610
		$xml->query( 'jetpack.unlink_user', $user_id );
611
612
		unset( $tokens[ $user_id ] );
613
614
		\Jetpack_Options::update_option( 'user_tokens', $tokens );
615
616
		/**
617
		 * Fires after the current user has been unlinked from WordPress.com.
618
		 *
619
		 * @since 4.1.0
620
		 *
621
		 * @param int $user_id The current user's ID.
622
		 */
623
		do_action( 'jetpack_unlinked_user', $user_id );
624
625
		return true;
626
	}
627
628
	/**
629
	 * Returns the requested Jetpack API URL.
630
	 *
631
	 * @param String $relative_url the relative API path.
632
	 * @return String API URL.
633
	 */
634
	public function api_url( $relative_url ) {
635
		$api_base = Constants::get_constant( 'JETPACK__API_BASE' );
636
		$version  = Constants::get_constant( 'JETPACK__API_VERSION' );
637
638
		$api_base = $api_base ? $api_base : 'https://jetpack.wordpress.com/jetpack.';
639
		$version  = $version ? '/' . $version . '/' : '/1/';
640
641
		return rtrim( $api_base . $relative_url, '/\\' ) . $version;
642
	}
643
644
	/**
645
	 * Attempts Jetpack registration which sets up the site for connection. Should
646
	 * remain public because the call to action comes from the current site, not from
647
	 * WordPress.com.
648
	 *
649
	 * @param String $api_endpoint (optional) an API endpoint to use, defaults to 'register'.
650
	 * @return Integer zero on success, or a bitmask on failure.
651
	 */
652
	public function register( $api_endpoint = 'register' ) {
653
		add_action( 'pre_update_jetpack_option_register', array( '\\Jetpack_Options', 'delete_option' ) );
654
		$secrets = $this->generate_secrets( 'register', get_current_user_id(), 600 );
655
656
		if (
657
			empty( $secrets['secret_1'] ) ||
658
			empty( $secrets['secret_2'] ) ||
659
			empty( $secrets['exp'] )
660
		) {
661
			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...
662
		}
663
664
		// Better to try (and fail) to set a higher timeout than this system
665
		// supports than to have register fail for more users than it should.
666
		$timeout = $this->set_min_time_limit( 60 ) / 2;
667
668
		$gmt_offset = get_option( 'gmt_offset' );
669
		if ( ! $gmt_offset ) {
670
			$gmt_offset = 0;
671
		}
672
673
		$stats_options = get_option( 'stats_options' );
674
		$stats_id      = isset( $stats_options['blog_id'] )
675
			? $stats_options['blog_id']
676
			: null;
677
678
		/**
679
		 * Filters the request body for additional property addition.
680
		 *
681
		 * @since 7.7.0
682
		 *
683
		 * @param Array $post_data request data.
684
		 * @param Array $token_data token data.
685
		 */
686
		$body = apply_filters(
687
			'jetpack_register_request_body',
688
			array(
689
				'siteurl'         => site_url(),
690
				'home'            => home_url(),
691
				'gmt_offset'      => $gmt_offset,
692
				'timezone_string' => (string) get_option( 'timezone_string' ),
693
				'site_name'       => (string) get_option( 'blogname' ),
694
				'secret_1'        => $secrets['secret_1'],
695
				'secret_2'        => $secrets['secret_2'],
696
				'site_lang'       => get_locale(),
697
				'timeout'         => $timeout,
698
				'stats_id'        => $stats_id,
699
				'state'           => get_current_user_id(),
700
				'site_created'    => $this->get_assumed_site_creation_date(),
701
				'jetpack_version' => Constants::get_constant( 'JETPACK__VERSION' ),
702
			)
703
		);
704
705
		$args = array(
706
			'method'  => 'POST',
707
			'body'    => $body,
708
			'headers' => array(
709
				'Accept' => 'application/json',
710
			),
711
			'timeout' => $timeout,
712
		);
713
714
		$args['body'] = $this->apply_activation_source_to_args( $args['body'] );
715
716
		// TODO: fix URLs for bad hosts.
717
		$response = Client::_wp_remote_request(
718
			$this->api_url( $api_endpoint ),
719
			$args,
720
			true
721
		);
722
723
		// Make sure the response is valid and does not contain any Jetpack errors.
724
		$registration_details = $this->validate_remote_register_response( $response );
725
726
		if ( is_wp_error( $registration_details ) ) {
727
			return $registration_details;
728
		} elseif ( ! $registration_details ) {
729
			return new \WP_Error(
730
				'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...
731
				'Unknown error registering your Jetpack site.',
732
				wp_remote_retrieve_response_code( $response )
733
			);
734
		}
735
736
		if ( empty( $registration_details->jetpack_secret ) || ! is_string( $registration_details->jetpack_secret ) ) {
737
			return new \WP_Error(
738
				'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...
739
				'Unable to validate registration of your Jetpack site.',
740
				wp_remote_retrieve_response_code( $response )
741
			);
742
		}
743
744
		if ( isset( $registration_details->jetpack_public ) ) {
745
			$jetpack_public = (int) $registration_details->jetpack_public;
746
		} else {
747
			$jetpack_public = false;
748
		}
749
750
		\Jetpack_Options::update_options(
751
			array(
752
				'id'         => (int) $registration_details->jetpack_id,
753
				'blog_token' => (string) $registration_details->jetpack_secret,
754
				'public'     => $jetpack_public,
755
			)
756
		);
757
758
		/**
759
		 * Fires when a site is registered on WordPress.com.
760
		 *
761
		 * @since 3.7.0
762
		 *
763
		 * @param int $json->jetpack_id Jetpack Blog ID.
764
		 * @param string $json->jetpack_secret Jetpack Blog Token.
765
		 * @param int|bool $jetpack_public Is the site public.
766
		 */
767
		do_action(
768
			'jetpack_site_registered',
769
			$registration_details->jetpack_id,
770
			$registration_details->jetpack_secret,
771
			$jetpack_public
772
		);
773
774
		if ( isset( $registration_details->token ) ) {
775
			/**
776
			 * Fires when a user token is sent along with the registration data.
777
			 *
778
			 * @since 7.6.0
779
			 *
780
			 * @param object $token the administrator token for the newly registered site.
781
			 */
782
			do_action( 'jetpack_site_registered_user_token', $registration_details->token );
783
		}
784
785
		return true;
786
	}
787
788
	/**
789
	 * Takes the response from the Jetpack register new site endpoint and
790
	 * verifies it worked properly.
791
	 *
792
	 * @since 2.6
793
	 *
794
	 * @param Mixed $response the response object, or the error object.
795
	 * @return string|WP_Error A JSON object on success or Jetpack_Error on failures
796
	 **/
797
	protected function validate_remote_register_response( $response ) {
798
		if ( is_wp_error( $response ) ) {
799
			return new \WP_Error(
800
				'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...
801
				$response->get_error_message()
802
			);
803
		}
804
805
		$code   = wp_remote_retrieve_response_code( $response );
806
		$entity = wp_remote_retrieve_body( $response );
807
808
		if ( $entity ) {
809
			$registration_response = json_decode( $entity );
810
		} else {
811
			$registration_response = false;
812
		}
813
814
		$code_type = intval( $code / 100 );
815
		if ( 5 === $code_type ) {
816
			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...
817
		} elseif ( 408 === $code ) {
818
			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...
819
		} elseif ( ! empty( $registration_response->error ) ) {
820
			if (
821
				'xml_rpc-32700' === $registration_response->error
822
				&& ! function_exists( 'xml_parser_create' )
823
			) {
824
				$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' );
825
			} else {
826
				$error_description = isset( $registration_response->error_description )
827
					? (string) $registration_response->error_description
828
					: '';
829
			}
830
831
			return new \WP_Error(
832
				(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...
833
				$error_description,
834
				$code
835
			);
836
		} elseif ( 200 !== $code ) {
837
			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...
838
		}
839
840
		// Jetpack ID error block.
841
		if ( empty( $registration_response->jetpack_id ) ) {
842
			return new \WP_Error(
843
				'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...
844
				/* translators: %s is an error message string */
845
				sprintf( __( 'Error Details: Jetpack ID is empty. Do not publicly post this error message! %s', 'jetpack' ), $entity ),
846
				$entity
847
			);
848
		} elseif ( ! is_scalar( $registration_response->jetpack_id ) ) {
849
			return new \WP_Error(
850
				'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...
851
				/* translators: %s is an error message string */
852
				sprintf( __( 'Error Details: Jetpack ID is not a scalar. Do not publicly post this error message! %s', 'jetpack' ), $entity ),
853
				$entity
854
			);
855
		} elseif ( preg_match( '/[^0-9]/', $registration_response->jetpack_id ) ) {
856
			return new \WP_Error(
857
				'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...
858
				/* translators: %s is an error message string */
859
				sprintf( __( 'Error Details: Jetpack ID begins with a numeral. Do not publicly post this error message! %s', 'jetpack' ), $entity ),
860
				$entity
861
			);
862
		}
863
864
		return $registration_response;
865
	}
866
867
	/**
868
	 * Adds a used nonce to a list of known nonces.
869
	 *
870
	 * @param int    $timestamp the current request timestamp.
871
	 * @param string $nonce the nonce value.
872
	 * @return bool whether the nonce is unique or not.
873
	 */
874
	public function add_nonce( $timestamp, $nonce ) {
875
		global $wpdb;
876
		static $nonces_used_this_request = array();
877
878
		if ( isset( $nonces_used_this_request[ "$timestamp:$nonce" ] ) ) {
879
			return $nonces_used_this_request[ "$timestamp:$nonce" ];
880
		}
881
882
		// This should always have gone through Jetpack_Signature::sign_request() first to check $timestamp an $nonce.
883
		$timestamp = (int) $timestamp;
884
		$nonce     = esc_sql( $nonce );
885
886
		// Raw query so we can avoid races: add_option will also update.
887
		$show_errors = $wpdb->show_errors( false );
888
889
		$old_nonce = $wpdb->get_row(
890
			$wpdb->prepare( "SELECT * FROM `$wpdb->options` WHERE option_name = %s", "jetpack_nonce_{$timestamp}_{$nonce}" )
891
		);
892
893
		if ( is_null( $old_nonce ) ) {
894
			$return = $wpdb->query(
895
				$wpdb->prepare(
896
					"INSERT INTO `$wpdb->options` (`option_name`, `option_value`, `autoload`) VALUES (%s, %s, %s)",
897
					"jetpack_nonce_{$timestamp}_{$nonce}",
898
					time(),
899
					'no'
900
				)
901
			);
902
		} else {
903
			$return = false;
904
		}
905
906
		$wpdb->show_errors( $show_errors );
907
908
		$nonces_used_this_request[ "$timestamp:$nonce" ] = $return;
909
910
		return $return;
911
	}
912
913
	/**
914
	 * Cleans nonces that were saved when calling ::add_nonce.
915
	 *
916
	 * @todo Properly prepare the query before executing it.
917
	 *
918
	 * @param bool $all whether to clean even non-expired nonces.
919
	 */
920
	public function clean_nonces( $all = false ) {
921
		global $wpdb;
922
923
		$sql      = "DELETE FROM `$wpdb->options` WHERE `option_name` LIKE %s";
924
		$sql_args = array( $wpdb->esc_like( 'jetpack_nonce_' ) . '%' );
925
926
		if ( true !== $all ) {
927
			$sql       .= ' AND CAST( `option_value` AS UNSIGNED ) < %d';
928
			$sql_args[] = time() - 3600;
929
		}
930
931
		$sql .= ' ORDER BY `option_id` LIMIT 100';
932
933
		$sql = $wpdb->prepare( $sql, $sql_args ); // phpcs:ignore WordPress.DB.PreparedSQL.NotPrepared
934
935
		for ( $i = 0; $i < 1000; $i++ ) {
936
			if ( ! $wpdb->query( $sql ) ) { // phpcs:ignore WordPress.DB.PreparedSQL.NotPrepared
937
				break;
938
			}
939
		}
940
	}
941
942
	/**
943
	 * Builds the timeout limit for queries talking with the wpcom servers.
944
	 *
945
	 * Based on local php max_execution_time in php.ini
946
	 *
947
	 * @since 5.4
948
	 * @return int
949
	 **/
950
	public function get_max_execution_time() {
951
		$timeout = (int) ini_get( 'max_execution_time' );
952
953
		// Ensure exec time set in php.ini.
954
		if ( ! $timeout ) {
955
			$timeout = 30;
956
		}
957
		return $timeout;
958
	}
959
960
	/**
961
	 * Sets a minimum request timeout, and returns the current timeout
962
	 *
963
	 * @since 5.4
964
	 * @param Integer $min_timeout the minimum timeout value.
965
	 **/
966 View Code Duplication
	public function set_min_time_limit( $min_timeout ) {
967
		$timeout = $this->get_max_execution_time();
968
		if ( $timeout < $min_timeout ) {
969
			$timeout = $min_timeout;
970
			set_time_limit( $timeout );
971
		}
972
		return $timeout;
973
	}
974
975
	/**
976
	 * Get our assumed site creation date.
977
	 * Calculated based on the earlier date of either:
978
	 * - Earliest admin user registration date.
979
	 * - Earliest date of post of any post type.
980
	 *
981
	 * @since 7.2.0
982
	 *
983
	 * @return string Assumed site creation date and time.
984
	 */
985 View Code Duplication
	public function get_assumed_site_creation_date() {
986
		$earliest_registered_users  = get_users(
987
			array(
988
				'role'    => 'administrator',
989
				'orderby' => 'user_registered',
990
				'order'   => 'ASC',
991
				'fields'  => array( 'user_registered' ),
992
				'number'  => 1,
993
			)
994
		);
995
		$earliest_registration_date = $earliest_registered_users[0]->user_registered;
996
997
		$earliest_posts = get_posts(
998
			array(
999
				'posts_per_page' => 1,
1000
				'post_type'      => 'any',
1001
				'post_status'    => 'any',
1002
				'orderby'        => 'date',
1003
				'order'          => 'ASC',
1004
			)
1005
		);
1006
1007
		// If there are no posts at all, we'll count only on user registration date.
1008
		if ( $earliest_posts ) {
1009
			$earliest_post_date = $earliest_posts[0]->post_date;
1010
		} else {
1011
			$earliest_post_date = PHP_INT_MAX;
1012
		}
1013
1014
		return min( $earliest_registration_date, $earliest_post_date );
1015
	}
1016
1017
	/**
1018
	 * Adds the activation source string as a parameter to passed arguments.
1019
	 *
1020
	 * @param Array $args arguments that need to have the source added.
1021
	 * @return Array $amended arguments.
1022
	 */
1023 View Code Duplication
	public static function apply_activation_source_to_args( $args ) {
1024
		list( $activation_source_name, $activation_source_keyword ) = get_option( 'jetpack_activation_source' );
1025
1026
		if ( $activation_source_name ) {
1027
			$args['_as'] = urlencode( $activation_source_name );
1028
		}
1029
1030
		if ( $activation_source_keyword ) {
1031
			$args['_ak'] = urlencode( $activation_source_keyword );
1032
		}
1033
1034
		return $args;
1035
	}
1036
1037
	/**
1038
	 * Returns the callable that would be used to generate secrets.
1039
	 *
1040
	 * @return Callable a function that returns a secure string to be used as a secret.
1041
	 */
1042
	protected function get_secret_callable() {
1043
		if ( ! isset( $this->secret_callable ) ) {
1044
			/**
1045
			 * Allows modification of the callable that is used to generate connection secrets.
1046
			 *
1047
			 * @param Callable a function or method that returns a secret string.
1048
			 */
1049
			$this->secret_callable = apply_filters( 'jetpack_connection_secret_generator', 'wp_generate_password' );
1050
		}
1051
1052
		return $this->secret_callable;
1053
	}
1054
1055
	/**
1056
	 * Generates two secret tokens and the end of life timestamp for them.
1057
	 *
1058
	 * @param String  $action  The action name.
1059
	 * @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...
1060
	 * @param Integer $exp     Expiration time in seconds.
1061
	 */
1062
	public function generate_secrets( $action, $user_id = false, $exp = 600 ) {
1063
		$callable = $this->get_secret_callable();
1064
1065
		$secrets = \Jetpack_Options::get_raw_option(
1066
			self::SECRETS_OPTION_NAME,
1067
			array()
1068
		);
1069
1070
		$secret_name = 'jetpack_' . $action . '_' . $user_id;
1071
1072
		if (
1073
			isset( $secrets[ $secret_name ] ) &&
1074
			$secrets[ $secret_name ]['exp'] > time()
1075
		) {
1076
			return $secrets[ $secret_name ];
1077
		}
1078
1079
		$secret_value = array(
1080
			'secret_1' => call_user_func( $callable ),
1081
			'secret_2' => call_user_func( $callable ),
1082
			'exp'      => time() + $exp,
1083
		);
1084
1085
		$secrets[ $secret_name ] = $secret_value;
1086
1087
		\Jetpack_Options::update_raw_option( self::SECRETS_OPTION_NAME, $secrets );
1088
		return $secrets[ $secret_name ];
1089
	}
1090
1091
	/**
1092
	 * Returns two secret tokens and the end of life timestamp for them.
1093
	 *
1094
	 * @param String  $action  The action name.
1095
	 * @param Integer $user_id The user identifier.
1096
	 * @return string|array an array of secrets or an error string.
1097
	 */
1098
	public function get_secrets( $action, $user_id ) {
1099
		$secret_name = 'jetpack_' . $action . '_' . $user_id;
1100
		$secrets     = \Jetpack_Options::get_raw_option(
1101
			self::SECRETS_OPTION_NAME,
1102
			array()
1103
		);
1104
1105
		if ( ! isset( $secrets[ $secret_name ] ) ) {
1106
			return self::SECRETS_MISSING;
1107
		}
1108
1109
		if ( $secrets[ $secret_name ]['exp'] < time() ) {
1110
			$this->delete_secrets( $action, $user_id );
1111
			return self::SECRETS_EXPIRED;
1112
		}
1113
1114
		return $secrets[ $secret_name ];
1115
	}
1116
1117
	/**
1118
	 * Deletes secret tokens in case they, for example, have expired.
1119
	 *
1120
	 * @param String  $action  The action name.
1121
	 * @param Integer $user_id The user identifier.
1122
	 */
1123
	public function delete_secrets( $action, $user_id ) {
1124
		$secret_name = 'jetpack_' . $action . '_' . $user_id;
1125
		$secrets     = \Jetpack_Options::get_raw_option(
1126
			self::SECRETS_OPTION_NAME,
1127
			array()
1128
		);
1129
		if ( isset( $secrets[ $secret_name ] ) ) {
1130
			unset( $secrets[ $secret_name ] );
1131
			\Jetpack_Options::update_raw_option( self::SECRETS_OPTION_NAME, $secrets );
1132
		}
1133
	}
1134
1135
	/**
1136
	 * Responds to a WordPress.com call to register the current site.
1137
	 * Should be changed to protected.
1138
	 *
1139
	 * @param array $registration_data Array of [ secret_1, user_id ].
1140
	 */
1141
	public function handle_registration( array $registration_data ) {
1142
		list( $registration_secret_1, $registration_user_id ) = $registration_data;
1143
		if ( empty( $registration_user_id ) ) {
1144
			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...
1145
		}
1146
1147
		return $this->verify_secrets( 'register', $registration_secret_1, (int) $registration_user_id );
1148
	}
1149
1150
	/**
1151
	 * Verify a Previously Generated Secret.
1152
	 *
1153
	 * @param string $action   The type of secret to verify.
1154
	 * @param string $secret_1 The secret string to compare to what is stored.
1155
	 * @param int    $user_id  The user ID of the owner of the secret.
1156
	 */
1157
	protected function verify_secrets( $action, $secret_1, $user_id ) {
1158
		$allowed_actions = array( 'register', 'authorize', 'publicize' );
1159
		if ( ! in_array( $action, $allowed_actions, true ) ) {
1160
			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...
1161
		}
1162
1163
		$user = get_user_by( 'id', $user_id );
1164
1165
		/**
1166
		 * We've begun verifying the previously generated secret.
1167
		 *
1168
		 * @since 7.5.0
1169
		 *
1170
		 * @param string   $action The type of secret to verify.
1171
		 * @param \WP_User $user The user object.
1172
		 */
1173
		do_action( 'jetpack_verify_secrets_begin', $action, $user );
1174
1175
		$return_error = function( \WP_Error $error ) use ( $action, $user ) {
1176
			/**
1177
			 * Verifying of the previously generated secret has failed.
1178
			 *
1179
			 * @since 7.5.0
1180
			 *
1181
			 * @param string    $action  The type of secret to verify.
1182
			 * @param \WP_User  $user The user object.
1183
			 * @param \WP_Error $error The error object.
1184
			 */
1185
			do_action( 'jetpack_verify_secrets_fail', $action, $user, $error );
1186
1187
			return $error;
1188
		};
1189
1190
		$stored_secrets = $this->get_secrets( $action, $user_id );
1191
		$this->delete_secrets( $action, $user_id );
1192
1193
		if ( empty( $secret_1 ) ) {
1194
			return $return_error(
1195
				new \WP_Error(
1196
					'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...
1197
					/* translators: "%s" is the name of a paramter. It can be either "secret_1" or "state". */
1198
					sprintf( __( 'The required "%s" parameter is missing.', 'jetpack' ), 'secret_1' ),
1199
					400
1200
				)
1201
			);
1202
		} elseif ( ! is_string( $secret_1 ) ) {
1203
			return $return_error(
1204
				new \WP_Error(
1205
					'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...
1206
					/* translators: "%s" is the name of a paramter. It can be either "secret_1" or "state". */
1207
					sprintf( __( 'The required "%s" parameter is malformed.', 'jetpack' ), 'secret_1' ),
1208
					400
1209
				)
1210
			);
1211
		} elseif ( empty( $user_id ) ) {
1212
			// $user_id is passed around during registration as "state".
1213
			return $return_error(
1214
				new \WP_Error(
1215
					'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...
1216
					/* translators: "%s" is the name of a paramter. It can be either "secret_1" or "state". */
1217
					sprintf( __( 'The required "%s" parameter is missing.', 'jetpack' ), 'state' ),
1218
					400
1219
				)
1220
			);
1221
		} elseif ( ! ctype_digit( (string) $user_id ) ) {
1222
			return $return_error(
1223
				new \WP_Error(
1224
					'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...
1225
					/* translators: "%s" is the name of a paramter. It can be either "secret_1" or "state". */
1226
					sprintf( __( 'The required "%s" parameter is malformed.', 'jetpack' ), 'state' ),
1227
					400
1228
				)
1229
			);
1230
		}
1231
1232
		if ( self::SECRETS_MISSING === $stored_secrets ) {
1233
			return $return_error(
1234
				new \WP_Error(
1235
					'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...
1236
					__( 'Verification secrets not found', 'jetpack' ),
1237
					400
1238
				)
1239
			);
1240
		} elseif ( self::SECRETS_EXPIRED === $stored_secrets ) {
1241
			return $return_error(
1242
				new \WP_Error(
1243
					'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...
1244
					__( 'Verification took too long', 'jetpack' ),
1245
					400
1246
				)
1247
			);
1248
		} elseif ( ! $stored_secrets ) {
1249
			return $return_error(
1250
				new \WP_Error(
1251
					'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...
1252
					__( 'Verification secrets are empty', 'jetpack' ),
1253
					400
1254
				)
1255
			);
1256
		} elseif ( is_wp_error( $stored_secrets ) ) {
1257
			$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...
1258
			return $return_error( $stored_secrets );
1259
		} elseif ( empty( $stored_secrets['secret_1'] ) || empty( $stored_secrets['secret_2'] ) || empty( $stored_secrets['exp'] ) ) {
1260
			return $return_error(
1261
				new \WP_Error(
1262
					'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...
1263
					__( 'Verification secrets are incomplete', 'jetpack' ),
1264
					400
1265
				)
1266
			);
1267
		} elseif ( ! hash_equals( $secret_1, $stored_secrets['secret_1'] ) ) {
1268
			return $return_error(
1269
				new \WP_Error(
1270
					'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...
1271
					__( 'Secret mismatch', 'jetpack' ),
1272
					400
1273
				)
1274
			);
1275
		}
1276
1277
		/**
1278
		 * We've succeeded at verifying the previously generated secret.
1279
		 *
1280
		 * @since 7.5.0
1281
		 *
1282
		 * @param string   $action The type of secret to verify.
1283
		 * @param \WP_User $user The user object.
1284
		 */
1285
		do_action( 'jetpack_verify_secrets_success', $action, $user );
1286
1287
		return $stored_secrets['secret_2'];
1288
	}
1289
1290
	/**
1291
	 * Responds to a WordPress.com call to authorize the current user.
1292
	 * Should be changed to protected.
1293
	 */
1294
	public function handle_authorization() {
1295
1296
	}
1297
1298
	/**
1299
	 * Builds a URL to the Jetpack connection auth page.
1300
	 * This needs rethinking.
1301
	 *
1302
	 * @param bool        $raw If true, URL will not be escaped.
1303
	 * @param bool|string $redirect If true, will redirect back to Jetpack wp-admin landing page after connection.
1304
	 *                              If string, will be a custom redirect.
1305
	 * @param bool|string $from If not false, adds 'from=$from' param to the connect URL.
1306
	 * @param bool        $register If true, will generate a register URL regardless of the existing token, since 4.9.0.
1307
	 *
1308
	 * @return string Connect URL
1309
	 */
1310
	public function build_connect_url( $raw, $redirect, $from, $register ) {
1311
		return array( $raw, $redirect, $from, $register );
1312
	}
1313
1314
	/**
1315
	 * Disconnects from the Jetpack servers.
1316
	 * Forgets all connection details and tells the Jetpack servers to do the same.
1317
	 */
1318
	public function disconnect_site() {
1319
1320
	}
1321
1322
	/**
1323
	 * The Base64 Encoding of the SHA1 Hash of the Input.
1324
	 *
1325
	 * @param string $text The string to hash.
1326
	 * @return string
1327
	 */
1328
	public function sha1_base64( $text ) {
1329
		return base64_encode( sha1( $text, true ) ); // phpcs:ignore WordPress.PHP.DiscouragedPHPFunctions.obfuscation_base64_encode
1330
	}
1331
1332
	/**
1333
	 * This function mirrors Jetpack_Data::is_usable_domain() in the WPCOM codebase.
1334
	 *
1335
	 * @param string $domain The domain to check.
1336
	 *
1337
	 * @return bool|WP_Error
1338
	 */
1339
	public function is_usable_domain( $domain ) {
1340
1341
		// If it's empty, just fail out.
1342
		if ( ! $domain ) {
1343
			return new \WP_Error(
1344
				'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...
1345
				/* translators: %1$s is a domain name. */
1346
				sprintf( __( 'Domain `%1$s` just failed is_usable_domain check as it is empty.', 'jetpack' ), $domain )
1347
			);
1348
		}
1349
1350
		/**
1351
		 * Skips the usuable domain check when connecting a site.
1352
		 *
1353
		 * Allows site administrators with domains that fail gethostname-based checks to pass the request to WP.com
1354
		 *
1355
		 * @since 4.1.0
1356
		 *
1357
		 * @param bool If the check should be skipped. Default false.
1358
		 */
1359
		if ( apply_filters( 'jetpack_skip_usuable_domain_check', false ) ) {
1360
			return true;
1361
		}
1362
1363
		// None of the explicit localhosts.
1364
		$forbidden_domains = array(
1365
			'wordpress.com',
1366
			'localhost',
1367
			'localhost.localdomain',
1368
			'127.0.0.1',
1369
			'local.wordpress.test',         // VVV pattern.
1370
			'local.wordpress-trunk.test',   // VVV pattern.
1371
			'src.wordpress-develop.test',   // VVV pattern.
1372
			'build.wordpress-develop.test', // VVV pattern.
1373
		);
1374 View Code Duplication
		if ( in_array( $domain, $forbidden_domains, true ) ) {
1375
			return new \WP_Error(
1376
				'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...
1377
				sprintf(
1378
					/* translators: %1$s is a domain name. */
1379
					__(
1380
						'Domain `%1$s` just failed is_usable_domain check as it is in the forbidden array.',
1381
						'jetpack'
1382
					),
1383
					$domain
1384
				)
1385
			);
1386
		}
1387
1388
		// No .test or .local domains.
1389 View Code Duplication
		if ( preg_match( '#\.(test|local)$#i', $domain ) ) {
1390
			return new \WP_Error(
1391
				'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...
1392
				sprintf(
1393
					/* translators: %1$s is a domain name. */
1394
					__(
1395
						'Domain `%1$s` just failed is_usable_domain check as it uses an invalid top level domain.',
1396
						'jetpack'
1397
					),
1398
					$domain
1399
				)
1400
			);
1401
		}
1402
1403
		// No WPCOM subdomains.
1404 View Code Duplication
		if ( preg_match( '#\.WordPress\.com$#i', $domain ) ) {
1405
			return new \WP_Error(
1406
				'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...
1407
				sprintf(
1408
					/* translators: %1$s is a domain name. */
1409
					__(
1410
						'Domain `%1$s` just failed is_usable_domain check as it is a subdomain of WordPress.com.',
1411
						'jetpack'
1412
					),
1413
					$domain
1414
				)
1415
			);
1416
		}
1417
1418
		// If PHP was compiled without support for the Filter module (very edge case).
1419
		if ( ! function_exists( 'filter_var' ) ) {
1420
			// Just pass back true for now, and let wpcom sort it out.
1421
			return true;
1422
		}
1423
1424
		return true;
1425
	}
1426
1427
	/**
1428
	 * Gets the requested token.
1429
	 *
1430
	 * Tokens are one of two types:
1431
	 * 1. Blog Tokens: These are the "main" tokens. Each site typically has one Blog Token,
1432
	 *    though some sites can have multiple "Special" Blog Tokens (see below). These tokens
1433
	 *    are not associated with a user account. They represent the site's connection with
1434
	 *    the Jetpack servers.
1435
	 * 2. User Tokens: These are "sub-"tokens. Each connected user account has one User Token.
1436
	 *
1437
	 * All tokens look like "{$token_key}.{$private}". $token_key is a public ID for the
1438
	 * token, and $private is a secret that should never be displayed anywhere or sent
1439
	 * over the network; it's used only for signing things.
1440
	 *
1441
	 * Blog Tokens can be "Normal" or "Special".
1442
	 * * Normal: The result of a normal connection flow. They look like
1443
	 *   "{$random_string_1}.{$random_string_2}"
1444
	 *   That is, $token_key and $private are both random strings.
1445
	 *   Sites only have one Normal Blog Token. Normal Tokens are found in either
1446
	 *   Jetpack_Options::get_option( 'blog_token' ) (usual) or the JETPACK_BLOG_TOKEN
1447
	 *   constant (rare).
1448
	 * * Special: A connection token for sites that have gone through an alternative
1449
	 *   connection flow. They look like:
1450
	 *   ";{$special_id}{$special_version};{$wpcom_blog_id};.{$random_string}"
1451
	 *   That is, $private is a random string and $token_key has a special structure with
1452
	 *   lots of semicolons.
1453
	 *   Most sites have zero Special Blog Tokens. Special tokens are only found in the
1454
	 *   JETPACK_BLOG_TOKEN constant.
1455
	 *
1456
	 * In particular, note that Normal Blog Tokens never start with ";" and that
1457
	 * Special Blog Tokens always do.
1458
	 *
1459
	 * When searching for a matching Blog Tokens, Blog Tokens are examined in the following
1460
	 * order:
1461
	 * 1. Defined Special Blog Tokens (via the JETPACK_BLOG_TOKEN constant)
1462
	 * 2. Stored Normal Tokens (via Jetpack_Options::get_option( 'blog_token' ))
1463
	 * 3. Defined Normal Tokens (via the JETPACK_BLOG_TOKEN constant)
1464
	 *
1465
	 * @param int|false    $user_id   false: Return the Blog Token. int: Return that user's User Token.
1466
	 * @param string|false $token_key If provided, check that the token matches the provided input.
1467
	 * @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.
1468
	 *
1469
	 * @return object|false
1470
	 */
1471
	public function get_access_token( $user_id = false, $token_key = false, $suppress_errors = true ) {
1472
		$possible_special_tokens = array();
1473
		$possible_normal_tokens  = array();
1474
		$user_tokens             = \Jetpack_Options::get_option( 'user_tokens' );
1475
1476
		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...
1477
			if ( ! $user_tokens ) {
1478
				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...
1479
			}
1480
			if ( self::JETPACK_MASTER_USER === $user_id ) {
1481
				$user_id = \Jetpack_Options::get_option( 'master_user' );
1482
				if ( ! $user_id ) {
1483
					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...
1484
				}
1485
			}
1486
			if ( ! isset( $user_tokens[ $user_id ] ) || ! $user_tokens[ $user_id ] ) {
1487
				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...
1488
			}
1489
			$user_token_chunks = explode( '.', $user_tokens[ $user_id ] );
1490
			if ( empty( $user_token_chunks[1] ) || empty( $user_token_chunks[2] ) ) {
1491
				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...
1492
			}
1493
			if ( $user_token_chunks[2] !== (string) $user_id ) {
1494
				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...
1495
			}
1496
			$possible_normal_tokens[] = "{$user_token_chunks[0]}.{$user_token_chunks[1]}";
1497
		} else {
1498
			$stored_blog_token = \Jetpack_Options::get_option( 'blog_token' );
1499
			if ( $stored_blog_token ) {
1500
				$possible_normal_tokens[] = $stored_blog_token;
1501
			}
1502
1503
			$defined_tokens_string = Constants::get_constant( 'JETPACK_BLOG_TOKEN' );
1504
1505
			if ( $defined_tokens_string ) {
1506
				$defined_tokens = explode( ',', $defined_tokens_string );
1507
				foreach ( $defined_tokens as $defined_token ) {
1508
					if ( ';' === $defined_token[0] ) {
1509
						$possible_special_tokens[] = $defined_token;
1510
					} else {
1511
						$possible_normal_tokens[] = $defined_token;
1512
					}
1513
				}
1514
			}
1515
		}
1516
1517
		if ( self::MAGIC_NORMAL_TOKEN_KEY === $token_key ) {
1518
			$possible_tokens = $possible_normal_tokens;
1519
		} else {
1520
			$possible_tokens = array_merge( $possible_special_tokens, $possible_normal_tokens );
1521
		}
1522
1523
		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...
1524
			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...
1525
		}
1526
1527
		$valid_token = false;
1528
1529
		if ( false === $token_key ) {
1530
			// Use first token.
1531
			$valid_token = $possible_tokens[0];
1532
		} elseif ( self::MAGIC_NORMAL_TOKEN_KEY === $token_key ) {
1533
			// Use first normal token.
1534
			$valid_token = $possible_tokens[0]; // $possible_tokens only contains normal tokens because of earlier check.
1535
		} else {
1536
			// Use the token matching $token_key or false if none.
1537
			// Ensure we check the full key.
1538
			$token_check = rtrim( $token_key, '.' ) . '.';
1539
1540
			foreach ( $possible_tokens as $possible_token ) {
1541
				if ( hash_equals( substr( $possible_token, 0, strlen( $token_check ) ), $token_check ) ) {
1542
					$valid_token = $possible_token;
1543
					break;
1544
				}
1545
			}
1546
		}
1547
1548
		if ( ! $valid_token ) {
1549
			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...
1550
		}
1551
1552
		return (object) array(
1553
			'secret'           => $valid_token,
1554
			'external_user_id' => (int) $user_id,
1555
		);
1556
	}
1557
1558
	/**
1559
	 * In some setups, $HTTP_RAW_POST_DATA can be emptied during some IXR_Server paths
1560
	 * since it is passed by reference to various methods.
1561
	 * Capture it here so we can verify the signature later.
1562
	 *
1563
	 * @param Array $methods an array of available XMLRPC methods.
1564
	 * @return Array the same array, since this method doesn't add or remove anything.
1565
	 */
1566
	public function xmlrpc_methods( $methods ) {
1567
		$this->raw_post_data = $GLOBALS['HTTP_RAW_POST_DATA'];
1568
		return $methods;
1569
	}
1570
1571
	/**
1572
	 * Resets the raw post data parameter for testing purposes.
1573
	 */
1574
	public function reset_raw_post_data() {
1575
		$this->raw_post_data = null;
1576
	}
1577
1578
	/**
1579
	 * Registering an additional method.
1580
	 *
1581
	 * @param Array $methods an array of available XMLRPC methods.
1582
	 * @return Array the amended array in case the method is added.
1583
	 */
1584
	public function public_xmlrpc_methods( $methods ) {
1585
		if ( array_key_exists( 'wp.getOptions', $methods ) ) {
1586
			$methods['wp.getOptions'] = array( $this, 'jetpack_getOptions' );
1587
		}
1588
		return $methods;
1589
	}
1590
1591
	/**
1592
	 * Handles a getOptions XMLRPC method call.
1593
	 *
1594
	 * @param Array $args method call arguments.
1595
	 * @return an amended XMLRPC server options array.
1596
	 */
1597
	public function jetpack_getOptions( $args ) {
1598
		global $wp_xmlrpc_server;
1599
1600
		$wp_xmlrpc_server->escape( $args );
1601
1602
		$username = $args[1];
1603
		$password = $args[2];
1604
1605
		$user = $wp_xmlrpc_server->login( $username, $password );
1606
		if ( ! $user ) {
1607
			return $wp_xmlrpc_server->error;
1608
		}
1609
1610
		$options   = array();
1611
		$user_data = $this->get_connected_user_data();
1612
		if ( is_array( $user_data ) ) {
1613
			$options['jetpack_user_id']         = array(
1614
				'desc'     => __( 'The WP.com user ID of the connected user', 'jetpack' ),
1615
				'readonly' => true,
1616
				'value'    => $user_data['ID'],
1617
			);
1618
			$options['jetpack_user_login']      = array(
1619
				'desc'     => __( 'The WP.com username of the connected user', 'jetpack' ),
1620
				'readonly' => true,
1621
				'value'    => $user_data['login'],
1622
			);
1623
			$options['jetpack_user_email']      = array(
1624
				'desc'     => __( 'The WP.com user email of the connected user', 'jetpack' ),
1625
				'readonly' => true,
1626
				'value'    => $user_data['email'],
1627
			);
1628
			$options['jetpack_user_site_count'] = array(
1629
				'desc'     => __( 'The number of sites of the connected WP.com user', 'jetpack' ),
1630
				'readonly' => true,
1631
				'value'    => $user_data['site_count'],
1632
			);
1633
		}
1634
		$wp_xmlrpc_server->blog_options = array_merge( $wp_xmlrpc_server->blog_options, $options );
1635
		$args                           = stripslashes_deep( $args );
1636
		return $wp_xmlrpc_server->wp_getOptions( $args );
1637
	}
1638
1639
	/**
1640
	 * Adds Jetpack-specific options to the output of the XMLRPC options method.
1641
	 *
1642
	 * @param Array $options standard Core options.
1643
	 * @return Array amended options.
1644
	 */
1645
	public function xmlrpc_options( $options ) {
1646
		$jetpack_client_id = false;
1647
		if ( $this->is_active() ) {
1648
			$jetpack_client_id = \Jetpack_Options::get_option( 'id' );
1649
		}
1650
		$options['jetpack_version'] = array(
1651
			'desc'     => __( 'Jetpack Plugin Version', 'jetpack' ),
1652
			'readonly' => true,
1653
			'value'    => Constants::get_constant( 'JETPACK__VERSION' ),
1654
		);
1655
1656
		$options['jetpack_client_id'] = array(
1657
			'desc'     => __( 'The Client ID/WP.com Blog ID of this site', 'jetpack' ),
1658
			'readonly' => true,
1659
			'value'    => $jetpack_client_id,
1660
		);
1661
		return $options;
1662
	}
1663
1664
	/**
1665
	 * Resets the saved authentication state in between testing requests.
1666
	 */
1667
	public function reset_saved_auth_state() {
1668
		$this->xmlrpc_verification = null;
1669
	}
1670
1671
	/**
1672
	 * Sign a user role with the master access token.
1673
	 * If not specified, will default to the current user.
1674
	 *
1675
	 * @access public
1676
	 *
1677
	 * @param string $role    User role.
1678
	 * @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...
1679
	 * @return string Signed user role.
1680
	 */
1681
	public function sign_role( $role, $user_id = null ) {
1682
		if ( empty( $user_id ) ) {
1683
			$user_id = (int) get_current_user_id();
1684
		}
1685
1686
		if ( ! $user_id ) {
1687
			return false;
1688
		}
1689
1690
		$token = $this->get_access_token();
1691
		if ( ! $token || is_wp_error( $token ) ) {
1692
			return false;
1693
		}
1694
1695
		return $role . ':' . hash_hmac( 'md5', "{$role}|{$user_id}", $token->secret );
1696
	}
1697
}
1698