Google's New Sign In Page UI Design

-

Comments

Post a Comment

Popular posts from this blog

3 Must Haves of a Status Report

-
Image
If you are a project manager, status report is the vital part of your communication to the leadership and audiences interested in your project. The purpose of the status report is not to drive a project with stakeholders. Project planning and driving should be handled separately. Status report has a single purpose, describe the status of the project. That's it. Here are the 3 attributes a status report should have. 1. Brief and Clear A status should be short and well thought. Remember what Mark Twain said, "I didn't have time to write a short letter, so I wrote a long one instead.". If your status report is long and hard to follow, it means you did not think enough on it. If you have not spend time on your status report, why would other people spend more time on your status report to understand. Even worse, if they read and try to decipher what you have written, each person may interpret it differently. Therefore, keep important updates at the top and use clear
Read more

AWS encryption chart (SSE-S3 vs SSE-KMS vs SSE-C)

-
IN TRANSIT AT REST SSL/TLS Server Side Managed Keys Client Side Managed Keys S3 (SSE-S3) Each object is encrypted with a key. Amazon encrypts the key with a master key, which rotates regularly. AWS Key Management Service (SSE-KMS) Allows you to audit trail (who and when used the key), extra cost and you manage the master key. Customer provided (SSE-C) User manages the keys but encryption done by Amazon User encrypts the data on client-side and uploads to S3
Read more

Curl "No status code specified in the response"

-
Sarps-Mac $ curl -vvv -X GET "https://jmd88pxp.execute-api.us-west-2.amazonaws.com/dev/user?limit=10" Note: Unnecessary use of -X or --request, GET is already inferred. *   Trying 54.192.119.190... * Connected to jmd88pxp.execute-api.us-west-2.amazonaws.com (54.192.119.180) port 443 (#0) * TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 * Server certificate: *.execute-api.us-west-2.amazonaws.com * Server certificate: Symantec Class 3 Secure Server CA - G4 * Server certificate: VeriSign Class 3 Public Primary Certification Authority - G5 > GET /dev/user?limit=10 HTTP/1.1 > Host: jmd88pxp.execute-api.us-west-2.amazonaws.com > User-Agent: curl/7.49.1 > Accept: */* >  < HTTP/1.1 502 Bad Gateway < Content-Type: application/json < Content-Length: 36 < Connection: keep-alive < Date: Sun, 18 Dec 2016 00:54:14 GMT < X-Cache: Error from cloudfront < Via: 1.1 66ed69e8b47ad05050331602c798133a.cloud
Read more