windows installer – MSI GT60 laptop stuck in endless BIOS Setup loop

My MSI GT60 gaming laptop is doing something very weird. I turned it off to relocate it on top of a 25U server rack and when I turned it on the Aptio setup screen appeared. No matter what I do, it comes back to that. It does see the drives because it can identify them, and it sees all other devices, but I can’t even get a USB stick with Ubuntu to boot (the computer is running 18.04). I have changed everything that might be even remotely related to this in the setup and nothing helps. I made the USB mode hard disk, I tried Legacy, UEFI and UEFI with CSM in the boot mode select, tried choosing different boot devices, but nothing works. I made a boot USB stick with 18.04 with UNetbootin and it doesn’t recognize it in UEFI or Legacy boot mode. Same with the SSD’s. I also tried it with secure boot mode off and on and nothing. Only pressing the Del key at boot has any effect. I also tried removing the battery, pressing the power key for 30 seconds and hoping whatever was the problem would get unstuck, but nothing.

What could possibly be going on here?

configuration – Google AdSense sellers.json setup for multiple domains

I’m struggling to find a good example of sellers.json for Google AdSense.

I checked these pages:

I have multiple domains on which I run ads, all from the same AdSense account.
Now, this page says 1] I have to choose the one that I think is the best and 2] only .com domains are supported.
Both these statements seem weird to me, since:

  1. What if the domains cover different topics, e.g. from cars to health to gambling. Advertisers won’t want to put their ads on a gambling site, but then they will also automtically not show on the health website?
  2. only .com domains are supported? That would mean an extremely large portion of advertisers will be excluded.

I now have this:

"is_confidential": false,

So, should I add an object to the sellers array for each domain on which I run ads and just keep seller_id value the same for all entries?

CTF setup for debugging heap exploits

I’m hope this is the right StackExchange to ask the following question

I’m currently studying binary heap exploitation (mainly the glibc (ptmalloc2) implementation), for CTF competitions. The problem I’m facing is debugging challenges designed for a certain glibc version. I know there are some differences between (for example) libc 2.27 and libc 2.31 that can make the exploitation of certain vulnerabilities harder (or impossible) to exploit on newer versions.

This is a template script I usually like to use (with pwntools):

#!/usr/bin/env python3

from pwn import *

LIBC = ""
HOST = ""
PORT = 9999

if LIBC != "":
    libc = ELF(LIBC, checksec=False)

rop = ROP(exe)

context.binary = exe
context.log_level = "debug"

