Completed
Push — remove/connection-manager-unne... ( d4946e )
by Marin
21:05 queued 13:19
created

Manager::api_url()   A

Complexity

Conditions 3
Paths 4

Size

Total Lines 9

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
cc 3
nc 4
nop 1
dl 0
loc 9
rs 9.9666
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
54
		$is_jetpack_xmlrpc_request = $this->setup_xmlrpc_handlers(
55
			$_GET,
56
			$this->is_active(),
57
			$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...
58
		);
59
60
		// All the XMLRPC functionality has been moved into setup_xmlrpc_handlers.
61
		if (
62
			! $is_jetpack_xmlrpc_request
63
			&& is_admin()
64
			&& isset( $_POST['action'] ) // phpcs:ignore WordPress.Security.NonceVerification
65
			&& (
66
				'jetpack_upload_file' === $_POST['action']  // phpcs:ignore WordPress.Security.NonceVerification
67
				|| 'jetpack_update_file' === $_POST['action']  // phpcs:ignore WordPress.Security.NonceVerification
68
			)
69
		) {
70
			$this->require_jetpack_authentication();
71
			$this->add_remote_request_handlers();
0 ignored issues
show
Bug introduced by
The method add_remote_request_handlers() does not seem to exist on object<Automattic\Jetpack\Connection\Manager>.

This check looks for calls to methods that do not seem to exist on a given type. It looks for the method on the type itself as well as in inherited classes or implemented interfaces.

This is most likely a typographical error or the method has been renamed.

Loading history...
72
			return;
73
		}
74
75
		if ( $this->is_active() ) {
76
			add_action( 'login_form_jetpack_json_api_authorization', array( &$this, 'login_form_json_api_authorization' ) );
77
			add_filter( 'xmlrpc_methods', array( $this, 'public_xmlrpc_methods' ) );
78
		} else {
79
			add_action( 'rest_api_init', array( $this, 'initialize_rest_api_registration_connector' ) );
80
		}
81
	}
82
83
	/**
84
	 * Sets up the XMLRPC request handlers.
85
	 *
86
	 * @param Array                  $request_params incoming request parameters.
87
	 * @param Boolean                $is_active whether the connection is currently active.
88
	 * @param Boolean                $is_signed whether the signature check has been successful.
89
	 * @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...
90
	 */
91
	public function setup_xmlrpc_handlers(
92
		$request_params,
93
		$is_active,
94
		$is_signed,
95
		\Jetpack_XMLRPC_Server $xmlrpc_server = null
96
	) {
97
		if (
98
			! isset( $request_params['for'] )
99
			|| 'jetpack' !== $request_params['for']
100
		) {
101
			return false;
102
		}
103
104
		// Alternate XML-RPC, via ?for=jetpack&jetpack=comms.
105
		if (
106
			isset( $request_params['jetpack'] )
107
			&& 'comms' === $request_params['jetpack']
108
		) {
109
			if ( ! Constants::is_defined( 'XMLRPC_REQUEST' ) ) {
110
				// Use the real constant here for WordPress' sake.
111
				define( 'XMLRPC_REQUEST', true );
112
			}
113
114
			add_action( 'template_redirect', array( $this, 'alternate_xmlrpc' ) );
115
116
			add_filter( 'xmlrpc_methods', array( $this, 'remove_non_jetpack_xmlrpc_methods' ), 1000 );
117
		}
118
119
		if ( ! Constants::get_constant( 'XMLRPC_REQUEST' ) ) {
120
			return false;
121
		}
122
		// Display errors can cause the XML to be not well formed.
123
		@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...
124
125
		if ( $xmlrpc_server ) {
126
			$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...
127
		} else {
128
			$this->xmlrpc_server = new \Jetpack_XMLRPC_Server();
129
		}
130
131
		$this->require_jetpack_authentication();
132
133
		if ( $is_active ) {
134
			// Hack to preserve $HTTP_RAW_POST_DATA.
135
			add_filter( 'xmlrpc_methods', array( $this, 'xmlrpc_methods' ) );
136
137
			if ( $is_signed ) {
138
				// The actual API methods.
139
				add_filter( 'xmlrpc_methods', array( $this->xmlrpc_server, 'xmlrpc_methods' ) );
140
			} else {
141
				// The jetpack.authorize method should be available for unauthenticated users on a site with an
142
				// active Jetpack connection, so that additional users can link their account.
143
				add_filter( 'xmlrpc_methods', array( $this->xmlrpc_server, 'authorize_xmlrpc_methods' ) );
144
			}
145
		} else {
146
			// The bootstrap API methods.
147
			add_filter( 'xmlrpc_methods', array( $this->xmlrpc_server, 'bootstrap_xmlrpc_methods' ) );
148
149
			if ( $is_signed ) {
150
				// The jetpack Provision method is available for blog-token-signed requests.
151
				add_filter( 'xmlrpc_methods', array( $this->xmlrpc_server, 'provision_xmlrpc_methods' ) );
152
			} else {
153
				new XMLRPC_Connector( $this );
154
			}
155
		}
156
157
		add_filter( 'xmlrpc_blog_options', array( $this, 'xmlrpc_options' ) );
158
159
		add_action( 'jetpack_clean_nonces', array( $this, 'clean_nonces' ) );
160
		if ( ! wp_next_scheduled( 'jetpack_clean_nonces' ) ) {
161
			wp_schedule_event( time(), 'hourly', 'jetpack_clean_nonces' );
162
		}
163
164
		// Now that no one can authenticate, and we're whitelisting all XML-RPC methods, force enable_xmlrpc on.
165
		add_filter( 'pre_option_enable_xmlrpc', '__return_true' );
166
167
		return true;
168
	}
169
170
	/**
171
	 * Initializes the REST API connector on the init hook.
172
	 */
173
	public function initialize_rest_api_registration_connector() {
174
		new REST_Connector( $this );
175
	}
176
177
	/**
178
	 * Since a lot of hosts use a hammer approach to "protecting" WordPress sites,
179
	 * and just blanket block all requests to /xmlrpc.php, or apply other overly-sensitive
180
	 * security/firewall policies, we provide our own alternate XML RPC API endpoint
181
	 * which is accessible via a different URI. Most of the below is copied directly
182
	 * from /xmlrpc.php so that we're replicating it as closely as possible.
183
	 *
184
	 * @todo Tighten $wp_xmlrpc_server_class a bit to make sure it doesn't do bad things.
185
	 */
186
	public function alternate_xmlrpc() {
187
		// phpcs:disable PHPCompatibility.Variables.RemovedPredefinedGlobalVariables.http_raw_post_dataDeprecatedRemoved
188
		// phpcs:disable WordPress.WP.GlobalVariablesOverride.Prohibited
189
		global $HTTP_RAW_POST_DATA;
190
191
		// Some browser-embedded clients send cookies. We don't want them.
192
		$_COOKIE = array();
193
194
		// A fix for mozBlog and other cases where '<?xml' isn't on the very first line.
195
		if ( isset( $HTTP_RAW_POST_DATA ) ) {
196
			$HTTP_RAW_POST_DATA = trim( $HTTP_RAW_POST_DATA );
197
		}
198
199
		// phpcs:enable
200
201
		include_once ABSPATH . 'wp-admin/includes/admin.php';
202
		include_once ABSPATH . WPINC . '/class-IXR.php';
203
		include_once ABSPATH . WPINC . '/class-wp-xmlrpc-server.php';
204
205
		/**
206
		 * Filters the class used for handling XML-RPC requests.
207
		 *
208
		 * @since 3.1.0
209
		 *
210
		 * @param string $class The name of the XML-RPC server class.
211
		 */
212
		$wp_xmlrpc_server_class = apply_filters( 'wp_xmlrpc_server_class', 'wp_xmlrpc_server' );
213
		$wp_xmlrpc_server       = new $wp_xmlrpc_server_class();
214
215
		// Fire off the request.
216
		nocache_headers();
217
		$wp_xmlrpc_server->serve_request();
218
219
		exit;
220
	}
