shoeper

Run cmd.exe as Administrator and execute the following command:

When your search doesn't work and Windows troubleshooting says the permissions are wrong, but cannot fix it, run the following command to fix the permissions and your search probably works, again (immediately).

takeown.exe /R /F C:\ProgramData\Microsoft\Search\

if it still doesn't work run

takeown.exe /R /F C:\ProgramData\Microsoft\

shoeper

#!/bin/bash

: <<'COMMENT'

This script takes the dataset from the Open Thesaurus project and 
transforms it to a wordlist comparable to the original diceware list. 
I thought the original list contains too much lines which just don't 
make any sense and/or are hard to memorize. So my goal was to 
automatically generate a list containing only memorable words, which 
can then be used to add your own special characters or variations. 

shoeper

#!/bin/bash

: <<'COMMENT'

This script takes the dataset from the Open Thesaurus project and 
transforms it to a wordlist comparable to the original diceware list. 
I thought the original list contains too much lines which just don't 
make any sense and/or are hard to memorize. So my goal was to 
automatically generate a list containing only memorable words, which 
can then be used to add your own special characters or variations. 

shoeper

Don't use VPN services.

No, seriously, don't. You're probably reading this because you've asked what VPN service to use, and this is the answer.

Note: The content in this post does not apply to using VPN for their intended purpose; that is, as a virtual private (internal) network. It only applies to using it as a glorified proxy, which is what every third-party "VPN provider" does.

A Russian translation of this article can be found here, contributed by Timur Demin. There's also this article about VPN services, which is honestly better written (and has more cat pictures!) than my article.

Why not?

shoeper

2019/08/05 10:43:15 [WARN] ▶ Image [docker.seadrive.org/seafileltd/seafile-pro:latest] contains 325 total vulnerabilities
2019/08/05 10:43:15 [ERRO] ▶ Image [docker.seadrive.org/seafileltd/seafile-pro:latest] contains 325 unapproved vulnerabilities
+------------+-----------------------------+---------------------+-------------------------------+------------------------------------------------------------------+
| STATUS     | CVE SEVERITY                | PACKAGE NAME        | PACKAGE VERSION               | CVE DESCRIPTION                                                  |
+------------+-----------------------------+---------------------+-------------------------------+------------------------------------------------------------------+
| Unapproved | High CVE-2018-16865         | systemd             | 237-3ubuntu10.3               | An allocation of memory without limits, that could result        |
|            |                             |                     |                               | in the stack

shoeper

<domain log-root="${com.sun.aas.instanceRoot}/logs" application-root="${com.sun.aas.instanceRoot}/applications" version="89">
  <security-configurations>
    <authentication-service default="true" name="adminAuth" use-password-credential="true">
      <security-provider name="spcrealm" type="LoginModule" provider-name="adminSpc">
        <login-module-config name="adminSpecialLM" control-flag="sufficient" module-class="com.sun.enterprise.admin.util.AdminLoginModule">
          <property name="config" value="server-config"></property>
          <property name="auth-realm" value="admin-realm"></property>
        </login-module-config>
      </security-provider>
      <security-provider name="filerealm" type="LoginModule" provider-name="adminFile">

shoeper

# I had a bit of trouble getting my unifi controller (hosted offsite) to use a proxy/letsencrypt. So here are the fruits of my labor. 
# The unifi default port is 8443 running on localhost. 

# License: CC0 (Public Domain)

server {
        # SSL configuration
        #
        listen 443 ssl default_server;
        listen [::]:443 ssl default_server;

shoeper

Enable Docker Remote API with TLS client verification

Docker's Remote API can be secured via TLS and client certificate verification.
First of all you need a few certificates and keys:

• CA certificate
• Server certificate
• Server key
• Client certificate
• Client key

Create certificate files

shoeper

import requests
import hashlib
import time
import uuid
import os
import copy
import json

# Fixed up version of my previous code to work with the Cloud endpoints.
# Hopefully this works.

shoeper

import requests
import hashlib
import time
import uuid
import os
import copy
import json

# This is based on my personal implementation but stripped down to only what is
# needed to verify it.