Skip to content

Instantly share code, notes, and snippets.

View nckroy's full-sized avatar

Nicole Roy nckroy

View GitHub Profile
@chitchcock
chitchcock / 20111011_SteveYeggeGooglePlatformRant.md
Created October 12, 2011 15:53
Stevey's Google Platforms Rant

Stevey's Google Platforms Rant

I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.

I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real

@jehrhardt
jehrhardt / KeyLengthDetector.java
Created March 15, 2013 06:23
Detect the allowed size of AES keys on the JVM. If the size is <= 256, it is limited. To fix it JCE unlimted stregth files are needed.
import javax.crypto.Cipher;
import java.security.NoSuchAlgorithmException;
public class KeyLengthDetector {
public static void main(String[] args) {
int allowedKeyLength = 0;
try {
allowedKeyLength = Cipher.getMaxAllowedKeyLength("AES");
} catch (NoSuchAlgorithmException e) {
@iay
iay / Aggregator Specification.md
Last active May 4, 2016 23:24
Aggregator Specification

Aggregator Specification

This is a simplified specification for a metadata aggregator with the general capabilities of the eduGAIN service. The specification attempts to make mandatory those aspects of operation which are necessary for the integrity of the service without unnecessarily constraining the metadata which is exchanged through the service.

Upstream Metadata

Upstream Configuration

Information required to configure an upstream channel:

@trscavo
trscavo / cget.sh
Last active January 6, 2020 22:54
Shell script to retrieve a web resource via HTTP Conditional GET
#!/bin/bash
#####################################################################
# Retrieve a web resource via HTTP Conditional GET [RFC 7232] and
# output the resource on stdout. Cache the web resource and consult
# the cache on subsequent requests for the same resource. By default,
# return the cached resource (if it exists) if and only if the web
# server responds with 304 Not Modified.
#
# Usage: cget.sh [-vfcH] URL
@trscavo
trscavo / probe_shib_idps.sh
Last active January 10, 2016 18:54
A bash script that probes a sequence of Shibboleth IdPs to determine which are based on the Shibboleth IdP V2 software
#!/bin/bash
#######################################################################
# Copyright 2015--2016 InCommon, LLC.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
swagger: '2.0'
info:
# Based on http://openvoot.org/protocol/
version: 2.0.0
title: VOOT version 2
host: voot-provider.example.org
basePath: /v2
schemes:
- http
- https
@bsavage
bsavage / voot2swagger2.json
Last active May 4, 2016 20:10
VOOT2 protocol expressed as swagger2 json
{
"swagger": "2.0",
"info": {
"version": "2.0.0",
"title": "VOOT version 2"
},
"host": "voot-provider.example.org",
"basePath": "/v2",
"schemes": [
"http",
@zamzterz
zamzterz / oidc-fed.md
Last active November 8, 2018 04:11
Description of model for federations built using OpenID Connect.

OpenID Connect federation model

All JWS's passed between entities MUST contain the "kid" header parameter to allow explicitly signaling a key change to the recipient. Furthermore, all key id's used by an entity MUST be scoped (to avoid name conflicts) by a unique URI managed by the organization owning the entity. In the same way, all JWK's passed between entities must have a scoped key id.

JWS's in the model:

  • Software statements issued by a federation.
{
"swagger": "2.0",
"schemes": [
"https"
],
"host": "tier.api.edu",
"basePath": "/tier/v2",
"info": {
"contact": {
"email": "tier-api@internet2.edu",
swagger: '2.0'
schemes:
- https
host: tier.api.edu
basePath: /tier/v2
info:
contact:
email: tier-api@internet2.edu
name: TIER API Working Group
url: 'https://spaces.internet2.edu/display/DSAWG'