221
222
	/**
223
	 * Removes all XML-RPC methods that are not `jetpack.*`.
224
	 * Only used in our alternate XML-RPC endpoint, where we want to
225
	 * ensure that Core and other plugins' methods are not exposed.
226
	 *
227
	 * @param array $methods a list of registered WordPress XMLRPC methods.
228
	 * @return array filtered $methods
229
	 */
230
	public function remove_non_jetpack_xmlrpc_methods( $methods ) {
231
		$jetpack_methods = array();
232
233
		foreach ( $methods as $method => $callback ) {
234
			if ( 0 === strpos( $method, 'jetpack.' ) ) {
235
				$jetpack_methods[ $method ] = $callback;
236
			}
237
		}
238
239
		return $jetpack_methods;
240
	}
241
242
	/**
243
	 * Removes all other authentication methods not to allow other
244
	 * methods to validate unauthenticated requests.
245
	 */
246
	public function require_jetpack_authentication() {
247
		// Don't let anyone authenticate.
248
		$_COOKIE = array();
249
		remove_all_filters( 'authenticate' );
250
		remove_all_actions( 'wp_login_failed' );
251
252
		if ( $this->is_active() ) {
253
			// Allow Jetpack authentication.
254
			add_filter( 'authenticate', array( $this, 'authenticate_jetpack' ), 10, 3 );
255
		}
256
	}
257
258
	/**
259
	 * Authenticates XML-RPC and other requests from the Jetpack Server
260
	 *
261
	 * @param WP_User|Mixed $user user object if authenticated.
262
	 * @param String        $username username.
263
	 * @param String        $password password string.
264
	 * @return WP_User|Mixed authenticated user or error.
265
	 */
266
	public function authenticate_jetpack( $user, $username, $password ) {
267
		if ( is_a( $user, '\\WP_User' ) ) {
268
			return $user;
269
		}
270
271
		$token_details = $this->verify_xml_rpc_signature();
272
273
		if ( ! $token_details ) {
274
			return $user;
275
		}
276
277
		if ( 'user' !== $token_details['type'] ) {
278
			return $user;
279
		}
280
281
		if ( ! $token_details['user_id'] ) {
282
			return $user;
283
		}
284
285
		nocache_headers();
286
287
		return new \WP_User( $token_details['user_id'] );
288
	}
289
290
	/**
291
	 * Verifies the signature of the current request.
292
	 *
293
	 * @return false|array
294
	 */
295
	public function verify_xml_rpc_signature() {
296
		if ( is_null( $this->xmlrpc_verification ) ) {
297
			$this->xmlrpc_verification = $this->internal_verify_xml_rpc_signature();
298
299
			if ( is_wp_error( $this->xmlrpc_verification ) ) {
300
				/**
301
				 * Action for logging XMLRPC signature verification errors. This data is sensitive.
302
				 *
303
				 * Error codes:
304
				 * - malformed_token
305
				 * - malformed_user_id
306
				 * - unknown_token
307
				 * - could_not_sign
308
				 * - invalid_nonce
309
				 * - signature_mismatch
310
				 *
311
				 * @since 7.5.0
312
				 *
313
				 * @param WP_Error $signature_verification_error The verification error
314
				 */
315
				do_action( 'jetpack_verify_signature_error', $this->xmlrpc_verification );
316
			}
317
		}
318
319
		return is_wp_error( $this->xmlrpc_verification ) ? false : $this->xmlrpc_verification;
320
	}
321
322
	/**
323
	 * Verifies the signature of the current request.
324
	 *
325
	 * This function has side effects and should not be used. Instead,
326
	 * use the memoized version `->verify_xml_rpc_signature()`.
327
	 *
328
	 * @internal
329
	 */
330
	private function internal_verify_xml_rpc_signature() {
331
		// It's not for us.
332
		if ( ! isset( $_GET['token'] ) || empty( $_GET['signature'] ) ) {
333
			return false;
334
		}
335
336
		$signature_details = array(
337
			'token'     => isset( $_GET['token'] ) ? wp_unslash( $_GET['token'] ) : '',
338
			'timestamp' => isset( $_GET['timestamp'] ) ? wp_unslash( $_GET['timestamp'] ) : '',
339
			'nonce'     => isset( $_GET['nonce'] ) ? wp_unslash( $_GET['nonce'] ) : '',
340
			'body_hash' => isset( $_GET['body-hash'] ) ? wp_unslash( $_GET['body-hash'] ) : '',
341
			'method'    => wp_unslash( $_SERVER['REQUEST_METHOD'] ),
342
			'url'       => wp_unslash( $_SERVER['HTTP_HOST'] . $_SERVER['REQUEST_URI'] ), // Temp - will get real signature URL later.
343
			'signature' => isset( $_GET['signature'] ) ? wp_unslash( $_GET['signature'] ) : '',
344
		);
345
346
		@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...
347
		if (
348
			empty( $token_key )
349
		||
350
			empty( $version ) || strval( JETPACK__API_VERSION ) !== $version
351
		) {
352
			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...
353
		}
354
355
		if ( '0' === $user_id ) {
356
			$token_type = 'blog';
357
			$user_id    = 0;
358
		} else {
359
			$token_type = 'user';
360
			if ( empty( $user_id ) || ! ctype_digit( $user_id ) ) {
361
				return new \WP_Error(
362
					'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...
363
					'Malformed user_id in request',
364
					compact( 'signature_details' )
365
				);
366
			}
367
			$user_id = (int) $user_id;
368
369
			$user = new \WP_User( $user_id );
370
			if ( ! $user || ! $user->exists() ) {
371
				return new \WP_Error(
372
					'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...
373
					sprintf( 'User %d does not exist', $user_id ),
374
					compact( 'signature_details' )
375
				);
376
			}
377
		}
378
379
		$token = $this->get_access_token( $user_id, $token_key, false );
380
		if ( is_wp_error( $token ) ) {
381
			$token->add_data( compact( 'signature_details' ) );
382
			return $token;
383
		} elseif ( ! $token ) {
384
			return new \WP_Error(
385
				'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...
386
				sprintf( 'Token %s:%s:%d does not exist', $token_key, $version, $user_id ),
387
				compact( 'signature_details' )
388
			);
389
		}
390
391
		$jetpack_signature = new \Jetpack_Signature( $token->secret, (int) \Jetpack_Options::get_option( 'time_diff' ) );
392
		// phpcs:disable WordPress.Security.NonceVerification.Missing
393
		if ( isset( $_POST['_jetpack_is_multipart'] ) ) {
394
			$post_data   = $_POST;
395
			$file_hashes = array();
396
			foreach ( $post_data as $post_data_key => $post_data_value ) {
397
				if ( 0 !== strpos( $post_data_key, '_jetpack_file_hmac_' ) ) {
398
					continue;
399
				}
400
				$post_data_key                 = substr( $post_data_key, strlen( '_jetpack_file_hmac_' ) );
401
				$file_hashes[ $post_data_key ] = $post_data_value;
402
			}
403
404
			foreach ( $file_hashes as $post_data_key => $post_data_value ) {
405
				unset( $post_data[ "_jetpack_file_hmac_{$post_data_key}" ] );
406
				$post_data[ $post_data_key ] = $post_data_value;
407
			}
408
409
			ksort( $post_data );
410
411
			$body = http_build_query( stripslashes_deep( $post_data ) );
412
		} elseif ( is_null( $this->raw_post_data ) ) {
413
			$body = file_get_contents( 'php://input' );
414
		} else {
415
			$body = null;
416
		}
417
		// phpcs:enable
418
419
		$signature = $jetpack_signature->sign_current_request(
420
			array( 'body' => is_null( $body ) ? $this->raw_post_data : $body )
421
		);
422
423
		$signature_details['url'] = $jetpack_signature->current_request_url;
424
425
		if ( ! $signature ) {
426
			return new \WP_Error(
427
				'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...
428
				'Unknown signature error',
429
				compact( 'signature_details' )
430
			);
431
		} elseif ( is_wp_error( $signature ) ) {
432
			return $signature;
433
		}
434
435
		$timestamp = (int) $_GET['timestamp'];
436
		$nonce     = stripslashes( (string) $_GET['nonce'] );
437
438
		// Use up the nonce regardless of whether the signature matches.
439
		if ( ! $this->add_nonce( $timestamp, $nonce ) ) {
440
			return new \WP_Error(
441
				'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...
442
				'Could not add nonce',
443
				compact( 'signature_details' )
444
			);
445
		}
446
447
		// Be careful about what you do with this debugging data.
448
		// If a malicious requester has access to the expected signature,
449
		// bad things might be possible.
450
		$signature_details['expected'] = $signature;
451
452
		if ( ! hash_equals( $signature, $_GET['signature'] ) ) {
453
			return new \WP_Error(
454
				'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...
455
				'Signature mismatch',
456
				compact( 'signature_details' )
457
			);
458
		}
459
460
		/**
461
		 * Action for additional token checking.
462
		 *
463
		 * @since 7.7.0
464
		 *
465
		 * @param Array $post_data request data.
466
		 * @param Array $token_data token data.
467
		 */
468
		return apply_filters(
469
			'jetpack_signature_check_token',
470
			array(
471
				'type'      => $token_type,
472
				'token_key' => $token_key,
473
				'user_id'   => $token->external_user_id,
474
			),
475
			$token,
476
			$this->raw_post_data
477
		);
478
	}