if "remote" in sys.argv:
    io = remote(HOST, PORT)
    io = gdb.debug((BINARY), gdbscript="""
         b main


This makes debugging locally extremely easy and fast IMO.

I’d like to have a method to easily be able to debug programs using the same (or kind of the same) script as above and using the right glibc (and ld as both are required to be the same version) version without messing with my system’s library.

This might be a rather dumb question but I’ve failed to find any good answer googling around!

Please share your setups for these kind of debugging, I’ll appreciate any help!

Windows 10 setup showing blank/white screen during new installation

I wiped and reinstalled a thinkpad T480 to sell. All good until doing the new setup and I get to this:

Screen just before Account page

Account page – showing a install modal, but a white box where the content should be

The ‘Account’ screen simply displays a white screen with no details. I’ve rebooted many times and gotten the same page. I’ve tried going into recovery mode but the ‘fix my install’ (not sure of wording) option says it can’t do anything.

How can I fix this?

smtp – Not found error in Mail Server setup

I have set up the following configurations in Domain and server settings but I receive this error:

Not Found
HTTP Error 404. The requested resource is not found.


  1. added A record with mail name pointing to server ip.
  2. added MX record mail pointing to server ip.
  3. Installed hMailServer on server.
  4. connected to hMailServer using localhost and administrator account.
  5. added in domains.
  6. added in Setting > SMTP > Delivery of E-mail > local host name.
  7. added port 25 to firewall incoming rules.

Foot note: the domain is properly defined on IIS and is working when I try

bitcoind – How can I setup Bitcoin to be anonymous with Tor?

This is not a thorough schooling on Tor and only shows how to configure it to work together with Bitcoin Core.

Bitcoin Core includes Tor integration

When Tor is correctly setup on your system, Bitcoin Core automatically identifies Tor and creates an anonymous service. Little configuration is required to be ‘off the grid’ and, just a tiny bit more to be completely anonymous if that is important to you, with none of your Bitcoin traffic reaching out onto the public internet.

Using these steps you can be anonymous in only five minutes.

With the full privacy setup, transactions will of course still be broadcast but will only be broadcast actually onto the public internet by other Bitcoin nodes. With the standard ‘off-the-grid’ Tor setup, your Bitcoin traffic will be routed through the anonymous Tor network before reaching the public internet and other Bitcoin nodes on and off the Tor network to be effectively untraceable.

Setting Up Bitcoin Core and Tor

These instructions work on Fedora 23>29 and assume a default setup of Bitcoin Core v0.15.1 and Tor v0.2.7.1 or newer (and have been tested to work with Bitcoin Core v0.16.0 on Fedora 27 with Tor v0.3.1.9). Fedora is a modern operating system that will run on most standard modern hardware. The configuration is the same on Windows, but the instructions are different. There are some instructions for setting up Tor on Windows here.

Further instructions for other *nix based systems are available here. NOTE: You do not need to configure your Tor client as a relay or exit node for Tor to operate, so you can skip the step for ‘Put the configuration file /etc/tor/torrc place:’ in that guide. You will still need to use all of the following steps in this guide.

  1. Setup Tor

    1. Install the tor package:

      sudo dnf install tor
    2. Start the tor daemon and make sure it starts at boot:

      sudo systemctl enable tor
      sudo systemctl start tor
  2. Figure out where your torrc file is (/etc/tor/torrc is one possibility).

  3. Open the torrc file to edit:

    xhost +local: ## skip if earlier than v29 only needed for Wayland
    sudo gedit /etc/tor/torrc


    sudo nano /etc/tor/torrc
  4. Add these lines to your torrc (or ensure that they are uncommented):

    ControlPort 9051
    CookieAuthentication 1
    CookieAuthFileGroupReadable 1
  5. You need to figure out what group tor is using. On Fedora 23 it is toranon. Run the following command:

    ps -eo user,group,comm |egrep 'tor' |awk '{print "tor group: " $2}'
  6. You need to figure out what user bitcoind or bitcoin-qt is running as. Run the following command while Bitcoin is running:

    ps -eo user,group,comm |egrep 'bitcoind|bitcoin-qt' |awk '{print "Bitcoin user: " $1}'
  7. Run the following command as root, which adds your Bitcoin user to the tor group. Replace TOR_GROUP and BITCOIN_USER with the actual information found above:

    sudo usermod -a -G TOR_GROUP BITCOIN_USER

If you don’t modify any other settings, Bitcoin Core will usually connect over the regular Internet, but will also allow connections to and from the hidden Tor service.

  1. So that Bitcoin Core wil only connect via Tor (for standard ‘off-the-grid’ setup), add these lines to bitcoin.conf. In Bitcoin Core, go to Settings -> Options -> Open Configuration File. Bitcoin Core uses Tor stream isolation by default:

    proxy= #If you use Windows, this could possibly be in some cases.
  2. (optional) If you like, you can add some onion service peer nodes to connect to. This will help especially if you do all of the following optional configurations. Add the following lines to your bitcoin.conf file. Bitcoin Core will only connect to a maximum of eight of these at any one time randomly, depending which ones are online:

    #Add seed nodes
    #And/or add some nodes

If you additionally want Bitcoin Core to only connect out to Tor hidden services and not even to connect to IPv4/IPv6 nodes on the public internet via the Tor network proxy:

  1. (optional) Also add this to bitcoin.conf for full anonymity (not particularly recommended)*:


*Note: Bitcoin Core will still query for peer addresses via DNS lookup if low on addresses. This also can be disabled using the next option. However, it is possible your node may not be able to find any other nodes to connect to.

*Note: Bitcoin Core v0.15.1 currently seems to make some outbound IPv4 connections at node startup even when onlynet=onion, none have been observed after initial startup. These connections should be made via your onion proxy, however, using the next option has been observed to prevent them.

  1. (optional) (advanced) If you also want to disable DNS lookup to query for peer addresses then also add the following to bitcoin.conf (not particularly recommended) note: if you use this option your node may be unable to find peers until you add some good peers with the addnode= parameter.:

  2. Restart tor:

    sudo systemctl stop tor
    sudo systemctl start tor
  3. Log out of your user, log back in (this is so that your new user group permissions are effective, I do not know what user you are running Bitcoin Core on).

  4. Restart Bitcoin Core. Since Tor version and newer the Bitcoin Core GUI version called bitcoin-qt automatically registers your Tor hidden service and makes it reachable on the onion network. For the command line version of Bitcoin Core, bitcoind, add the following parameter to your command line:

    >bitcoind -listenonion

No port forwarding is necessary for everything to work with Tor including incoming connections via the Tor hidden service, you do not need to forward any ports for Bitcoin Core or Tor for this.

If you want your Bitcoin node still publicly reachable via the public internet for incoming connections you will still need to forward port 8333 for Bitcoin Core.

Checking everything is working

There are only two things to check that all is working. Checking peer info in the debug window of bitcoin-qt, you should see that connections to IPv4/IPv6 peers now have some extra connected ‘via’ info along with the peer address when you click on a peer. Onion addresses only route via Tor.

Checking the same thing via console or CLI for getnetworkinfo, you should see for each network type the proxy info and, checking with getpeerinfo you should see that the addrlocal info is a remote address for each peer. Onion peers do not have addrlocal and just have their onion service name for addr.

The second thing to check is that your onion service for inbound Tor connections is up and all configuration is in place. Have a look in your debug.log file, you should see a few entries after the most recent node restart that match the following:

2018-02-10 06:31:48 InitParameterInteraction: parameter interaction: -proxy set -> setting -upnp=0
2018-02-10 06:31:48 InitParameterInteraction: parameter interaction: -proxy set -> setting -discover=0
2018-02-10 06:32:13 Bound to
2018-02-10 06:32:13 torcontrol thread start
2018-02-10 06:32:13 tor: Got service ID {onion}, advertising service {onion}.onion:8333
2018-02-10 06:32:13 AddLocal({onion}.onion:8333,4)

The advertising service information is your onion service address.

In the debug.log, connections to onion peers will only look like the following but still show up in the peers tab of the debug window on bitcoin-qt:

2018-02-10 06:34:07 receive version message: /Satoshi:0.15.1/: version 70015, blocks=508469, us=(::):0, peer=7

It is not necessary to configure port forwarding on your modem/router for Tor to operate. If you are behind a restrictive firewall it may be necessary to configure outbound connections to allow Tor to connect out to other Tor nodes. Tor can be configured to only connect out using port 80/443 if that helps. See Appendix 1 – Monitoring Tor for nyx and access to full Tor configuration options.

It is difficult to be completely anonymous since the sender and the receiver know, however, you can obfuscate your transaction origin so that your data cannot be traced by IP address without breaching the Tor network. Do some research, onlynet=onion is more secure.

Additionally, there has been research(1)(2) done on graphing the blockchain in an attempt to trace all BTC to their origin, potentially identifying source<-wallet<-purchase and depending on the combination of UTXOs potentially identifying wallet balances or wallet balance subsets. Data linkage is a privacy issue we may all be concerned about, this article discusses the use of bitcoin mixers, and this series of tweets.

Done! Enjoy being anonymous!

Appendix 1 – Monitoring Tor

You can monitor (and further tweak/break) Tor using nyx.

There are several installation methods available. On Fedora 27:

sudo dnf install nyx

To start nyx simply type nyx in the console and it will connect to Tor if it is running.


Once correctly configured, most synchronisation issues are to do with your hardware. See this answer for more information.

There are more configuration options available, and additional ways you can support the Tor network. Please see the several pages available here for information.

Thanks to for your excellent guide that got me started on this.

Additional information is available from the bitcoin project here.

For an even higher level of anonymity, it is possible to configure Tor as a DNS resolver and, configure your system network configuration to use Tor to resolve DNS queries.

*by default, Tor will participate in the Tor network.

Magento bitnami linux Setup Varnish

I want to configure and use :
for Magento in bitnami Linux

How to setup Pingdom on your Magemto 2 sites

I want to set up Pingdom for our Magento 2 sites.

I have seen they need a script just above of the site. but we have multiple stores so how would that work and where do i put the script (what file?)

Any suggestion are appreciated.

Facebook Marketplace setup – security keeps sending me a 6 digit code instead of a 5 digit one

I am trying to set up a Facebook marketplace account but it keeps sending me a 6 digit code but there is only space for 5 digits. Anyone know how to fix this?