| [Desktop Entry] | |
| Name=AoE2 URL Opener | |
| Comment=Play this game on Steam (Open URL) | |
| Exec=/home/<youruser>/.local/bin/aoe2url %u | |
| Icon=steam_icon_813780 | |
| Terminal=false | |
| Type=Application | |
| MimeType=x-scheme-handler/aoe2de; | |
| Categories=Game; |
| --- | |
| blueprint: | |
| name: Z2M - IKEA styrbar (4 button)/Tradfi (On/Off) remote for lights | |
| description: | | |
| Control lights with a: | |
| - IKEA styrbar (4 button) remote [E2001/E2002](https://www.zigbee2mqtt.io/devices/E2001_E2002.html#ikea-e2001%252Fe2002). | |
| - TRADFRI on/off switch [E1743](https://www.zigbee2mqtt.io/devices/E1743.html#ikea-e1743). | |
| There are 3 different features: | |
| - Turn the light group on or off |
This guide is for homelab admins who understand IPv4s well but find setting up IPv6 hard or annoying because things work differently. In some ways, managing an IPv6 network can be simpler than IPv4, one just needs to learn some new concepts and discard some old ones.
Let’s begin.
First of all, there are some concepts that one must unlearn from ipv4:
Concept 1
——————————
This manual is written in German, as I am hardly aware of the FRITZ!Box product outside of Germany. However, should there be any interest in further instructions in English, I will provide these on request.
——————————
| /* | |
| To use in Home Assistant, configure card: | |
| type: 'custom:example-card' | |
| entities: | |
| - switch.wemo_insight | |
| - light.bed_light | |
| - light.ceiling_lights | |
| - light.kitchen_lights |
(Scraped from the Internet Wayback Machine. Original content by Eran Hammer / hueniverse.com July 26, 2012)
They say the road to hell is paved with good intentions. Well, that’s OAuth 2.0.
Last month I reached the painful conclusion that I can no longer be associated with the OAuth 2.0 standard. I resigned my role as lead author and editor, withdraw my name from the specification, and left the working group. Removing my name from a document I have painstakingly labored over for three years and over two dozen drafts was not easy. Deciding to move on from an effort I have led for over five years was agonizing.
There wasn’t a single problem or incident I can point to in order to explain such an extreme move. This is a case of death by a thousand cuts, and as the work was winding down, I’ve found myself reflecting more and more on what we actually accomplished. At the end, I reached the conclusion that OAuth 2.0 is a bad
Recently I came across a web service that required two-factor authentication using the Symantec VIP Access App. I already manage all of my OTP tokens in a different app (If you are on iOS I highly recommend using OTP Auth by Roland Moers.) and did not want to have to use yet another app to generate the TOTP.
There is a way to generate a Symantec VIP Access compatible token very easily if you have access to an environment which can run Python PIP. I happen to have Ubuntu Windows Subsystem Linux running on my machine. (If you are running Windows 10 and don't have this you should really check it out.) Let's get started...
Here we install python3-pip and qrencode so we can generate our secret, I
This document contains excerpts from my web server logs collected over a period of 7 years that shows various kinds of recon and attack vectors.
There were a total of 37.2 million lines of logs out of which 1.1 million unique HTTP requests (Method + URI) were found.
$ sed 's/^.* - - \[.*\] "\(.*\) HTTP\/.*" .*/\1/' access.log > requests.txt
| before_script: | |
| - apt-get update -qq && apt-get install -y -qq pkg-config cmake | |
| - ruby -v | |
| - which ruby | |
| - gem install dandelion --no-ri --no-rdoc | |
| - gem install net-sftp --no-ri --no-rdoc | |
| deploy: | |
| script: | |
| - dandelion deploy $CI_COMMIT_SHA |