479
480
	/**
481
	 * Returns true if the current site is connected to WordPress.com.
482
	 *
483
	 * @return Boolean is the site connected?
484
	 */
485
	public function is_active() {
486
		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...
487
	}
488
489
	/**
490
	 * Returns true if the user with the specified identifier is connected to
491
	 * WordPress.com.
492
	 *
493
	 * @param Integer|Boolean $user_id the user identifier.
494
	 * @return Boolean is the user connected?
495
	 */
496
	public function is_user_connected( $user_id = false ) {
497
		$user_id = false === $user_id ? get_current_user_id() : absint( $user_id );
498
		if ( ! $user_id ) {
499
			return false;
500
		}
501
502
		return (bool) $this->get_access_token( $user_id );
503
	}
504
505
	/**
506
	 * Get the wpcom user data of the current|specified connected user.
507
	 *
508
	 * @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...
509
	 * @return Object the user object.
510
	 */
511 View Code Duplication
	public function get_connected_user_data( $user_id = null ) {
512
		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...
513
			$user_id = get_current_user_id();
514
		}
515
516
		$transient_key    = "jetpack_connected_user_data_$user_id";
517
		$cached_user_data = get_transient( $transient_key );
518
519
		if ( $cached_user_data ) {
520
			return $cached_user_data;
521
		}
522
523
		\Jetpack::load_xml_rpc_client();
524
		$xml = new \Jetpack_IXR_Client(
525
			array(
526
				'user_id' => $user_id,
527
			)
528
		);
529
		$xml->query( 'wpcom.getUser' );
530
		if ( ! $xml->isError() ) {
531
			$user_data = $xml->getResponse();
532
			set_transient( $transient_key, $xml->getResponse(), DAY_IN_SECONDS );
533
			return $user_data;
534
		}
535
536
		return false;
537
	}
538
539
	/**
540
	 * Returns true if the provided user is the Jetpack connection owner.
541
	 * If user ID is not specified, the current user will be used.
542
	 *
543
	 * @param Integer|Boolean $user_id the user identifier. False for current user.
544
	 * @return Boolean True the user the connection owner, false otherwise.
545
	 */
546
	public function is_connection_owner( $user_id = false ) {
547
		if ( ! $user_id ) {
548
			$user_id = get_current_user_id();
549
		}
550
551
		$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...
552
553
		return $user_token && is_object( $user_token ) && isset( $user_token->external_user_id ) && $user_id === $user_token->external_user_id;
554
	}
555
556
	/**
557
	 * Unlinks the current user from the linked WordPress.com user
558
	 *
559
	 * @param Integer $user_id the user identifier.
560
	 */
561
	public static function disconnect_user( $user_id ) {
562
		return $user_id;
563
	}
564
565
	/**
566
	 * Returns the requested Jetpack API URL.
567
	 *
568
	 * @param String $relative_url the relative API path.
569
	 * @return String API URL.
570
	 */
571
	public function api_url( $relative_url ) {
572
		$api_base = Constants::get_constant( 'JETPACK__API_BASE' );
573
		$version  = Constants::get_constant( 'JETPACK__API_VERSION' );
574
575
		$api_base = $api_base ? $api_base : 'https://jetpack.wordpress.com/jetpack.';
576
		$version  = $version ? '/' . $version . '/' : '/1/';
577
578
		return rtrim( $api_base . $relative_url, '/\\' ) . $version;
579
	}
580
581
	/**
582
	 * Attempts Jetpack registration which sets up the site for connection. Should
583
	 * remain public because the call to action comes from the current site, not from
584
	 * WordPress.com.
585
	 *
586
	 * @param String $api_endpoint (optional) an API endpoint to use, defaults to 'register'.
587
	 * @return Integer zero on success, or a bitmask on failure.
588
	 */
