HN user

guac

52 karma
Posts0
Comments17
View on HN
No posts found.

This seems to explain why my Mac was nearly unusable after a reboot last week. Turns out bind crashed on my firewall leaving me with no DNS.

After I restarted it I could actually launch apps other than terminal again.

That's standard practice with USAA. My first few checks had a pending status but after that (100s of checks later) they all posted immediately. Same thing happened when I signed up my wife. It's a selling point of USAA.

My paycheck also posts immediately, I get "paid" Thursday while everyone else I work with gets it Friday.

Unix Toolbox 11 years ago

If you have homebrew you can just install the 'gnu-sed' package and then change the function to call 'gsed' instead.

How about this: http://jsfiddle.net/pJ8Mt/1/

It's a poor example since I couldn't think of anything useful off the top of my head but it shows how you might modify a service at config time by creating its provider yourself.

Also I believe .config executes immediately so the provider needs to be defined beforehand (in this case above .config, but probably better to define it in another module to ensure it's available at config time). When I defined it after .config angular complained it couldn't find awesomeProvider.

> Constants are especially interesting because they can be injected into the .config function of a module. No other provider can be injected for the very good reason that .config cannot inject transitive dependencies.

It should be noted than you can inject providers themselves in .config. Most users do this with built-in $routeProvider (which provides $route).

It's not mentioned in the post but he could pass "awesomeProvider" into module.config and (if it was more interesting than just a $get method) do something with it during the config phase.

With $routeProvider you would use the .when method to configure angular routing. It's .$get method returns the $route instance.

Even if you aren't storing card information you still are subject to PCI compliance if the card information passes through your application/server. In the case where you are processing but not storing you would need to complete the SAQ-C questionnaire and still probably be subject to quarterly scans (the self-assessment where are you storing data is SAQ-D)

https://www.pcisecuritystandards.org/merchants/self_assessme...

I believe the "premium" ones are extended validation (EV) certificates. These give the green bar on newer browsers.

The $12 ones just validate domain ownership and not organization identity. I believe they also ignore the Organization and Organizational unit fields in your CSR and replace it with the common name in the certificate they issue.

For the proxy thing you may want to configure your applications to proxy DNS requests as well. Some do not do it by default and would leak the hostnames you're connecting to.

In firefox the about:config variable is "network.proxy.socks_remote_dns". Set it to true.