I’ve read another Nginx book (see my last review here) and this one is all about Nginx’s modular way and what modules are available. It’s called Nginx Module Extension
It starts off with a basic walkthrough on how Nginx is built philosophically with its modularity and takes you through the config of the main module. Pretty basic stuff if you’ve used Nginx before.
Read more…
Here you can generate a cipher that carries many messages depending on the key used.
A so called Deniable Encryption.
Shorter plaintexts will be padded with Z's so they match the length of the longest one.
Enter up to three different plaintexts blow and I'll give you the keys and ciphertext for them.
Just english uppercase letters are valid input, everything else will be removed.
For example, the ciphertext "YUTZANTKJGTZNYYWITDOSPH" can have unlimited (well, not unlimited but you get the idea) number
of solutions. With this key: "TKSFAFLJYYKSNIQRKHQPIHG" it reads "RELEASETHEDRAGONSATDAWN", but with this key: "AUBSMNTQZMHGBQNDRGWLHKS"
it reads "YOURMAMAISAFOOL" (trailing Z's should always be removed. It's just length padding.) and with
this key: "TKASENAJFVHTRCUEHGWLHKS" it reads "RETREATTOBASEASAP".
Pretty cool huh?
Even if this can't be treated as a real One Time Pad since
it theoretically could use the same key twice it's pretty unbreakable afaict. Do you agree?
As always with these kinds of cryptos, the weakness lies in how you pass the key to the receiver.
Enter a cipher and a key to decrypt it.
- Ciphertext
- Key
I like Docker. A lot.
Everything I build and deploy now ends up in their own container on some server/VPS of mine. One reason for this is because of how easy it is to move the site or service to another server if needed. Just export and import the Docker container and you’re done. No config on web and database servers needed, it’s all done.
But there’s one thing you need to do. You can’t have lots of containers listening on the same public port 80, so you have to have your containers listening on some random port like 4553, 4566, 4333 etc. But your site’s visitors are coming to port 80 so you need to somehow listen to port 80 and forward requests to the right Docker container on the right port.
There are several ways to do this and I started out with Nginx as a reverse proxy. This works fine but I don’t want a web server doing that. I’ve used HAProxy in the past for load balancing. And it is actually just what I need, a load balancer is made for forwarding requests.
I recently had to make cross origin AJAX requests (CORS), which was fine since I had control over the API server and simply adding these headers will make modern browsers ask the API server for permission and then make the request.
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: POST,GET,PUT,DELETE
Access-Control-Allow-Headers: Authorization, Lang
But, of course, Internet Explorer want to be a pita and IE 8 & 9 does not support this (a part of it is supported, check out this table). And I have to support IE 9 at least.
So, nginx to the rescue like many times in the past.
Site built with AngularJS and Twitter Bootstrap.
I’m starting to learn Cypher recetly since I’m doing a project backed with a Neo4j database.
One thing I bumped in to recently was a situation like this:
A user can post a link. Users can comment on that link, and on other comments as well. (think reddit).
If someone comments on your link or on one of your comments, you should get an email saying so.
So, we have: (n:user)<-[:POSTED_BY]-(m:link) for the link.
And for the comments we have (n:user)-[:POSTED]->(o:comment)-[:COMMENT]-(m:link)
When you post a link or add a comment, a SUBSCRIBES_TO relation is added. Like this:
(n:user)-[:SUBSCRIBES_TO]->(m:link)
or(n:user)-[:SUBSCRIBES_TO]->(o:comment)
Likes: 17
Nu är det vår!