589
	public function register( $api_endpoint = 'register' ) {
590
		add_action( 'pre_update_jetpack_option_register', array( '\\Jetpack_Options', 'delete_option' ) );
591
		$secrets = $this->generate_secrets( 'register', get_current_user_id(), 600 );
592
593
		if (
594
			empty( $secrets['secret_1'] ) ||
595
			empty( $secrets['secret_2'] ) ||
596
			empty( $secrets['exp'] )
597
		) {
598
			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...
599
		}
600
601
		// Better to try (and fail) to set a higher timeout than this system
602
		// supports than to have register fail for more users than it should.
603
		$timeout = $this->set_min_time_limit( 60 ) / 2;
604
605
		$gmt_offset = get_option( 'gmt_offset' );
606
		if ( ! $gmt_offset ) {
607
			$gmt_offset = 0;
608
		}
609
610
		$stats_options = get_option( 'stats_options' );
611
		$stats_id      = isset( $stats_options['blog_id'] )
612
			? $stats_options['blog_id']
613
			: null;
614
615
		/**
616
		 * Filters the request body for additional property addition.
617
		 *
618
		 * @since 7.7.0
619
		 *
620
		 * @param Array $post_data request data.
621
		 * @param Array $token_data token data.
622
		 */
623
		$body = apply_filters(
624
			'jetpack_register_request_body',
625
			array(
626
				'siteurl'         => site_url(),
627
				'home'            => home_url(),
628
				'gmt_offset'      => $gmt_offset,
629
				'timezone_string' => (string) get_option( 'timezone_string' ),
630
				'site_name'       => (string) get_option( 'blogname' ),
631
				'secret_1'        => $secrets['secret_1'],
632
				'secret_2'        => $secrets['secret_2'],
633
				'site_lang'       => get_locale(),
634
				'timeout'         => $timeout,
635
				'stats_id'        => $stats_id,
636
				'state'           => get_current_user_id(),
637
				'site_created'    => $this->get_assumed_site_creation_date(),
638
				'jetpack_version' => Constants::get_constant( 'JETPACK__VERSION' ),
639
			)
640
		);
641
642
		$args = array(
643
			'method'  => 'POST',
644
			'body'    => $body,
645
			'headers' => array(
646
				'Accept' => 'application/json',
647
			),
648
			'timeout' => $timeout,
649
		);
650
651
		$args['body'] = $this->apply_activation_source_to_args( $args['body'] );
652
653
		// TODO: fix URLs for bad hosts.
654
		$response = Client::_wp_remote_request(
655
			$this->api_url( $api_endpoint ),
656
			$args,
657
			true
658
		);
659
660
		// Make sure the response is valid and does not contain any Jetpack errors.
661
		$registration_details = $this->validate_remote_register_response( $response );
662
663
		if ( is_wp_error( $registration_details ) ) {
664
			return $registration_details;
665
		} elseif ( ! $registration_details ) {
666
			return new \WP_Error(
667
				'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...
668
				'Unknown error registering your Jetpack site.',
669
				wp_remote_retrieve_response_code( $response )
670
			);
671
		}
672
673
		if ( empty( $registration_details->jetpack_secret ) || ! is_string( $registration_details->jetpack_secret ) ) {
674
			return new \WP_Error(
675
				'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...
676
				'Unable to validate registration of your Jetpack site.',
677
				wp_remote_retrieve_response_code( $response )
678
			);
679
		}
680
681
		if ( isset( $registration_details->jetpack_public ) ) {
682
			$jetpack_public = (int) $registration_details->jetpack_public;
683
		} else {
684
			$jetpack_public = false;
685
		}
686
687
		\Jetpack_Options::update_options(
688
			array(
689
				'id'         => (int) $registration_details->jetpack_id,
690
				'blog_token' => (string) $registration_details->jetpack_secret,
691
				'public'     => $jetpack_public,
692
			)
693
		);
694
695
		/**
696
		 * Fires when a site is registered on WordPress.com.
697
		 *
698
		 * @since 3.7.0
699
		 *
700
		 * @param int $json->jetpack_id Jetpack Blog ID.
701
		 * @param string $json->jetpack_secret Jetpack Blog Token.
702
		 * @param int|bool $jetpack_public Is the site public.
703
		 */
704
		do_action(
705
			'jetpack_site_registered',
706
			$registration_details->jetpack_id,
707
			$registration_details->jetpack_secret,
708
			$jetpack_public
709
		);
710
711
		if ( isset( $registration_details->token ) ) {
712
			/**
713
			 * Fires when a user token is sent along with the registration data.
714
			 *
715
			 * @since 7.6.0
716
			 *
717
			 * @param object $token the administrator token for the newly registered site.
718
			 */
719
			do_action( 'jetpack_site_registered_user_token', $registration_details->token );
720
		}
721
722
		return true;
723
	}
724
725
	/**
726
	 * Takes the response from the Jetpack register new site endpoint and
727
	 * verifies it worked properly.
728
	 *
729
	 * @since 2.6
730
	 *
731
	 * @param Mixed $response the response object, or the error object.
732
	 * @return string|WP_Error A JSON object on success or Jetpack_Error on failures
733
	 **/
