[CSS/JS] Hiding a transparent DIV behind another transparent DIV

So this is a problem which is related to a project I have been working on for a few weeks now and the project itself will be an entire other post of itself but before that I wanted to share a little bit of a CSS workaround I stumbled upon.

The problem is simple, it is hard to hide something behind a DIV with a background that is transparent. z-index does not help here unfortunately and after trying numerous things with little success I ended up with a compromise!

This is the result:

 

And the simple workaround was simply making the DIV go from 0 to 300px using jquery. 

CSS:

#table-wrapper{    position:absolute;

    right:-115px;
    top:115px;
    height:300px;
    width:0px;
    transition:0.5s;
    background-color: rgba(0, 0, 0, 0.2);
}

#table{
    padding-top:10px;
    background-color:none;
    transition:0.5s;
    color:rgba(255, 255, 255, 0);
    font-weight:normal;
    text-align:left;
    font-size:12px;
    border-spacing: 0px;
    border-collapse: separate;
    padding-left:3px;
    float:left;
    width:1px;
    white-space: nowrap;
}

JQuery:

 $('#archive-button').on('click', function(){
       $('#table-wrapper').css('right', '-405px');
       $('#table-wrapper').css('width', '290px');
       $('#table').css('width', '290px');
       $('#table').css('color','rgba(255, 255, 255, 1)');
       $('#archive-button-element').css('transform', 'rotate(90deg)')

 });

No need to hide any DIV's! 

Windows 10 autologon for local accounts on domain connected PC's

This is going to be a quick one. Had to dig way too much online to get a solid answer to this.
The registry change below will configure automatic logon on Windows 10 computers, specifically local accounts on computers connected to a domain.

1. Open regedit and navigate to:
 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

2. Modify the keys below, if you cannot find them create them: Right Click > New > String Value

AutoAdminLogon=1

DefaultDomain=your.domain.name

DefaultUserName=UserName

DeafaultPassword=Password

 3. Done!


- Monkey out.

U-Block Origin on Firefox changing the extension settings via GPO

This tutorial seems like a good way to revive this blog. There is a couple of guides I was able to find online for Chrome but not for Firefox.

Note: This guide assumes you already have a GPO configured to install the U-Block Origin extension on your domain workstations.

Firefox - Creating the Group Policy Object

1. Right click on the GPO and click edit
2. Navigate to Computer Configuration > Preferences > Windows Settings > Registry

3. On the right hand side Right click in the empty area > New > Registry Item
4. Fill out the settings as follows:
Action: Create
Hive: HKEY_LOCAL_MACHINE
Key Path: SOFTWARE\Mozilla\ManagedStorage\uBlock0@raymondhill.net
Value name: Turn on Default
Value type: REG_SZ
Value data: \\path\to\the\file.json

(We are going to create the .json file in the next step)

 Firefox - Creating the .json configuration file

1. Create a .json file in the location you wrote in the previous section of the tutorial
2. Paste the following data into it

{
    "name": "uBlock0@raymondhill.net",
    "description": "ignored",
    "type": "storage",
    "data": {
        "adminSettings":
    }
}

3. Open U-Block and click on settings

4. Modify all the settings as you want them on all your domain workstations, auto-update, whitelist etc.
5. Go to the Settings tab and click Back Up to File at the bottom
6. Open the newly saved .txt file and remove all of the setting lines which you wish to remain configurable by your users
7. Copy the file contents
8. Go to http://raymondhill.net/ublock/adminSetting.html and paste your .txt contents into the top most field
9. Click the downward facing arrow
10. Copy the newly generated contents from the bottom-most field

11. Paste the newly copied line after "adminSettings": in your .json file
12. Save the file
13. You are done!


If you find any errors in the tutorial above please let me know in the comments and I will make sure to update the steps.
 

So 2 motherboards later I finally have a working Esx host, or at least the hardware for one, sort of.
Turns out the NIC the M5A97 R2.0 has onboard is not supported with ESXi which kind of sucks since I wanted to finish the build on the weekend but will now have to wait for the amazon delivery with the NIC instead.

I have returned the MSI board as it turned out to be busted. I picked up the M5A97, which is cheaper and actually posts, the only downside is that its extremely ugly. Light blue on brown, really ASUS?

I will keep this post short as there has not been much else going on. I will probably post my script for the samba setup this week, so there will be more content on this page soon.

M0nkey out.

Esxbox Update

Quick update on my upcoming ESX host project. I have decided to return the motherboard due to me getting an awesome deal on Ebay for the FX 8370. Sadly the board is designed for 95w CPU's, and due to the 125w power hog that is the 8-core FX 8370, this would not be a good pairing.

The replacement board is an MSI 970A Carbon. I decided to get something with an M.2 Drive to run vSphere off of, so this board should do quite nicely.

