enygma

<?php

interface Subject
{
	public function getIdentifier();
	public function getCredential();
}

interface Enforcer
{

enygma

<?php

namespace App\Providers;

use Blade;
use Illuminate\Support\ServiceProvider;

class PropAuthBladeServiceProvider extends ServiceProvider
{
	/**

enygma

<?php

// First, our service provider defining the policies
<?php

namespace App\Providers;

use Illuminate\Support\ServiceProvider;
use Psecio\PropAuth\Enforcer;
use Psecio\PropAuth\Policy;

enygma

<?php
require_once 'vendor/autoload.php';

use \Psecio\PropAuth\Enforcer;
use \Psecio\PropAuth\User;
use \Psecio\PropAuth\Policy;
use \Psecio\PropAuth\PolicySet;


//---------------------------

enygma

Chriss-MacBook-Pro:laravel ccornutt$ composer require psecio/gatekeeper
Using version ^2.6 for psecio/gatekeeper
./composer.json has been updated
> php artisan clear-compiled
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for vlucas/phpdotenv == 1.1.1.0 -> satisfiable by vlucas/phpdotenv[v1.1.1].

enygma

Late yesterday afternoon the PSR-9 and PSR-10 drafts were moved into master on the <a href="https://github.com/php-fig/fig-standards/" title="PHP-FIG Standards">php-fig/standards</a> repository, moving them along to the next step and to get the wider perspective of the main PHP-FIG group's opinions on it.

What are <b>PSR-9</b> and <b>PSR-10</b>, you ask? Here's a brief summary so far:

At the end of last year (2014) <i>Lukas Smith</i> <a href="https://groups.google.com/d/msg/php-fig/45AIj5bPHJ4/ThERB43j-u8J">made a proposal</a> to the PHP-FIG group for a standard that would make reporting security issues with PHP projects and libraries a much more structured thing. The general idea is that a standardized document (or documents?) in a project's repository would provide information about current and past security issues in a well-defined structure that could have some automated tooling around it. <a href="https://groups.google.com/forum/#!searchin/php-fig/security/php-fig/45AIj5bPHJ4/ThERB43j-u8J">Much discuss

enygma

$url = '/wsapi/2.0/verify?'.http_build_query($params).'&h='.$signature;

        // Make the connections in a pool
        $pool = array();
        $client = new \Guzzle\Http\Client();

        foreach ($this->hosts as $host) {
            $pool[] = $client->get('http://'.$host.$url);
        }
        $responses = $client->send($pool, array(

enygma

Keybase proof

I hereby claim:

• I am enygma on github.
• I am ccornutt (https://keybase.io/ccornutt) on keybase.
• I have a public key whose fingerprint is BA43 E518 8775 24EF ECC2 6831 D67D 8542 2535 DF94

To claim this, I am signing this object:

enygma

 Executing step: Check out the repository
   When directory "my-repo" does not exist
 	And I git clone "git.internal:/opt/git/my-repo"
 	>> Cloning into 'my-repo'...
 	Then change to directory "my-repo"
 	Then execute "pwd"
 	>> /Users/chris/work/picklebuild/my-repo
 	Then git checkout "release"
 	>> Switched to a new branch 'release'
 	>> Branch release set up to track remote branch release from origin.

enygma

<?php
/**
 * When using Guzzle with self-signed certs, something recently changed that makes the
 * previous manual config no longer work...see below
 */

// this no longer works
$init = array(
    'curl.CURLOPT_SSL_VERIFYHOST' => false,
    'curl.CURLOPT_SSL_VERIFYPEER' => false,