734
	protected function validate_remote_register_response( $response ) {
735
		if ( is_wp_error( $response ) ) {
736
			return new \WP_Error(
737
				'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...
738
				$response->get_error_message()
739
			);
740
		}
741
742
		$code   = wp_remote_retrieve_response_code( $response );
743
		$entity = wp_remote_retrieve_body( $response );
744
745
		if ( $entity ) {
746
			$registration_response = json_decode( $entity );
747
		} else {
748
			$registration_response = false;
749
		}
750
751
		$code_type = intval( $code / 100 );
752
		if ( 5 === $code_type ) {
753
			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...
754
		} elseif ( 408 === $code ) {
755
			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...
756
		} elseif ( ! empty( $registration_response->error ) ) {
757
			if (
758
				'xml_rpc-32700' === $registration_response->error
759
				&& ! function_exists( 'xml_parser_create' )
760
			) {
761
				$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' );
762
			} else {
763
				$error_description = isset( $registration_response->error_description )
764
					? (string) $registration_response->error_description
765
					: '';
766
			}
767
768
			return new \WP_Error(
769
				(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...
770
				$error_description,
771
				$code
772
			);
773
		} elseif ( 200 !== $code ) {
774
			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...
775
		}
776
777
		// Jetpack ID error block.
778
		if ( empty( $registration_response->jetpack_id ) ) {
779
			return new \WP_Error(
780
				'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...
781
				/* translators: %s is an error message string */
782
				sprintf( __( 'Error Details: Jetpack ID is empty. Do not publicly post this error message! %s', 'jetpack' ), $entity ),
783
				$entity
784
			);
785
		} elseif ( ! is_scalar( $registration_response->jetpack_id ) ) {
786
			return new \WP_Error(
787
				'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...
788
				/* translators: %s is an error message string */
789
				sprintf( __( 'Error Details: Jetpack ID is not a scalar. Do not publicly post this error message! %s', 'jetpack' ), $entity ),
790
				$entity
791
			);
792
		} elseif ( preg_match( '/[^0-9]/', $registration_response->jetpack_id ) ) {
793
			return new \WP_Error(
794
				'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...
795
				/* translators: %s is an error message string */
796
				sprintf( __( 'Error Details: Jetpack ID begins with a numeral. Do not publicly post this error message! %s', 'jetpack' ), $entity ),
797
				$entity
798
			);
799
		}
800
801
		return $registration_response;
802
	}
803
804
	/**
805
	 * Adds a used nonce to a list of known nonces.
806
	 *
807
	 * @param int    $timestamp the current request timestamp.
808
	 * @param string $nonce the nonce value.
809
	 * @return bool whether the nonce is unique or not.
810
	 */
811
	public function add_nonce( $timestamp, $nonce ) {
812
		global $wpdb;
813
		static $nonces_used_this_request = array();
814
815
		if ( isset( $nonces_used_this_request[ "$timestamp:$nonce" ] ) ) {
816
			return $nonces_used_this_request[ "$timestamp:$nonce" ];
817
		}
818
819
		// This should always have gone through Jetpack_Signature::sign_request() first to check $timestamp an $nonce.
820
		$timestamp = (int) $timestamp;
821
		$nonce     = esc_sql( $nonce );
822
823
		// Raw query so we can avoid races: add_option will also update.
824
		$show_errors = $wpdb->show_errors( false );
825
826
		$old_nonce = $wpdb->get_row(
827
			$wpdb->prepare( "SELECT * FROM `$wpdb->options` WHERE option_name = %s", "jetpack_nonce_{$timestamp}_{$nonce}" )
828
		);
829
830
		if ( is_null( $old_nonce ) ) {
831
			$return = $wpdb->query(
832
				$wpdb->prepare(
833
					"INSERT INTO `$wpdb->options` (`option_name`, `option_value`, `autoload`) VALUES (%s, %s, %s)",
834
					"jetpack_nonce_{$timestamp}_{$nonce}",
835
					time(),
836
					'no'
837
				)
838
			);
839
		} else {
840
			$return = false;
841
		}
842
843
		$wpdb->show_errors( $show_errors );
844
845
		$nonces_used_this_request[ "$timestamp:$nonce" ] = $return;
846
847
		return $return;
848
	}
849
850
	/**
851
	 * Cleans nonces that were saved when calling ::add_nonce.
852
	 *
853
	 * @todo Properly prepare the query before executing it.
854
	 *
855
	 * @param bool $all whether to clean even non-expired nonces.
856
	 */
857
	public function clean_nonces( $all = false ) {
858
		global $wpdb;
859
860
		$sql      = "DELETE FROM `$wpdb->options` WHERE `option_name` LIKE %s";
861
		$sql_args = array( $wpdb->esc_like( 'jetpack_nonce_' ) . '%' );
862
863
		if ( true !== $all ) {
864
			$sql       .= ' AND CAST( `option_value` AS UNSIGNED ) < %d';
865
			$sql_args[] = time() - 3600;
866
		}
867
868
		$sql .= ' ORDER BY `option_id` LIMIT 100';
869
870
		$sql = $wpdb->prepare( $sql, $sql_args ); // phpcs:ignore WordPress.DB.PreparedSQL.NotPrepared
871
872
		for ( $i = 0; $i < 1000; $i++ ) {
873
			if ( ! $wpdb->query( $sql ) ) { // phpcs:ignore WordPress.DB.PreparedSQL.NotPrepared
874
				break;
875
			}
876
		}
877
	}
878
879
	/**
880
	 * Builds the timeout limit for queries talking with the wpcom servers.
881
	 *
882
	 * Based on local php max_execution_time in php.ini
883
	 *
884
	 * @since 5.4
885
	 * @return int
886
	 **/
887
	public function get_max_execution_time() {
888
		$timeout = (int) ini_get( 'max_execution_time' );
889
890
		// Ensure exec time set in php.ini.
891
		if ( ! $timeout ) {
892
			$timeout = 30;
893
		}
894
		return $timeout;
895
	}
896
897
	/**
898
	 * Sets a minimum request timeout, and returns the current timeout
899
	 *
900
	 * @since 5.4
901
	 * @param Integer $min_timeout the minimum timeout value.
902
	 **/
903 View Code Duplication
	public function set_min_time_limit( $min_timeout ) {
904
		$timeout = $this->get_max_execution_time();
905
		if ( $timeout < $min_timeout ) {
906
			$timeout = $min_timeout;
907
			set_time_limit( $timeout );
908
		}
909
		return $timeout;
910
	}
911
912
	/**
913
	 * Get our assumed site creation date.
914
	 * Calculated based on the earlier date of either:
915
	 * - Earliest admin user registration date.
916
	 * - Earliest date of post of any post type.
917
	 *
918
	 * @since 7.2.0
919
	 *
920
	 * @return string Assumed site creation date and time.
921
	 */
922 View Code Duplication
	public function get_assumed_site_creation_date() {
923
		$earliest_registered_users  = get_users(
924
			array(
925
				'role'    => 'administrator',
926
				'orderby' => 'user_registered',
927
				'order'   => 'ASC',
928
				'fields'  => array( 'user_registered' ),
929
				'number'  => 1,
930
			)
931
		);
932
		$earliest_registration_date = $earliest_registered_users[0]->user_registered;
933
934
		$earliest_posts = get_posts(
935
			array(
936
				'posts_per_page' => 1,
937
				'post_type'      => 'any',
938
				'post_status'    => 'any',
939
				'orderby'        => 'date',
940
				'order'          => 'ASC',
941
			)
942
		);
943
944
		// If there are no posts at all, we'll count only on user registration date.
945
		if ( $earliest_posts ) {
946
			$earliest_post_date = $earliest_posts[0]->post_date;
947
		} else {
948
			$earliest_post_date = PHP_INT_MAX;
949
		}
950
951
		return min( $earliest_registration_date, $earliest_post_date );
952
	}
953
954
	/**
955
	 * Adds the activation source string as a parameter to passed arguments.
956
	 *
957
	 * @param Array $args arguments that need to have the source added.
958
	 * @return Array $amended arguments.
959
	 */
960 View Code Duplication
	public static function apply_activation_source_to_args( $args ) {
961
		list( $activation_source_name, $activation_source_keyword ) = get_option( 'jetpack_activation_source' );
962
963
		if ( $activation_source_name ) {
964
			$args['_as'] = urlencode( $activation_source_name );
965
		}
966
967
		if ( $activation_source_keyword ) {
968
			$args['_ak'] = urlencode( $activation_source_keyword );
969
		}
970
971
		return $args;
972
	}
973
974
	/**
975
	 * Returns the callable that would be used to generate secrets.
976
	 *
977
	 * @return Callable a function that returns a secure string to be used as a secret.
978
	 */
979
	protected function get_secret_callable() {
980
		if ( ! isset( $this->secret_callable ) ) {
981
			/**
982
			 * Allows modification of the callable that is used to generate connection secrets.
983
			 *
984
			 * @param Callable a function or method that returns a secret string.
985
			 */
986
			$this->secret_callable = apply_filters( 'jetpack_connection_secret_generator', 'wp_generate_password' );
987
		}
988
989
		return $this->secret_callable;
990
	}
991
992
	/**
993
	 * Generates two secret tokens and the end of life timestamp for them.
994
	 *
995
	 * @param String  $action  The action name.
996
	 * @param Integer $user_id The user identifier.
997
	 * @param Integer $exp     Expiration time in seconds.
998
	 */
999
	public function generate_secrets( $action, $user_id, $exp ) {
1000
		$callable = $this->get_secret_callable();
1001
1002
		$secrets = \Jetpack_Options::get_raw_option(
1003
			self::SECRETS_OPTION_NAME,
1004
			array()
1005
		);
1006
1007
		$secret_name = 'jetpack_' . $action . '_' . $user_id;
1008
1009
		if (
1010
			isset( $secrets[ $secret_name ] ) &&
1011
			$secrets[ $secret_name ]['exp'] > time()
1012
		) {
1013
			return $secrets[ $secret_name ];
1014
		}
1015
1016
		$secret_value = array(
1017
			'secret_1' => call_user_func( $callable ),
1018
			'secret_2' => call_user_func( $callable ),
1019
			'exp'      => time() + $exp,
1020
		);
1021
1022
		$secrets[ $secret_name ] = $secret_value;
1023
1024
		\Jetpack_Options::update_raw_option( self::SECRETS_OPTION_NAME, $secrets );
1025
		return $secrets[ $secret_name ];
1026
	}
1027
1028
	/**
1029
	 * Returns two secret tokens and the end of life timestamp for them.
1030
	 *
1031
	 * @param String  $action  The action name.
1032
	 * @param Integer $user_id The user identifier.
1033
	 * @return string|array an array of secrets or an error string.
1034
	 */
1035
	public function get_secrets( $action, $user_id ) {
1036
		$secret_name = 'jetpack_' . $action . '_' . $user_id;
1037
		$secrets     = \Jetpack_Options::get_raw_option(
1038
			self::SECRETS_OPTION_NAME,
1039
			array()
1040
		);
1041
1042
		if ( ! isset( $secrets[ $secret_name ] ) ) {
1043
			return self::SECRETS_MISSING;
1044
		}
1045
1046
		if ( $secrets[ $secret_name ]['exp'] < time() ) {
1047
			$this->delete_secrets( $action, $user_id );
1048
			return self::SECRETS_EXPIRED;
1049
		}
1050
1051
		return $secrets[ $secret_name ];
1052
	}
1053
1054
	/**
1055
	 * Deletes secret tokens in case they, for example, have expired.
1056
	 *
1057
	 * @param String  $action  The action name.
1058
	 * @param Integer $user_id The user identifier.
1059
	 */
1060
	public function delete_secrets( $action, $user_id ) {
1061
		$secret_name = 'jetpack_' . $action . '_' . $user_id;
1062
		$secrets     = \Jetpack_Options::get_raw_option(
1063
			self::SECRETS_OPTION_NAME,
1064
			array()
1065
		);
1066
		if ( isset( $secrets[ $secret_name ] ) ) {
1067
			unset( $secrets[ $secret_name ] );
1068
			\Jetpack_Options::update_raw_option( self::SECRETS_OPTION_NAME, $secrets );
1069
		}
1070
	}
1071
1072
	/**
1073
	 * Responds to a WordPress.com call to register the current site.
1074
	 * Should be changed to protected.
1075
	 *
1076
	 * @param array $registration_data Array of [ secret_1, user_id ].
1077
	 */
1078
	public function handle_registration( array $registration_data ) {
1079
		list( $registration_secret_1, $registration_user_id ) = $registration_data;
1080
		if ( empty( $registration_user_id ) ) {
1081
			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...
1082
		}
1083
1084
		return $this->verify_secrets( 'register', $registration_secret_1, (int) $registration_user_id );
1085
	}
1086
1087
	/**
1088
	 * Verify a Previously Generated Secret.
1089
	 *
1090
	 * @param string $action   The type of secret to verify.
1091
	 * @param string $secret_1 The secret string to compare to what is stored.
1092
	 * @param int    $user_id  The user ID of the owner of the secret.
1093
	 */
1094
	protected function verify_secrets( $action, $secret_1, $user_id ) {
1095
		$allowed_actions = array( 'register', 'authorize', 'publicize' );
1096
		if ( ! in_array( $action, $allowed_actions, true ) ) {
1097
			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...
1098
		}
1099
1100
		$user = get_user_by( 'id', $user_id );
1101
1102
		/**
1103
		 * We've begun verifying the previously generated secret.
1104
		 *
1105
		 * @since 7.5.0
1106
		 *
1107
		 * @param string   $action The type of secret to verify.
1108
		 * @param \WP_User $user The user object.
1109
		 */
1110
		do_action( 'jetpack_verify_secrets_begin', $action, $user );
1111
1112
		$return_error = function( \WP_Error $error ) use ( $action, $user ) {
1113
			/**
1114
			 * Verifying of the previously generated secret has failed.
1115
			 *
1116
			 * @since 7.5.0
1117
			 *
1118
			 * @param string    $action  The type of secret to verify.
1119
			 * @param \WP_User  $user The user object.
1120
			 * @param \WP_Error $error The error object.
1121
			 */
1122
			do_action( 'jetpack_verify_secrets_fail', $action, $user, $error );
1123
1124
			return $error;
1125
		};
1126
1127
		$stored_secrets = $this->get_secrets( $action, $user_id );
1128
		$this->delete_secrets( $action, $user_id );
1129
1130
		if ( empty( $secret_1 ) ) {
1131
			return $return_error(
1132
				new \WP_Error(
1133
					'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...
1134
					/* translators: "%s" is the name of a paramter. It can be either "secret_1" or "state". */
1135
					sprintf( __( 'The required "%s" parameter is missing.', 'jetpack' ), 'secret_1' ),
1136
					400
1137
				)
1138
			);
1139
		} elseif ( ! is_string( $secret_1 ) ) {
1140
			return $return_error(
1141
				new \WP_Error(
1142
					'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...
1143
					/* translators: "%s" is the name of a paramter. It can be either "secret_1" or "state". */
1144
					sprintf( __( 'The required "%s" parameter is malformed.', 'jetpack' ), 'secret_1' ),
1145
					400
1146
				)
1147
			);
1148
		} elseif ( empty( $user_id ) ) {
1149
			// $user_id is passed around during registration as "state".
1150
			return $return_error(
1151
				new \WP_Error(
1152
					'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...
1153
					/* translators: "%s" is the name of a paramter. It can be either "secret_1" or "state". */
1154
					sprintf( __( 'The required "%s" parameter is missing.', 'jetpack' ), 'state' ),
1155
					400
1156
				)
1157
			);
1158
		} elseif ( ! ctype_digit( (string) $user_id ) ) {
1159
			return $return_error(
1160
				new \WP_Error(
1161
					'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...
1162
					/* translators: "%s" is the name of a paramter. It can be either "secret_1" or "state". */
1163
					sprintf( __( 'The required "%s" parameter is malformed.', 'jetpack' ), 'state' ),
1164
					400
1165
				)
1166
			);
1167
		}
1168
1169
		if ( ! $stored_secrets ) {
1170
			return $return_error(
1171
				new \WP_Error(
1172
					'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...
1173
					__( 'Verification secrets not found', 'jetpack' ),
1174
					400
1175
				)
1176
			);
1177
		} elseif ( is_wp_error( $stored_secrets ) ) {
1178
			$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...
1179
			return $return_error( $stored_secrets );
1180
		} elseif ( empty( $stored_secrets['secret_1'] ) || empty( $stored_secrets['secret_2'] ) || empty( $stored_secrets['exp'] ) ) {
1181
			return $return_error(
1182
				new \WP_Error(
1183
					'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...
1184
					__( 'Verification secrets are incomplete', 'jetpack' ),
1185
					400
1186
				)
1187
			);
1188
		} elseif ( ! hash_equals( $secret_1, $stored_secrets['secret_1'] ) ) {
1189
			return $return_error(
1190
				new \WP_Error(
1191
					'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...
1192
					__( 'Secret mismatch', 'jetpack' ),
1193
					400
1194
				)
1195
			);
1196
		}
1197
1198
		/**
1199
		 * We've succeeded at verifying the previously generated secret.
1200
		 *
1201
		 * @since 7.5.0
1202
		 *
1203
		 * @param string   $action The type of secret to verify.
1204
		 * @param \WP_User $user The user object.
1205
		 */
1206
		do_action( 'jetpack_verify_secrets_success', $action, $user );
1207
1208
		return $stored_secrets['secret_2'];
1209
	}
1210
1211
	/**
1212
	 * Responds to a WordPress.com call to authorize the current user.
1213
	 * Should be changed to protected.
1214
	 */
1215
	public function handle_authorization() {
1216
1217
	}
1218
1219
	/**
1220
	 * Builds a URL to the Jetpack connection auth page.
1221
	 * This needs rethinking.
1222
	 *
1223
	 * @param bool        $raw If true, URL will not be escaped.
1224
	 * @param bool|string $redirect If true, will redirect back to Jetpack wp-admin landing page after connection.
1225
	 *                              If string, will be a custom redirect.
1226
	 * @param bool|string $from If not false, adds 'from=$from' param to the connect URL.
1227
	 * @param bool        $register If true, will generate a register URL regardless of the existing token, since 4.9.0.
1228
	 *
1229
	 * @return string Connect URL
1230
	 */
1231
	public function build_connect_url( $raw, $redirect, $from, $register ) {
1232
		return array( $raw, $redirect, $from, $register );
1233
	}
1234
1235
	/**
1236
	 * Disconnects from the Jetpack servers.
1237
	 * Forgets all connection details and tells the Jetpack servers to do the same.
1238
	 */
1239
	public function disconnect_site() {
1240
1241
	}
1242
1243
	/**
1244
	 * The Base64 Encoding of the SHA1 Hash of the Input.
1245
	 *
1246
	 * @param string $text The string to hash.
1247
	 * @return string
1248
	 */
1249
	public function sha1_base64( $text ) {
1250
		return base64_encode( sha1( $text, true ) ); // phpcs:ignore WordPress.PHP.DiscouragedPHPFunctions.obfuscation_base64_encode
1251
	}
1252
1253
	/**
1254
	 * This function mirrors Jetpack_Data::is_usable_domain() in the WPCOM codebase.
1255
	 *
1256
	 * @param string $domain The domain to check.
1257
	 *
1258
	 * @return bool|WP_Error
1259
	 */
1260
	public function is_usable_domain( $domain ) {
1261
1262
		// If it's empty, just fail out.
1263
		if ( ! $domain ) {
1264
			return new \WP_Error(
1265
				'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...
1266
				/* translators: %1$s is a domain name. */
1267
				sprintf( __( 'Domain `%1$s` just failed is_usable_domain check as it is empty.', 'jetpack' ), $domain )
1268
			);
1269
		}
1270
1271
		/**
1272
		 * Skips the usuable domain check when connecting a site.
1273
		 *
1274
		 * Allows site administrators with domains that fail gethostname-based checks to pass the request to WP.com
1275
		 *
1276
		 * @since 4.1.0
1277
		 *
1278
		 * @param bool If the check should be skipped. Default false.
1279
		 */
1280
		if ( apply_filters( 'jetpack_skip_usuable_domain_check', false ) ) {
1281
			return true;
1282
		}
1283
1284
		// None of the explicit localhosts.
1285
		$forbidden_domains = array(
1286
			'wordpress.com',
1287
			'localhost',
1288
			'localhost.localdomain',
1289
			'127.0.0.1',
1290
			'local.wordpress.test',         // VVV pattern.
1291
			'local.wordpress-trunk.test',   // VVV pattern.
1292
			'src.wordpress-develop.test',   // VVV pattern.
1293
			'build.wordpress-develop.test', // VVV pattern.
1294
		);
1295 View Code Duplication
		if ( in_array( $domain, $forbidden_domains, true ) ) {
1296
			return new \WP_Error(
1297
				'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...
1298
				sprintf(
1299
					/* translators: %1$s is a domain name. */
1300
					__(
1301
						'Domain `%1$s` just failed is_usable_domain check as it is in the forbidden array.',
1302
						'jetpack'
1303
					),
1304
					$domain
1305
				)
1306
			);
1307
		}
1308
1309
		// No .test or .local domains.
1310 View Code Duplication
		if ( preg_match( '#\.(test|local)$#i', $domain ) ) {
1311
			return new \WP_Error(
1312
				'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...
1313
				sprintf(
1314
					/* translators: %1$s is a domain name. */
1315
					__(
1316
						'Domain `%1$s` just failed is_usable_domain check as it uses an invalid top level domain.',
1317
						'jetpack'
1318
					),
1319
					$domain
1320
				)
1321
			);
1322
		}
1323
1324
		// No WPCOM subdomains.
1325 View Code Duplication
		if ( preg_match( '#\.WordPress\.com$#i', $domain ) ) {
1326
			return new \WP_Error(
1327
				'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...
1328
				sprintf(
1329
					/* translators: %1$s is a domain name. */
1330
					__(
1331
						'Domain `%1$s` just failed is_usable_domain check as it is a subdomain of WordPress.com.',
1332
						'jetpack'
1333
					),
1334
					$domain
1335
				)
1336
			);
1337
		}
1338
1339
		// If PHP was compiled without support for the Filter module (very edge case).
1340
		if ( ! function_exists( 'filter_var' ) ) {
1341
			// Just pass back true for now, and let wpcom sort it out.
1342
			return true;
1343
		}
1344
1345
		return true;
1346
	}
1347
1348
	/**
1349
	 * Gets the requested token.
1350
	 *
1351
	 * Tokens are one of two types:
1352
	 * 1. Blog Tokens: These are the "main" tokens. Each site typically has one Blog Token,
1353
	 *    though some sites can have multiple "Special" Blog Tokens (see below). These tokens
1354
	 *    are not associated with a user account. They represent the site's connection with
1355
	 *    the Jetpack servers.
1356
	 * 2. User Tokens: These are "sub-"tokens. Each connected user account has one User Token.
1357
	 *
1358
	 * All tokens look like "{$token_key}.{$private}". $token_key is a public ID for the
1359
	 * token, and $private is a secret that should never be displayed anywhere or sent
1360
	 * over the network; it's used only for signing things.
1361
	 *
1362
	 * Blog Tokens can be "Normal" or "Special".
1363
	 * * Normal: The result of a normal connection flow. They look like
1364
	 *   "{$random_string_1}.{$random_string_2}"
1365
	 *   That is, $token_key and $private are both random strings.
1366
	 *   Sites only have one Normal Blog Token. Normal Tokens are found in either
1367
	 *   Jetpack_Options::get_option( 'blog_token' ) (usual) or the JETPACK_BLOG_TOKEN
1368
	 *   constant (rare).
1369
	 * * Special: A connection token for sites that have gone through an alternative
1370
	 *   connection flow. They look like:
1371
	 *   ";{$special_id}{$special_version};{$wpcom_blog_id};.{$random_string}"
1372
	 *   That is, $private is a random string and $token_key has a special structure with
1373
	 *   lots of semicolons.
1374
	 *   Most sites have zero Special Blog Tokens. Special tokens are only found in the
1375
	 *   JETPACK_BLOG_TOKEN constant.
1376
	 *
1377
	 * In particular, note that Normal Blog Tokens never start with ";" and that
1378
	 * Special Blog Tokens always do.
1379
	 *
1380
	 * When searching for a matching Blog Tokens, Blog Tokens are examined in the following
1381
	 * order:
1382
	 * 1. Defined Special Blog Tokens (via the JETPACK_BLOG_TOKEN constant)
1383
	 * 2. Stored Normal Tokens (via Jetpack_Options::get_option( 'blog_token' ))
1384
	 * 3. Defined Normal Tokens (via the JETPACK_BLOG_TOKEN constant)
1385
	 *
1386
	 * @param int|false    $user_id   false: Return the Blog Token. int: Return that user's User Token.
1387
	 * @param string|false $token_key If provided, check that the token matches the provided input.
1388
	 * @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.
1389
	 *
1390
	 * @return object|false
1391
	 */
1392
	public function get_access_token( $user_id = false, $token_key = false, $suppress_errors = true ) {
1393
		$possible_special_tokens = array();
1394
		$possible_normal_tokens  = array();
1395
		$user_tokens             = \Jetpack_Options::get_option( 'user_tokens' );
1396
1397
		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...
1398
			if ( ! $user_tokens ) {
1399
				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...
1400
			}
1401
			if ( self::JETPACK_MASTER_USER === $user_id ) {
1402
				$user_id = \Jetpack_Options::get_option( 'master_user' );
1403
				if ( ! $user_id ) {
1404
					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...
1405
				}
1406
			}
1407
			if ( ! isset( $user_tokens[ $user_id ] ) || ! $user_tokens[ $user_id ] ) {
1408
				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...
1409
			}
1410
			$user_token_chunks = explode( '.', $user_tokens[ $user_id ] );
1411
			if ( empty( $user_token_chunks[1] ) || empty( $user_token_chunks[2] ) ) {
1412
				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...
1413
			}
1414
			if ( $user_token_chunks[2] !== (string) $user_id ) {
1415
				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...
1416
			}
1417
			$possible_normal_tokens[] = "{$user_token_chunks[0]}.{$user_token_chunks[1]}";
1418
		} else {
1419
			$stored_blog_token = \Jetpack_Options::get_option( 'blog_token' );
1420
			if ( $stored_blog_token ) {
1421
				$possible_normal_tokens[] = $stored_blog_token;
1422
			}
1423
1424
			$defined_tokens_string = Constants::get_constant( 'JETPACK_BLOG_TOKEN' );
1425
1426
			if ( $defined_tokens_string ) {
1427
				$defined_tokens = explode( ',', $defined_tokens_string );
1428
				foreach ( $defined_tokens as $defined_token ) {
1429
					if ( ';' === $defined_token[0] ) {
1430
						$possible_special_tokens[] = $defined_token;
1431
					} else {
1432
						$possible_normal_tokens[] = $defined_token;
1433
					}
1434
				}
1435
			}
1436
		}
1437
1438
		if ( self::MAGIC_NORMAL_TOKEN_KEY === $token_key ) {
1439
			$possible_tokens = $possible_normal_tokens;
1440
		} else {
1441
			$possible_tokens = array_merge( $possible_special_tokens, $possible_normal_tokens );
1442
		}
1443
1444
		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...
1445
			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...
1446
		}