The CPU will arive next week, and the ram the week after. I am really excited to get this build finished, hopefully everything will go without any hiccups!

M0nkey out.

Tutorial: Creating an NFS Share on Centos 7

This tutorial will cover setting up a shared file directory on CentOS 7 using NFS. The guide will be sharing the directory with a Windows 10 Client.


1. Install the software
yum install nfs-utils libnfsidmap

2. Set the services to start on startup
systemctl enable nfs-server
systemctl enable rpcbind

3. Reboot the server
reboot

4. Select the directory you want to share or create one.
mkdir /nfsdir

5. Set permissions on the NFS shared directory
chmod 777 /nfsdir 

6. Edit the /etc/exports file with the location of your shared NFS directory.
Make sure the IP address is that of the PC you are sharing the directory with.
/nfsdir 192.168.1.3(rw,sync,no_root_squash,no_all_squash)

7. Export the directory
exportfs -r

8. Configure firewall
firewall-cmd --permanent --zone public --add-service mountd

firewall-cmd --permanent --zone public --add-service rpc-bind

firewall-cmd --permanent --zone public --add-service nfs

firewall-cmd --reload

9. Edit /etc/rc.local and add the following lines

systemctl restart nfs-server

mount -a

10. Add Services for NFS to Windows 10.

Search for Turn Windows features on or off in the start menu. 

11. Expand Services for NFS and check off Administrative Tools and Client for NFS

12. After the install reboot your computer

13. Mount the linux share to a network drive. Run the command, where 192.168.1.2 is the address of the Linux server. 

mount 192.168.1.2:\nfsdir z:

Enjoy your new Linux file server!




M0nkey out

Tutorial: Create a WIFI Access Point using Hostapd and a Raspberry Pi

This tutorial will guide you through the steps of converting your Raspberry Pi into a local WiFi Access Point for your network.
Security: WPA2

Note: The AP is for an existing network with working dhcp.

Recommended WiFi dongle: 
EDUP EP-MS1559 11N 300Mbps Wifi Wireless-N USB Adapter.

Is there a specific reason why I am recommending this one? No, not really but it has worked for me without any issues and it provides a strong signal without any drops. 

Also the antenna I am using came from a different dongle, however the one it comes with should do the job just fine. 

If you are going to get a different dongle make sure that it uses the Realtek 8192cu chip, it is possible to get an AP working on a different chipset however this guide is for 8192cu. 


Connect your Pi to your home network via ethernet and plugin the wifi dongle into one of the USB slots.

1.
dmseg | grep 8192cu
usbcore: registered new interface driver rtl8192cu

2.
sudo apt-get install hostapd bridge-utils

3.

wget http://www.daveconroy.com/wp3/wpcontent/uploads/2013/07/hostapd.zip
unzip hostapd.zip 
sudo mv /usr/sbin/hostapd /usr/sbin/hostapd.bak
sudo mv hostapd /usr/sbin/hostapd.edimax 
sudo ln -sf /usr/sbin/hostapd.edimax /usr/sbin/hostapd 
sudo chown root.root /usr/sbin/hostapd 
sudo chmod 755 /usr/sbin/hostapd

The hostapd binary by default does not work with the 8192 chipset however if you replace it with the one above it should work without any issues.

4.

nano /etc/network/interfaces
Edit the file to look like this, modify the IP values to fit your own network.
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.1.18
netmask 255.255.255.0
gateway 192.168.1.1

allow-hotplug wlan0
iface wlan0 inet manual

auto br0
iface br0 inet static
address 192.168.1.252
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1

bridge-ports eth0 wlan0

5. 

nano /etc/hostapd/hostapd.conf

Edit the file to look like this, modify the fields to your requirements.

Generate the wpa-psk string by going to http://jorisvr.nl/wpapsk.html and entering your SSID and password into the generator.

ctrl_interface=/var/run/hostapd

macaddr_acl=0 auth_algs=1

driver=rtl871xdrv

interface=wlan0

bridge=br0

hw_mode=g

ieee80211n=1

wme_enabled=1

channel=4

ssid=Wifi-Name

macaddr_acl=0

auth_algs=1

ignore_broadcast_ssid=0

wpa=2

wpa_psk=4bba27cede6b7ee0a62c8d597dc8fb0b3ff4eebb99a5cd037e5acf4cb4a8

wpa_key_mgmt=WPA-PSK

#wpa_pairwise=TKIP

rsn_pairwise=CCMP

6. 

nano /etc/default/hostapd

Uncomment the line: DAEMON_CONF="/etc/hostapd/hostapd.conf"

This will enable hostapd to start on boot.

7. 

Restart your pi and attempt to connect!

Enjoy your new AP.

M0nkey out.