Completed
Push — renovate/jest-monorepo ( bd2eaf...d289c3 )
by
unknown
44:07 queued 37:28
created

Manager::setup_xmlrpc_handlers()   C

Complexity

Conditions 12
Paths 52

Size

Total Lines 78

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
cc 12
nc 52
nop 4
dl 0
loc 78
rs 6.0533
c 0
b 0
f 0

How to fix   Long Method    Complexity   

Long Method

Small methods make your code easier to understand, in particular if combined with a good name. Besides, if your method is small, finding a good name is usually much easier.

For example, if you find yourself adding comments to a method's body, this is usually a good sign to extract the commented part to a new method, and use the comment as a starting point when coming up with a good name for this new method.

Commonly applied refactorings include:

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