1447
1448
		$valid_token = false;
1449
1450
		if ( false === $token_key ) {
1451
			// Use first token.
1452
			$valid_token = $possible_tokens[0];
1453
		} elseif ( self::MAGIC_NORMAL_TOKEN_KEY === $token_key ) {
1454
			// Use first normal token.
1455
			$valid_token = $possible_tokens[0]; // $possible_tokens only contains normal tokens because of earlier check.
1456
		} else {
1457
			// Use the token matching $token_key or false if none.
1458
			// Ensure we check the full key.
1459
			$token_check = rtrim( $token_key, '.' ) . '.';
1460
1461
			foreach ( $possible_tokens as $possible_token ) {
1462
				if ( hash_equals( substr( $possible_token, 0, strlen( $token_check ) ), $token_check ) ) {
1463
					$valid_token = $possible_token;
1464
					break;
1465
				}
1466
			}
1467
		}
1468
1469
		if ( ! $valid_token ) {
1470
			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...
1471
		}
1472
1473
		return (object) array(
1474
			'secret'           => $valid_token,
1475
			'external_user_id' => (int) $user_id,
1476
		);
1477
	}
1478
1479
	/**
1480
	 * In some setups, $HTTP_RAW_POST_DATA can be emptied during some IXR_Server paths
1481
	 * since it is passed by reference to various methods.
1482
	 * Capture it here so we can verify the signature later.
1483
	 *
1484
	 * @param Array $methods an array of available XMLRPC methods.
1485
	 * @return Array the same array, since this method doesn't add or remove anything.
1486
	 */
1487
	public function xmlrpc_methods( $methods ) {
1488
		$this->raw_post_data = $GLOBALS['HTTP_RAW_POST_DATA'];
1489
		return $methods;
1490
	}
1491
1492
	/**
1493
	 * Resets the raw post data parameter for testing purposes.
1494
	 */
1495
	public function reset_raw_post_data() {
1496
		$this->raw_post_data = null;
1497
	}
1498
1499
	/**
1500
	 * Registering an additional method.
1501
	 *
1502
	 * @param Array $methods an array of available XMLRPC methods.
1503
	 * @return Array the amended array in case the method is added.
1504
	 */
1505
	public function public_xmlrpc_methods( $methods ) {
1506
		if ( array_key_exists( 'wp.getOptions', $methods ) ) {
1507
			$methods['wp.getOptions'] = array( $this, 'jetpack_getOptions' );
1508
		}
1509
		return $methods;
1510
	}
1511
1512
	/**
1513
	 * Handles a getOptions XMLRPC method call.
1514
	 *
1515
	 * @todo Audit whether we really need to use strings without textdomains.
1516
	 *
1517
	 * @param Array $args method call arguments.
1518
	 * @return an amended XMLRPC server options array.
1519
	 */
1520
	public function jetpack_getOptions( $args ) {
1521
		global $wp_xmlrpc_server;
1522
1523
		$wp_xmlrpc_server->escape( $args );
1524
1525
		$username = $args[1];
1526
		$password = $args[2];
1527
1528
		$user = $wp_xmlrpc_server->login( $username, $password );
1529
		if ( ! $user ) {
1530
			return $wp_xmlrpc_server->error;
1531
		}
1532
1533
		$options   = array();
1534
		$user_data = $this->get_connected_user_data();
1535
		if ( is_array( $user_data ) ) {
1536
			$options['jetpack_user_id']         = array(
1537
				'desc'     => __( 'The WP.com user ID of the connected user' ), // phpcs:ignore WordPress.WP.I18n.MissingArgDomain
1538
				'readonly' => true,
1539
				'value'    => $user_data['ID'],
1540
			);
1541
			$options['jetpack_user_login']      = array(
1542
				'desc'     => __( 'The WP.com username of the connected user' ), // phpcs:ignore WordPress.WP.I18n.MissingArgDomain
1543
				'readonly' => true,
1544
				'value'    => $user_data['login'],
1545
			);
1546
			$options['jetpack_user_email']      = array(
1547
				'desc'     => __( 'The WP.com user email of the connected user' ), // phpcs:ignore WordPress.WP.I18n.MissingArgDomain
1548
				'readonly' => true,
1549
				'value'    => $user_data['email'],
1550
			);
1551
			$options['jetpack_user_site_count'] = array(
1552
				'desc'     => __( 'The number of sites of the connected WP.com user' ), // phpcs:ignore WordPress.WP.I18n.MissingArgDomain
1553
				'readonly' => true,
1554
				'value'    => $user_data['site_count'],
1555
			);
1556
		}
1557
		$wp_xmlrpc_server->blog_options = array_merge( $wp_xmlrpc_server->blog_options, $options );
1558
		$args                           = stripslashes_deep( $args );
1559
		return $wp_xmlrpc_server->wp_getOptions( $args );
1560
	}
1561
1562
	/**
1563
	 * Adds Jetpack-specific options to the output of the XMLRPC options method.
1564
	 *
1565
	 * @todo Audit whether we really need to use strings without textdomains.
1566
	 *
1567
	 * @param Array $options standard Core options.
1568
	 * @return Array amended options.
1569
	 */
1570
	public function xmlrpc_options( $options ) {
1571
		$jetpack_client_id = false;
1572
		if ( $this->is_active() ) {
1573
			$jetpack_client_id = \Jetpack_Options::get_option( 'id' );
1574
		}
1575
		$options['jetpack_version'] = array(
1576
			'desc'     => __( 'Jetpack Plugin Version' ), // phpcs:ignore WordPress.WP.I18n.MissingArgDomain
1577
			'readonly' => true,
1578
			'value'    => Constants::get_constant( 'JETPACK__VERSION' ),
1579
		);
1580
1581
		$options['jetpack_client_id'] = array(
1582
			'desc'     => __( 'The Client ID/WP.com Blog ID of this site' ), // phpcs:ignore WordPress.WP.I18n.MissingArgDomain
1583
			'readonly' => true,
1584
			'value'    => $jetpack_client_id,
1585
		);
1586
		return $options;
1587
	}
1588
1589
	/**
1590
	 * Resets the saved authentication state in between testing requests.
1591
	 */
1592
	public function reset_saved_auth_state() {
1593
		$this->xmlrpc_verification = null;
1594
	}
1595
}
1596