build: enforce minimum required Windows version (7) by ...

BiblePay (BBP)

BiblePay (BBP) is a Charity Christian Cryptocurrency that donates 10% of coins to Charity every month, sponsoring orphans
[link]

TiPS (FedoraCoin): The Official Subreddit!

TiPS (a.k.a. FedoraCoin) is a new state of the art cryptocoin based on the [Tips Fedora meme](http://knowyourmeme.com/memes/tips-fedora). Our objective is to become the tipping currency of the internet. More information is available in the [BitcoinTalk thread](https://bitcointalk.org/index.php?topic=1420302.0).
[link]

Unify Cryptocurrency

This is the place to go for anything UnifyCoin related! Things like news, updates, bounties, important links, testimonials, tips & tricks, guides and let's not forget... Unify memes!
[link]

Bitcoin Fullnode Install Guide for Dummies ;-)

Bitcoin Fullnode Install Guide for Dummies ;-)
Feel free to stop at Level 0 or Level 1, which is fine. More advanced configs are offered to those with more tech savvy. This guide, obviously assumes a Windows 10 install, but other OSes work fine, just find a different guide. BTW, the "For Dummies" is a callback to a set of "tech" books in the 90's intended to be as easy as possible. It is in jest and not intended to insult the reader. Finally, if you dislike the formatting, a well formatted copy can be found here
There is a fairly small subset of Bitcoin users that run a full node. I think the idea of running a full node has gotten a bad rap over the years since there is so much talk about running on a Raspberry Pi, or getting zippy SSDs. Although all of this can be fun, it is often not really required at all. Here are some ways to run a full node starting with the very simple. I'll get into more complex configs, but these are all optional.

Tech Skill Level: 0 (the basics)

  1. Download Bitcoin Core
  2. Launch the downloaded installer and install the app
  3. Launch the installed "Bitcoin Core" app and let it run overnight
In many cases, thats it. If your running a new machine with a fairly good internet connection, 8 or 9 hours will be enough to complete the "Initial Block Download" (IBD). This may fill up your drive a bit, but again, on most new machines, 300 GB of space isn't that hard to come by.

Tech Skill Level: 1 (encrypted wallet)

One thing we left out in the level-0 exercise is encrypting your wallet. It's easy enough to do well, but a bit more difficult to do right. The main challenge is that humans generate really poor passwords. If you want a good password, the best way is to use something called "diceware". Basically, you just grab 4 or 5 dice and each throw of the dice represents a certain word on a special list. The throw {1,4,5,3,1} for example would be the word camping on the EFF-diceware-wordlist. So you repeat this a few times until you have a list of 8 or so words which becomes the passphrase you use to encrypt your wallet. Write it down, it is always hard to remember at first. So at level-1 your list becomes:
  1. Download Bitcoin Core
  2. Launch the downloaded installer and install the app
  3. Launch the installed "Bitcoin Core" app and let it run overnight
  4. Choose Encrypt Wallet from the Settings menu
  5. Enter your 8 word (or so) passphrase generated using the Diceware method

Wallet Encryption Dialog

Tech Skill Level: 2 (enable pruning if needed)

Though I said "300 GB of space isn't hard to come by", some times it actually is. If space is an issue, a simple way to fix it is to tell bitcoin to simple take less space. This is called "pruning" and can take that number from 300 GB down to below 5 GB. If you can't find 5 GB, then you'll have to read ahead to level-4 to add USB storage. But the good news is, enabling pruning is pretty easy, we just add another step to our working list:
  1. Download Bitcoin Core
  2. Launch the downloaded installer and install the app
  3. Launch the installed "Bitcoin Core" app and let it run overnight
  4. Do the wallet encryption steps here if you wish
  5. Choose Options from the Settings menu
  6. Choose Prune block storage to: and select the max size for the blocks to use
  7. Exit and restart the bitcoin application for the changes to take effect

Pruning Dialog
Note, even setting this to 1 GB will still leave you with about a 4.5 GB install. The blocks take up a lot of space, but the chainstate and other folders eat up at least 3.5 GB and they can't be pruned. Also, be aware, to disable pruning requires you to perform the entire IBD again. While pruned some other functions my be disabled as well, so just know that pruning does limit some functionality.

Tech Skill Level: 3 (verify the installer)

Although this is arguably something that should be done at level-0, some find the intricacies of comparing hash (thumbprint) values to be tedious and beyond the scope of a beginner. You will find these types of hash compares suggested quite often as a way to prevent running tainted programs. Programs are often tainted by bad disk or network performance, but most often, taint is malicious code inserted by viruses or malware. This is a way to guard yourself against those types of attacks.
What I cover here is a very basic comparison on the certificate, but a more thorough verification advised by mosts uses a program called Gpg4Win, and is beyond the scope of this beginners guide. But regardless, most users should strive to do this minimum level of validation.
  1. Download Bitcoin Core
  2. Launch the downloaded installer
  3. When prompted "Do you want to allow..." click Show more details
  4. In the details section select Show information about the publisher's certificate
  5. In the certificate window select the Details tab
  6. In the Details tab Subject should start with "CN = Bitcoin Core Code Signing Association"
  7. Ensure Thumbprint in Details reads ea27d3cefb3eb715ed214176a5d027e01ba1ee86
  8. If the checks pass, click OK to exit the certificate window and Yes to allow the installer to run.
  9. Launch the installed "Bitcoin Core" app and let it run overnight
  10. Do the wallet encryption steps here if you wish
  11. Do the optional pruning steps here if you wish

Certification Validation Windows
Note: The certificate used to sign the current Bitcoin installer is only valid from March 2020 to March 2021. After that point the thumbprint on the certificate will change. This is by design and intentional. If your reading this post after March 2021, then it is understood that the thumbprint has changed.

Tech Skill Level: 4 (use secondary storage)

We glossed over the "new machine with fairly good internet" part. Truth be known many people do not have fairly new machines, and find the IBD to take longer than the "over night" best wishes. For most people the slowdown is the disk access when calculating what is called chainstate. This requires fast random reads and writes to the disk. If you have an SSD disk, this will be no problem, but if you have a non-SSD "spinning" disk, random writes are always slow. Though an SSD will speed things up, they are pricey, so a nice middle ground may be a simple high-end USB key drive. You can get some with 10 to 15 MB/s random writes for $20 on Amazon. This is usually a order of magnitude faster than a "spinning" disk. And with pruning (see level-2), a small USB drive should be fine.
Once you decide on a drive, the tricky part will be to enable external storage. It requires editing a configuration file and adding a line. First, we want to create a directory on the key drive. You will need to determine the drive letter of your USB key drive. For the sake of this example, we will assume it is D:, but you must determine this yourself and correct the example. Once you know the drive letter, create a blank folder on the drive called Bitcoin. So for this example, creating Bitcoin on drive D: will create the path D:\Bitcoin. Once done, assuming that D: is your drive, here are the new steps including the edit of the configuration file:
  1. Download Bitcoin Core
  2. Launch the installer, verify it, then run it
  3. Launch the installed "Bitcoin Core" app and let it run overnight
  4. Do the wallet encryption steps here if you wish
  5. Do the optional pruning steps here if you wish
  6. Launch "Notepad" by typing "Notepad.exe" in the windows search bar then click Open
  7. Type the line datadir=D:\Bitcoin (depending on your drive letter) in the blank file
  8. Choose Save from the File menu in notepad
  9. Type %APPDATA%\Bitcoin\bitcoin.conf (note the percent signs) in the File name box
  10. Select All Files from the Save as type dropdown
  11. Click the Save button and overwrite the file if prompted
  12. Exit and restart the bitcoin application for the changes to take effect

Save As Dialog
Now that you've reached this level of technical expertise, there are many new configuration options that you can begin to modify if you wish. Most configuration data is contained in the bitcoin.conf file and learning how to maintain it is a key step for a node operator.

Tech Skill Level: 5 (all other customizations)

Here's a short list of various things you can ADD to your bitcoin.conf file. You generally just add a new line for each configuration settings.
  • addresstype=bech32
  • changetype=bech32
The addresstype / changetype allows your wallet to use the native-segwit (bech32) format. This is the most efficient and inexpensive way to spend bitcoin, and is a recommended configuration. The default uses something called p2sh-segwit which is more compatible with older wallets, but more expensive to spend.
  • minrelaytxfee=0.00000011
Changing the minrelaytxfee setting allows you to help propagate lower fee transactions. It will require more memory but TXN memory is capped at 300 MB by default anyways, so if you have enough memory, it is a good setting to choose.
  • dbcache=2048
The dbcache setting controls how many MB of memory the program will use for the chainstate database. Since this is a key bottleneck in the IBD, setting this value high (2048 MB) will greatly speed up the IBD, assuming you have the memory to spare
  • blocksdir=C:\Bitcoin
  • datadir=D:\Bitcoin
In level-4 we discussed moving the datadir to a fast external storage, but the majority of the space used for bitcoin is the blocks directory (blocksdir). Although you should always use for fastest storage for datadir, you are free to use slow storage for blocksdir. So if you only want to consume a small amount of your SSD (assumed D:) then you can keep your blocks on your slow "spinning" drive.
  • upnp=1
One of the harder challenges you may face running a node, is to get incoming connections. If you are lucky, you may find that your firewall and network HW support the uPnP protocol. If they do, this setting will allow bitcoin to configure uPnP to allow incoming connections to your node. Other methods exist to make your node reachable, but they are well beyond the scope of this guide.
submitted by brianddk to Bitcoin [link] [comments]

PSA: Enable Tor as a simple way to make your node reachable.

Become one of the 10% of node operators that receive incoming connections.
Installing bitcoin core is easy, and with pruning it really isn't the space sink it is characterized as. Even a modest computer can complete the initial block download (IBD) and become a full node. But what some users (90%) find a bit more challenging, is how to become a listening node. Listening nodes are an important part of the network, and are simple enough to enable. I can think of 4 ways to do it:
  1. Operate on an OS and Network that support uPnP, allowing bitcoin to open the ports for you.
  2. Subscribe to a VPN that allows you to open ports through their service.
  3. Manually configure your OS and network to forward port 8333 and 18333.
  4. Run Tor and direct bitcoin to listen through it.
I'll discuss #4. Obviously #1 or #2 are easier, but require a VPN subscription or uPnP enabled HW. And if you live in a dorm or don't control the network, Tor may be the only free option available.
As a bit of background, bitcoin supports three networks that your node can listen on:
Obviously, the more you enable, the better, but here are the basic steps for Tor in broad strokes. If you have any questions post them here and I'll see if we can't help you out:
  1. Download, verify1 and install Gpg4win
  2. Download, verify2, install, and launch Tor Browser
  3. Download, verify3, install, and launch Bitcoin Core
  4. Launch and Admin command console in the directory containing tor.exe
  5. Install the Tor service: tor.exe --service install
  6. CD to service dir: cd %windir%\ServiceProfiles\LocalService\AppData\Roaming\tor
  7. Create and edit a file called torrc with the contents suggested below
  8. Restart tor: tor.exe --service stop && tor.exe --service start
  9. Record the hostname: type .\HiddenService\hostname as
  10. Add the bitcoin.conf options suggested below
  11. Restart the bitcoin-qt program
  12. (Optional) Activate the bitnodes crawler at https://bitnodes.io/nodes/-8333/
It may take a while for your node to show up on bitnodes. I've found the check button sometimes has trouble with onions. Of course you don't need to do it, but it can provide a simple way to check status once your on the list.

torrc file: (replace c:\windows with the proper path as needed)

```

Change to C:\Windows\ServiceProfiles\LocalService\AppData\Roaming

Log notice file \tor\service.log

Bridges may be needed if the Gov't shuts down Tor exit nodes. Get Bridges by

emailing [email protected] from Gmail (only) and uncomment as follows:

Bridge obfs4 : cert= iat-mode=

HiddenServiceDir \tor\HiddenService HiddenServiceVersion 2 HiddenServicePort 8333 127.0.0.1:8333 HiddenServicePort 18333 127.0.0.1:18333 ```

bitcoin.conf file: (entries to be ADDED)

```

Change to what you recorded earlier

onion=127.0.0.1:9050 listen=1 externalip= discover=1 ```
Footnotes:
  • 1 Cert: {Subject: Intevation GmbH; SHA1: c13a65963ad53e78694dd223d518007791a05fe4}
  • 2 PGP Signing Key: 0xEF6E286DDA85EA2A4BA7DE684E2C6E8793298290
  • 3 PGP Signing Key: 0x01EA5486DE18A882D4C2684590C8019E36C2E964
submitted by brianddk to Bitcoin [link] [comments]

Checker Thread (A list of hacked clients for easy reference)

Community contribution is the only way this thread will be useful. This is a WIP! More clients will be added as time goes on!
Quick note: The vast majority of these are files supplied by the community -- some may not work. The person who sent me 9b9t says it doesn't work, but I have not personally tested. Please let me know if it works or does not work.

Some additional notes:
I am open to community criticism so long as it can actually be used to benefit the thread. Issues with formatting, approach, client choice, etc. are all great things to come talk to me about so I may improve. However, people keep commenting the same things over and over and over — “VirusTotal can’t catch X” is a popular one — and I don’t have time to deal with it. If you have a security concern, you are more than welcome to raise it. HOWEVER, do not make unreasonable requests of me — I work, in addition to that I have a social life, I have responsibilities at home as well. This is a side thing that I do when I have the time. A lot of people have suggested looking through bytecode to determine if a client is malicious. I do not have the time to do this for every client. If you are willing to help and do more than say “you should do more than you already are, even though you have a job and a life outside of an obscure subreddit,” feel free to DM me. People who take the broken record approach and say things that are already covered in the thread, or refuse to offer help and just post complaints, will be blocked and ignored. I’m all down for making this post better, but I’m not gonna waste my time with people who won’t work with me. Thank you for your help!

BIG THANKS TO u/jpie726 FOR HIS MASSIVE CONTRIBUTIONS! WITHOUT HIM THIS LIST WOULD BE SIGNIFICANTLY LESS EXPANSIVE. GO UPVOTE THIS MAN INTO HEAVEN, HE DESERVES IT!

Eventually I would like to make a Python script that takes care of all the necessary tasks to install these clients. Python itself is available through the Windows Store as well as on Python's website, or through various other installers. It will install any additional dependencies via Pip and will use Curl to retrieve the files. Anyone interested in helping with this script is more than welcome to do so, if you wish. The two options for assisting me would be as follows:
1. You can install Visual Studio Code or Atom and work with me directly through those applications (more details soon™)
2. A GitHub page may be made and you could submit pull requests through that and edit the script alone.

#######################################################################
There is a misconception that I am only here for free paid clients.
1. I can't use a paid client unless I have access to a cracked version, an account, and the HWID bound to said account.
2. People are also saying there's a way for clients to track if someone leaks them. While I suppose this is possible if they bothered to put in the absurd amount of effort it would take, it would give them no benefit and it would do no good as I am not running the software on my desktop -- I am sending the software to VirusTotal, grabbing the SHA-256 checksum, and deleting the file.
3. If all you're going to do is post that "VirusTotal can't catch x" or "muh client" do not waste my time, and don't waste yours. You will be ignored in favor of people who will actually help me construct what I hope to be a megathread for this subreddit, FOR YOU GUYS. I mean jeez, someone's trying to help and half the fucking responses are "muh client" like come on. No wonder this fucking subreddit is dead, sheesh. If someone's trying to help you and you just step on their toes that's just not very cool, not everyone is trying to scam you. I do just be trying to help people who come here doe.
4. If you have concerns, raise them respectfully. Do not attack me, you will be ignored or if I feel so inclined I will give you 110% of the shit you give me right back to you. I will answer questions, I will elaborate on my goals, I will take helpful advice. Everything else will be outright ignored, and misinformation will be countered. That is all, thread below.
#######################################################################

I named this the Checker Thread to make it easy to search for in the subreddit. Enjoy.Below will be a list of hacked clients, with VirusTotal links, SHA-256 hashes, direct download links (skipping ad pages) and eventually features for each client. I'd also like to add what servers they do and don't work on, but I need the community to help with that.
The only client I use is Impact, send me additional clients in the comments and they will be added to this list.

Note about SHA-256 hashes:
SHA-256 hashes are a hash of a file produced algorithmically. This type of hash was developed by the United States National Security Agency, and is typically used to verify that files are what they are supposed to be. Widely used in cryptographic applications such as SSH, APT repositories, transactions on websites, verifying files, Bitcoin, and more. It is very common. This type of cryptographic hash has been in use since 2001. An SHA-256 hash will be the exact same for the same file regardless of the source of the file, so if your hash is different from the one listed here you do not have the legitimate installer OR the hash is not up-to-date.

Note about VirusTotal tests:
Several people have pointed out to me something I feel should be brought up in the main thread. VirusTotal is not a catch-all, just as your typical antivirus software is not a catch-all. It will not catch everything. It should be used as a general guideline only. Clean VirusTotal tests do not guarantee your safety, although if the program passes all ~70 or so antivirus engines it's probably safe to use. Any additional malicious activity should be caught by your antivirus program's heuristics. I take no responsibility for anything that is malicious, but I can say in good conscience that I have done everything I can to ensure that everything on this thread is safe. Keep in mind that programs that trip VirusTotal may still be safe to use, antivirus programs often pick up injectors as malware or Trojans because that's how those types of viruses behave in the real world. Use your best judgement. If your best judgement is not good enough, do not use these programs. You have been warned.

----- C --- L --- I --- E --- N --- T--- S ------ C --- L --- I --- E --- N --- T--- S ------ C --- L --- I --- E --- N --- T--- S -----

Impact | 1.11.2 to 1.15.2 | Java Edition
VirusTotal Link for *.exe Installer | VirusTotal Link for *.jar Installer
SHA-256 Hash: 4EAFFB99759FBD949D0FBEF58AE9CEB45CE8CA2B0D7DC22147D4FF0E46F010EC
Impact triggered 0/72 engines on both installers.
Direct Link to Impact's *.exe Installer | Direct Link to Impact's *.jar Installer
------------------------------------------------------------------------------------------------------------------------------------------------

Sigma | 1.8 to 1.16 | Java Edition
VirusTotal Link for *.jar Installer | VirusTotal Link for the *.zip the Installer is Contained In
SHA-256 Hash for the *.zip file: 3FCD397849358522BF0EEEAF117487DBA860919900A904551DF512BE2C34B48C
Sigma's *.zip file triggered 0/59 engines on the *.zip file.
Sigma's *.jar file triggered 0/60 engines on the *.jar file.
Direct Link to Sigma's *.zip File that Contains the Installer
------------------------------------------------------------------------------------------------------------------------------------------------

9b9t | 1.12.2, needs testing | Java Edition | Forge Mod
VirusTotal Link for the *.jar Forge Mod
SHA-256 Hash: 30E4F2778688D54CE7992AFDE509460A7BDDBDA77800219083D4D12BC696EEA0
9b9t triggered 0/60 engines.
AnonFile link to 9b9t's *.jar Mod
------------------------------------------------------------------------------------------------------------------------------------------------

Ingrosware | 1.12.2 | Java Edition | Forge Mod
VirusTotal Link for the *.jar Forge Mod
SHA-256 Hash: BD1A0F9079F4C834A251163C3A0ECBFF7DFC28AB00CF1C74008AADD042FAD358
Ingrosware triggered 0/59 engines.
AnonFile link to a pre-built *.jar Mod
Note: Ingrosware is open source, and is available on GitHub. If you want to build it yourself, you can do so here.
------------------------------------------------------------------------------------------------------------------------------------------------

Mercury | 1.12.2 | Java Edition | Forge Mod
VirusTotal Link for the *.jar Forge Mod
SHA-256 Hash: 70E585A94218149970410ACAE5BE7C1C1B731140F1AF55FE2D1292B1CA74DCB9
Mercury triggered 0/60 engines.
AnonFile link to Mercury's *.jar Mod
------------------------------------------------------------------------------------------------------------------------------------------------

Atlas | 1.12.2 | Java Edition | Forge Mod | Use with caution!
VirusTotal Link for the *.jar Forge Mod
SHA-256 Hash: 7AEB7220CBD5D7C4E4421A940357F14EC70B18DB905469E288529FE3A2C04D57
Note: The file is called AceHackGold-n3.0-release.jar in VirusTotal. The client is identified as Atlas in the .nfo file it came bundled with.
Atlas triggered 7/59 engines.
Note: Upon closer inspection of the VirusTotal scan, the client appears to be of the injected flavor. Injectors are commonly a false positive Trojan. The client appears to be safe, and there was nothing particularly noteworthy in the VirusTotal scan that is atypical for an injector. While this makes the file appear to be safe, use with caution.
AnonFile Link for the *.jar Mod
Note: This is a cracked client! The crack is pre-done, so no additional work is required to use -- just put it in your Forge Mods folder and click play.
Note 2: The file downloaded is called AceHackGold-n3.0-release.jar*, I'm not sure why. This file was community-sourced, but it has been inspected in the same manner as all the others*.
------------------------------------------------------------------------------------------------------------------------------------------------

Atom | 1.12.2 | Java Edition | Forge Mod | Use with extreme caution!
VirusTotal Link for the *.zip the Forge Mod is Contained In
SHA-256 Hash: 3B43F952EB5B14F2B01592057B27E92B0E38B6874EA10B8E893BFCBC71463377
Note: The file is called output.157312297.txt in VirusTotal. In addition, VirusTotal identifies the file type properly (\.zip).*
Atom triggered 9/59 engines.
Note: Upon closer inspection of the VirusTotal scan, the client accesses numerous registry keys, which is a behavior I personally would consider to be unnecessary and incredibly suspicious. You can find more information in the VirusTotal scan. The client also exhibits typical Trojan false-positives.
AnonFile Link for the *.zip File
Note: This is a cracked client! The crack is pre-done, so no additional work is required to use -- just put it in your Forge Mods folder and click play.
Use this client with extreme caution. There are behaviors that I consider to be extremely suspicious, you must determine for yourself if it's safe to use however. This may just be how the client works. I do not know, and I can't be bothered to test it.
------------------------------------------------------------------------------------------------------------------------------------------------

Aurora | 1.12.2 | Java Edition | Forge Mod
VirusTotal Link for the *.zip the Forge Mod is Contained In
SHA-256 Hash: 9A66929B629AB076383340D33E0EF9B8CE221679EF79315240EA6C760651A533
Aurora triggered 0/61 engines.
AnonFile Link for the *.zip File
Note: This is a cracked client! The crack is pre-done, so no additional work is required to use -- just put it in your Forge Mods folder and click play.
------------------------------------------------------------------------------------------------------------------------------------------------

CandyCat | 1.12.2 | Java Edition | Forge Mod | Use with caution!
VirusTotal Link for the *.zip the Forge Mod is Contained In
SHA-256 Hash: 8CEC2F9F28AA3957504E0CC66BF1516080C7BAC50EADB54DC6DD97E0E6E9C745
CandyCat triggered 9/61 engines.
Note: Upon closer inspection of the VirusTotal scan, the client appears to be of the injected flavor. Injectors are commonly a false positive Trojan. The client appears to be safe, and there was nothing particularly noteworthy in the VirusTotal scan that is atypical for an injector. While this makes the file appear to be safe, use with caution.
AnonFile Link for the *.zip File
Note: This is a cracked client! The crack is pre-done, so no additional work is required to use -- just put it in your Forge Mods folder and click play.
------------------------------------------------------------------------------------------------------------------------------------------------

DayNightGod | 1.12.2 | Java Edition | Forge Mod | Use with caution!
VirusTotal Link for the *.zip the Forge Mod is Contained In
SHA-256 Hash: 9CEEB43476B18149C0DA76B7AE94713AAF60ED4D2BFD2339E863CC46A1808A0D
DayNightGod triggered 1/59 engines.
Note: Upon closer inspection, only one engine was triggered. The client did not trigger the usual false-positives of a Trojan, use with caution.
AnonFile Link for the *.zip File
Note: This is a cracked client! The crack is pre-done, so no additional work is required to use -- just put it in your Forge Mods folder and click play.
------------------------------------------------------------------------------------------------------------------------------------------------

HyperLethal | 1.12.2 | Java Edition | Forge Mod | Use with caution!
VirusTotal Link for the *.zip the Forge Mod is Contained In
SHA-256 Hash: 77FACC1FDB0415438963CCC8DDB4081958563AAA962CE9C024E5063DA32E8FAD
HyperLethal triggered 2/59 engines.
Note: Upon closer inspection of the VirusTotal scan, the client appears to be of the injected flavor. Injectors are commonly a false positive Trojan. The client appears to be safe, and there was nothing particularly noteworthy in the VirusTotal scan that is atypical for an injector. While this makes the file appear to be safe, use with caution.
AnonFile Link for the *.zip File
Note: This is a cracked client! The crack is pre-done, so no additional work is required to use -- just put it in your Forge Mods folder and click play.
------------------------------------------------------------------------------------------------------------------------------------------------

LoveClient | 1.12.2 | Java Edition | Forge Mod | Use with extreme caution!
VirusTotal Link for the *.zip the Forge Mod is Contained In
SHA-256 Hash: C71EC42FF612D75CB7AA21B8400D164A74AAD9BB65D2DFEE232461DAF98034C2
LoveClient triggered 9/61 engines.
Note: Upon closer inspection of the VirusTotal scan, the client accesses numerous registry keys, which is a behavior I personally would consider to be unnecessary and incredibly suspicious. You can find more information in the VirusTotal scan. The client also exhibits typical Trojan false-positives.
AnonFile Link for the *.zip File
Use this client with extreme caution. There are behaviors that I consider to be extremely suspicious, you must determine for yourself if it's safe to use however. This may just be how the client works. I do not know, and I can't be bothered to test it.
------------------------------------------------------------------------------------------------------------------------------------------------

SnowHack | 1.12.2 | Java Edition | Forge Mod
VirusTotal Link for the *.zip the Forge Mod is Contained In
SHA-256 Hash: 7100C8D59CE06B279F7D03D834FC2C361F10BEAE913575FC7EFA74E498167D2C
SnowHack triggered 10/62 engines.
Note: Upon closer inspection of the VirusTotal scan, the client appears to be of the injected flavor. Injectors are commonly a false positive Trojan. The client appears to be safe, and there was nothing particularly noteworthy in the VirusTotal scan that is atypical for an injector. While this makes the file appear to be safe, use with caution.
AnonFile Link for the *.zip File
Note: This is a cracked client! The crack is pre-done, so no additional work is required to use -- just put it in your Forge Mods folder and click play.
------------------------------------------------------------------------------------------------------------------------------------------------
submitted by Daemris to minecraftclients [link] [comments]

Windows / Linux Guide to using Trezor with Bitcoin Core (HWI)

This is a guide to using your Trezor with Bitcoin Core. It may seem like more trouble than it's worth but many applications use Bitcoin Core as a wallet such as LND, EPS, and JoinMarket. Learning how to integrate your Trezor into a Bitcoin Core install is rather useful in many unexpected ways. I did this all through the QT interfaces, but it's simple to script. There is a much simpler guide available from the HWI github, and the smallest Linux TLDR is here
Unfortunately, I don't have access to a Coldcard or Ledger. I'm not sure how the setpin or -stdinpass parameters are handled on that HW.

( A ) Install TrezorCTL, HWI, and build GUI

You only need to set the wallet up once, but may repeat to upgrade

( A.I ) Download extract and install HWI

  1. Download and isntall Python
  2. Download https://github.com/bitcoin-core/HWI/archive/1.1.2.zip
  3. Extract it to a working folder (assumes C:\User\Reddit\src\HWI)
  4. Change Directory (cd) to working folder cd "C:\User\Reddit\src\HWI"
  5. Setup venv python -m venv .venv
  6. Enter venv .venv\Scripts\activate.bat 1
  7. Install dependencies python -m pip install -U setuptools pip wheel
  8. Install TrezorCTL python -m pip install trezor[hidapi]
  9. Install HWI python -m pip install hwi pyside2
  10. Download github.com/libusb/libusb/releases/download/v1.0.23/libusb-1.0.23.7z
  11. Extract MS64\dll\libusb-1.0.dll from the archive
  12. Copy to pywin copy libusb-1.0.dll .venv\Lib\site-packages\pywin32_system32\

( A.II ) Build the QT UI files

  1. Download and install MSYS2
  2. Launch a mingw64.exe shell
  3. CD to working folder cd "C:\User\Reddit\src\HWI"
  4. Enter venv source .venv/Scripts/activate 1
  5. Run UI build bash contrib/generate-ui.sh

( B ) Create a Trezor wallet in Bitcoin Core (testnet)

You only need to set the wallet up once, no private key data is stored, only xpub data

( B.I ) Retrieve keypool from HWI-QT

  1. Launch hwi-qt.exe --testnet (assuming testnet)
  2. Click Set passphrase (if needed) to cache your passphrase then click Refresh
  3. Select you trezor from the list then click Set Pin (if needed)
  4. Ensure your Trezor in the dropdown has a fingerprint
  5. Select Change keypool options and choose P2WPKH
  6. Copy all the text from the Keypool textbox

( B.II ) Create the wallet in Bitcoin QT

  1. Launch Bitcoin Core (testnet) (non-pruned) 2
  2. Select Console from the Window menu
  3. Create a wallet createwallet "hwi" true
  4. Ensure that hwi is selected in the console wallet dropdown
  5. Verify walletname using the getwalletinfo command
  6. Import keypool importmulti '' (note ' caging)
  7. Rescan if TXNs are missing rescanblockchain 3

( C.I ) Grab Tesnet coins

  1. Select the Receive tab in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Select Create new receiving address and copy address
  4. Google "bitcoin testnet faucet" and visit a few sites
  5. Answer captcha and input your addressed copied from C.I.3

( D ) Spending funds with HWI

This is how you can spend funds in your Trezor using Bitcoin Core (testnet)

( D.I ) Create an unsigned PSBT

  1. Select the Send tab in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Verify your balance in Watch-only balance
  4. Rescan if balance is wrong (see B.II.7) 3
  5. Craft your TXN as usual, then click Create Unsigned
  6. Copy the PSBT to your clipboard when prompted

( D.II ) Sign your PSBT

  1. In HWI-QT click Sign PSBT
  2. Paste what you copied in D.I.6 in PSBT to Sign field
  3. Click Sign PSBT
  4. Copy the text for PSBT Result

( D.III ) Broadcast your TXN

  1. Select the Console window in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Finalize PSBT: finalizepsbt
  4. Copy the signed TXN hex from the hex field returned
  5. Broadcast TXN: sendrawtransaction

Final Thoughts

I did this all through the GUI interfaces for the benefit of the Windows users. Windows console is fine, but the quote escaping in windows console is nightmarish. Powershell would be good, but that throws this on a whole another level for most Windows folks.
There is also the need to use HWI-QT due to a bug in blank passphrases on the commandline. You can work around it by toggling passphrase off or on, but again, it's more than I wanted to spell out.
Footnotes:
  • 1. - Later version of python put the activate script under 'bin' instead of 'Script'
  • 2. - You can run pruned, but you need to have a fresh wallet
  • 3. - Rescan is automatic on 'importmulti' but I was pruned so it was wierd
submitted by brianddk to Bitcoin [link] [comments]

Batch script to create pruned block data from full block data

TLDR; Produce a pruned block directory from a full block directory without copying any extra block data
I have a full node, but at times I want to run in a VM or on a RPi or something. Normally I have to clone my whole 300 GB block directory, enable pruning, then point bitcoin-qt.exe to the clone to finally arrive at a small 4 GB datadir. I found it frustrating that I was doing this 295 GB of pointless copy operations since once I enable pruning, the old blocks are discarded. I was also discouraged at the fact that .\Bitcoin\testnet3\blocks\blk00186.dat is different (by checksum) in a pruned and non-pruned directory.
So I finally came up with an answer. Basically, I copy over the latest few blk*.dat and rev*.dat files, then just make empty copies of the other blk*.dat and rev*.dat files. Then once bitcoin-qt.exe launches, it discards the empty files and rewrites the few files it needs. For Windows, it looks something like this:
set /a "sum=0" for /f %%I in ('dir /s /b /o:-n %full_blk%\blk*.dat') do ( set size=%%~zI set blkdat=%%~nxI set revdat=!blkdat:blk=rev! if !sum! GTR !pruned_mb! ( echo.> %pruned_blk%\!blkdat! echo.> %pruned_blk%\!revdat! ) else ( copy %full_blk%\!blkdat! %pruned_blk%\!blkdat! copy %full_blk%\!revdat! %pruned_blk%\!revdat! ) set /a "sum=!sum! -1 + !size!/(1024*1024)" )
I can stamp out a pruned blocks directory from my full blocks directory in seconds. Much easier... well for me.
Here's the source, but no guarantees. Just food for thought.
 
Update: I had originally thought to symlink the unused files, but turns out they are never read at all, so I can just dummy them out.
submitted by brianddk to Bitcoin [link] [comments]

Tron v11.1.3 (2020-08-20) // Minor updates; Remove PCHunter due to A/V false positives

Background

Tron is a script that "fights for the User."
It aims to automate ~87% of the tedious work in getting a badly-running Windows system back on its feet (clicking "next" in a/v scan windows, etc); with much left to the discretion of the tech.
It is built with heavy reliance on community input and updated regularly.
It is NOT a system optimization or "baseline" script.
Read the instructions.

Sequence of operation

Prep > Tempclean > De-bloat > Disinfect > Repair > Patch > Optimize > Wrap-up | Manual tools
Saves a log to C:\logs\tron\tron.log (configurable).
screenshots of Tron in action

Changelog

(significant changes in bold; full changelog on Github)
v11.1.3 (2020-08-20)
- Removed PCHunter utility (extra utility, Tron never ran PCHunter) due to false positives with many A/V engines
. Minor definition updates

Download

  1. Primary method: Download the .torrent.
  2. Secondary: Download a self-extracting .exe pack from one of the mirrors:
    Mirror HTTPS HTTP Location Host
    Official link link US-DC u/SGC-Hosting
    #1 link link US-NY u/danodemano
    #3 link link DE u/bodrino
    #4 link link US/EU u/mxmod
    #5 link --- US-MI u/ajcutshall
    #6 link --- AU u/agent-squirrel
    #7 link --- GB-LND u/FreezerMoosh
    #8 link --- US-MO u/OlderGeeks
    #9 link --- Amazon CDN u/helpdesktv
    #10 link --- Global CDN Softpedia
  3. Tertiary: Connect to the Syncthing repo (instructions) to get fixes/updates immediately. This method has some risks and you should only use it if you understand them.
  4. Quaternary: Source code
    Source code is available on Github (Note: this doesn't include many of the utilities Tron relies on to function). If you want to view the code without downloading a ~600MB package, Github is a good place to do it.

Command-Line Support

Tron has full command-line support. Switches are optional, can be used simultaneously, and override their respective default when used. See here for a list of command-line switches.

Pack Integrity

SHA-256 hashes are in \tron\integrity_verification\checksums.txt and are signed with my PGP key; included. Use this to verify pack integrity.

Donations

Tron will always be free and open-source. If you'd like to buy me a beer or more importantly ... scotch ... you can do so here:
  • Patreon
  • Bitcoin: 1Biw8gx2kD7mZf66ZdNgB9tG1pE9YA3kEd
  • Bitcoin Cash: 18sXTTrAViPZVQtm63zBK6aCK3XfJpEThk
  • Monero (preferred): 4GG9KsJhwcW3zapDw62UaS71ZfFBjH9uwhc8FeyocPhUHHsuxj5zfvpZpZcZFHWpxoXD99MVt6PnR9QfftXDV8s6HbYdDuZEDZ947uiEje
These addresses go directly to u/vocatus. If you wish to support another volunteer (e.g. the incredibly generous u/SGC-Hosting) please contact them directly.

Problems and Support

Please look here first for a list of common issues (Tron appearing to be stalled, etc). If it doesn't answer your issue, make a top-level post to TronScript and myself or one of the community members will look at the issue. Additionally, you can reach me 24/7 on Keybase.
\integrity verification contains checksums.txt and is signed with my PGP key (0x07d1490f82a211a2, pubkey included). Use this to verify the pack.
"Do not withhold good from those to whom it is due, when it is in your power to act." -p3:27
submitted by vocatus to TronScript [link] [comments]

Ransomware (Fidye Virüsü) Yedim ve Deep Web'e Davet Edildim

Ne indirdiğimi ben de batırlamıyorum. Öyle "Çokoyunindir.com" gibi sitelere de giren biri değilim ama bu gün kağıttan turna kuşu yapmayı öğrenirken bilgisayar 50 tane izin istedi. Ben de baktım microsoftun geliştirdiği uygulama (yani doğrulanmış uygulama) izin verdim. Önce windows uptade, daha sonra windows düzenleyici mi ne onun iznini istedi. Baktım bilgisayara Crop Edit diye bir uygulama kurulmuş. Ardından Opera'da manyak gibi reklam siteleri açılmaya başladı. Sanırım fidye virüsünü de o sitelerden yedim. Her neyse. Önce arkaplanın fotoğrafı degişti (Ben bunu fark etmedim.). Fark etmemi sağlayan şey "DxC16.readme.txt diye bir metin belgesinin açılması oldu.
Özetle çoğu dosyamın (exe dosyalarının hiçbiri şifrelenmemişti) şifrelendiğini, Deep Web'deki (Tor Browser indirmem gerekicekmiş) bir siteden onlara 500 dolar değerinde bitcoin gönderir isem bir decoder yollayacaklarını söylüyorlardı. Ayrıca hangi pc olduğumu anlamak için özel bir kodum da vardı. Dosyaların uzantısını değistirir ve kendi başıma bu işi çözmeye çalışırsam tüm dosyaların silineceğini, bilgisayarın pert olacağını ve özel bilgilerin halka açık olarak paylaşılacağını da not etmişlerdi.
Ben pek sakin bir şekilde interneti ve bilgisayarı kapatıp bu virüsü araştırdım. Tahminimce "Avaddon" adında vir ransomware (fidye virüsü) yemişim. Bu gün de bilgisayarın kurtarma ayarlarından windowsu fabrika ayarlarına döndürüyorum. Tüm diskler temizlenecekmiş ama amına koyduğumun virüsü Z sürücüsü diye bir şey açmıştı virüsü oraya da kurmuş olabilir.
Bu konular hakkında bilgisi olan bir arkadaş varsa benimpe iletişime geçebilir mi? Sizce bilgisayarı sıfırlamakla hata mı ettim? (Not: şu an yüzde 37si bitti) Bilgisayar da benim değil emanet. Lütfen yardım edin
Edit: Yardım eden herkese teşekkürler. Bilgisayarı sıfırladım ve Z diski ortadan kalktı. Sorunsuz kullanıyorum. Avaddon'da çalışan orospu çocukları da bokumu yesinler.
submitted by AliCeyhun to KGBTR [link] [comments]

Help with scraping interactive chart error: unable to locate element (Selenium)

Hey guys, I'm currently trying to scrape the values (date and the index value) off the chart located here: https://www.mvis-indices.com/indices/digital-assets/mvis-cryptocompare-bitcoin-select-spot
The issue i end up running into is when i try and locate the date and value, i get the error: unable to locate element. I would appreciate any help. My code is as follows:
import selenium from selenium import webdriver from selenium.webdriver.chrome.options import Options from selenium.webdriver.support.ui import WebDriverWait from selenium.webdriver.support import expected_conditions as EC from selenium.webdriver.common.by import By from selenium.webdriver.common.action_chains import ActionChains from selenium.webdriver.common.keys import Keys from time import sleep import datetime as dt import pandas as pd import datetime from datetime import date date_today=date.today()-datetime.timedelta(5) dt_string = date_today.strftime("%d%m%y") #setting up webdrive PATH = "C:\Program Files (x86)\chromedriver.exe" driver = webdriver.Chrome(PATH) #opening the connection and grabbing the page my_url="https://www.mvis-indices.com/indices/digital-assets/mvis-cryptocompare-bitcoin-select-spot" driver.get(my_url) driver.maximize_window() #initializing the action object action = webdriver.ActionChains(driver) #deselect normalize check_box=WebDriverWait(driver,20).until(EC.presence_of_element_located((By.XPATH,'/html/body/section [3]/div/div[2]/div/div/div[3]/div/div/div/div[1]/ul[2]/li/label/input'))) check_box.click() #grabbing the element and its size and location element=WebDriverWait(driver,20).until(EC.presence_of_element_located((By.XPATH,'/html/body/section[3] /div/div[2]/div/div/div[3]/div/div/div/div[2]'))) loc=element.location size=element.size print(loc) print(size) #move the cursor to extreme right of the object sleep(5) action.move_to_element(element).perform() sleep(2) action.move_by_offset(323,0).perform() #getting the first date and value pair date_2=driver.find_element_by_xpath('/html/body/section[3]/div/div[2]/div/div/div[3]/div/div/div/div[2] /div/svg/g[15]').text value=driver.find_element_by_xpath('/html/body/section[3]/div/div[2]/div/div/div[3]/div/div/div/div[2] /div/svg/g[17]').text #setting up the dictionary time_serie={} time_serie[date_2]=value print(date_2,value) 
submitted by Messist11 to learnpython [link] [comments]

Help with scraping interactive chart error: unable to locate element (Python)

Hey guys, I'm currently trying to scrape the values (date and the index value) off the chart located here: https://www.mvis-indices.com/indices/digital-assets/mvis-cryptocompare-bitcoin-select-spot
The issue i end up running into is when i try and locate the date and value, i get the error: unable to locate element. I would appreciate any help. My code is as follows:
import selenium from selenium import webdriver from selenium.webdriver.chrome.options import Options from selenium.webdriver.support.ui import WebDriverWait from selenium.webdriver.support import expected_conditions as EC from selenium.webdriver.common.by import By from selenium.webdriver.common.action_chains import ActionChains from selenium.webdriver.common.keys import Keys from time import sleep import datetime as dt import pandas as pd import datetime from datetime import date date_today=date.today()-datetime.timedelta(5) dt_string = date_today.strftime("%d%m%y") #setting up webdrive PATH = "C:\Program Files (x86)\chromedriver.exe" driver = webdriver.Chrome(PATH) #opening the connection and grabbing the page my_url="https://www.mvis-indices.com/indices/digital-assets/mvis-cryptocompare-bitcoin-select-spot" driver.get(my_url) driver.maximize_window() #initializing the action object action = webdriver.ActionChains(driver) #deselect normalize check_box=WebDriverWait(driver,20).until(EC.presence_of_element_located((By.XPATH,'/html/body/section [3]/div/div[2]/div/div/div[3]/div/div/div/div[1]/ul[2]/li/label/input'))) check_box.click() #grabbing the element and its size and location element=WebDriverWait(driver,20).until(EC.presence_of_element_located((By.XPATH,'/html/body/section[3] /div/div[2]/div/div/div[3]/div/div/div/div[2]'))) loc=element.location size=element.size print(loc) print(size) #move the cursor to extreme right of the object sleep(5) action.move_to_element(element).perform() sleep(2) action.move_by_offset(323,0).perform() #getting the first date and value pair date_2=driver.find_element_by_xpath('/html/body/section[3]/div/div[2]/div/div/div[3]/div/div/div/div[2] /div/svg/g[15]').text value=driver.find_element_by_xpath('/html/body/section[3]/div/div[2]/div/div/div[3]/div/div/div/div[2] /div/svg/g[17]').text #setting up the dictionary time_serie={} time_serie[date_2]=value print(date_2,value) 
submitted by Messist11 to selenium [link] [comments]

Tron v11.1.2 (2020-07-13) // Fix screen rotation bug caused by O&OSU10; escape some references to %USERNAME%; minor definition updates

Background

Tron is a script that "fights for the User."
It aims to automate ~87% of the tedious work in getting a badly-running Windows system back on its feet (clicking "next" in a/v scan windows, etc); with much left to the discretion of the tech.
It is built with heavy reliance on community input and updated regularly.
It is NOT a system optimization or "baseline" script.
Read the instructions.

Sequence of operation

Prep > Tempclean > De-bloat > Disinfect > Repair > Patch > Optimize > Wrap-up | Manual tools
Saves a log to C:\logs\tron\tron.log (configurable).
screenshots of Tron in action

Changelog

(significant changes in bold; full changelog on Github)
v11.1.2 (2020-07-13)
! bugfix: Wrap missed reference to %TEMP% in quotes. Thanks to u/TheDarkThought
- Minor definition updates

Download

  1. Primary method: Download the .torrent.
  2. Secondary: Download a self-extracting .exe pack from one of the mirrors:
    Mirror HTTPS HTTP Location Host
    Official link link US-DC u/SGC-Hosting
    #1 link link US-NY u/danodemano
    #3 link link DE u/bodrino
    #4 link link US/EU u/mxmod
    #5 link --- US-MI u/ajcutshall
    #6 link --- AU u/agent-squirrel
    #7 link --- GB-LND u/FreezerMoosh
    #8 link --- US-MO u/OlderGeeks
    #9 link --- Amazon CDN u/helpdesktv
    #10 link --- Global CDN Softpedia
  3. Tertiary: Connect to the Syncthing repo (instructions) to get fixes/updates immediately. This method has some risks and you should only use it if you understand them.
  4. Quaternary: Source code
    Source code is available on Github (Note: this doesn't include many of the utilities Tron relies on to function). If you want to view the code without downloading a ~600MB package, Github is a good place to do it.

Command-Line Support

Tron has full command-line support. Switches are optional, can be used simultaneously, and override their respective default when used. See here for a list of command-line switches.

Pack Integrity

SHA-256 hashes are in \tron\integrity_verification\checksums.txt and are signed with my PGP key; included. Use this to verify pack integrity.

Donations

Tron will always be free and open-source. If you'd like to buy me a beer or more importantly ... scotch ... you can do so here:
  • Patreon
  • Bitcoin: 1Biw8gx2kD7mZf66ZdNgB9tG1pE9YA3kEd
  • Bitcoin Cash: 18sXTTrAViPZVQtm63zBK6aCK3XfJpEThk
  • Monero (preferred): 4GG9KsJhwcW3zapDw62UaS71ZfFBjH9uwhc8FeyocPhUHHsuxj5zfvpZpZcZFHWpxoXD99MVt6PnR9QfftXDV8s6HbYdDuZEDZ947uiEje
These addresses go directly to u/vocatus. If you wish to support another volunteer (e.g. the incredibly generous u/SGC-Hosting) please contact them directly.

Problems and Support

Please look here first for a list of common issues (Tron appearing to be stalled, etc). If it doesn't answer your issue, make a top-level post to TronScript and myself or one of the community members will look at the issue. Additionally, you can reach me 24/7 on Keybase.
\integrity verification contains checksums.txt and is signed with my PGP key (0x07d1490f82a211a2, pubkey included). Use this to verify the pack.
"Do not withhold good from those to whom it is due, when it is in your power to act." -p3:27
submitted by vocatus to TronScript [link] [comments]

BitcoinPlus 2.8.0 release with Secure Messaging

BitcoinPlus 2.8.0 is now released and includes Secure Messaging user interface to allow sending of encrypted messages across the BitcoinPlus network that are only decipherable by the sender and recipient. Read more about using secure messaging here.
For a detailed list of changes in the 2.8.0 release and downloads visit the BitcoinPlus GitHub release page here.
Direct Downloads
Windows 32bit Windows 64bit macOS Linux 32bit Linux 64bit
submitted by Bushstar to BitcoinPlus_XBC [link] [comments]

Heres some proof about sigma not being a trojan and omikron client proof from the sigma creator andro

The high GPU usage is due to the GPU acceleration or the UIs. And this is not comparable to other person's GPU usage since every GPU behave differently. You can compare this usage with vanilla 1.15.2's GPU usage. In my personal case, it's about +1~8% higher.
And the overall performance loss over the 1.8 clients is due to the 1.15 itself, the heavy UI, the missing optimisations (performance update soon), the obfuscation, etc
Some people are saying that "conhost.exe" is a malware... It's actually the console process spawned by java.exe which is used by Sigma (instead of the javaw.exe, the window version of java.exe without the console, that is mostly used for Minecraft).
Fun fact: Badlion client and Lunar client are also spawning conhost, and they aren't getting called out as malwares.
Here's a great explanation of what it is: https://www.howtogeek.com/howto/4996/what-is-conhost.exe-and-why-is-it-running/

And Omikron client was not a bitcoin miner, here's the copypasta :
Omikron client didn't have any btc miner / rat / botnet or whatever. The thing running in background was a system to validate the usage of the auto alt / proxy from other computers. Therefore, if you used auto alt / auto proxy, your computer among others validated in some sort of P2P the usage of alts / proxies. If >50% of computers says that a "transaction" is good, it was validated. Omikron decided to do that to counter the abuse of auto alt / auto proxy.
But ofc you could disable that autorun in Omikron Client's setting. And it was clearly written in the client that it would autorun (but no body really read it) if you use auto alts / auto proxy.
Edit, another copypasta:
I know, this is missleading. In the code, finding alts is refenrenced as "mining" them because you have this usepass combo and sometime yay ! Its a working minecraft alt ! The whole problem about all this drama is that its old code written when the client was "ghost client" and putting it in a .m file intead of .minecraft, having the package not named omikron, not using omikron domain name in the code was a good idear to prevent memory scanning cheating software such as BLSquad to find "omikron" but as you can tell it has bring more trouble that anything. You shoudn't be scared, your cpu isn't and wont be used to mine crypto or any unwanted activity and you will soon be able to chose if you want the service to run. In the next release, beside the fact that all of this was moved to .minecraft/Omikron, using proper domain name etc, you will be able to choose if you are using the client and want the background service running to find alts or if you have the client installed but not using it you will be able to disable the background service.
The video that is spreading about Omikron client is only proving that it downloads an autorun, and runs it in the background, which is intended.

Be careful of people trying to spread that Sigma could be a virus. Most of the time, they're made up by people who are clueless and don't know about what they're talking about (ex: conhost).
submitted by Vardenisss to minecraftclients [link] [comments]

Windows Guide to using Trezor with Bitcoin Core (HWI)

This is a guide to using your Trezor with Bitcoin Core. It may seem like more trouble than it's worth but many applications use Bitcoin Core as a wallet such as LND, EPS, and JoinMarket. Learning how to integrate your Trezor into a Bitcoin Core install is rather useful in many unexpected ways. I did this all through the QT interfaces, but it's simple to script. There is a much simpler guide available from the HWI github, and the smallest TLDR is here

( A ) Install TrezorCTL, HWI, and build GUI

You only need to set the wallet up once, but may repeat to upgrade

( A.I ) Download extract and install HWI

  1. Download and isntall Python
  2. Download https://github.com/bitcoin-core/HWI/archive/1.1.2.zip
  3. Extract it to a working folder (assumes C:\User\Reddit\src\HWI)
  4. Change Directory (cd) to working folder cd "C:\User\Reddit\src\HWI"
  5. Setup venv python -m venv .venv
  6. Enter venv .venv\Scripts\activate.bat 1
  7. Install dependencies python -m pip install -U setuptools pip wheel
  8. Install TrezorCTL python -m pip install trezor[hidapi]
  9. Install HWI python -m pip install hwi pyside2
  10. Download github.com/libusb/libusb/releases/download/v1.0.23/libusb-1.0.23.7z
  11. Extract MS64\dll\libusb-1.0.dll from the archive
  12. Copy to pywin copy libusb-1.0.dll .venv\Lib\site-packages\pywin32_system32\

( A.II ) Build the QT UI files

  1. Download and install MSYS2
  2. Launch a mingw64.exe
  3. CD to working folder cd "C:\User\Reddit\src\HWI"
  4. Enter venv source .venv/Scripts/activate 1
  5. Run UI build bash contrib/generate-ui.sh

( B ) Create a Trezor wallet in Bitcoin Core (testnet)

You only need to set the wallet up once, no private key data is stored, only xpub data

( B.I ) Retrieve keypool from HWI-QT

  1. Launch hwi-qt.exe --testnet (assuming testnet)
  2. Click Set passphrase (if needed) to cache your passphrase then click Refresh
  3. Select you trezor from the list then click Set Pin (if needed)
  4. Ensure your Trezor in the dropdown has a fingerprint
  5. Select Change keypool options and choose P2WPKH
  6. Copy all the text from the Keypool textbox

( B.II ) Create the wallet in Bitcoin QT

  1. Launch Bitcoin Core (testnet) (non-pruned) 2
  2. Select Console from the Window menu
  3. Create a wallet createwallet "hwi" true
  4. Ensure that hwi is selected in the console wallet dropdown
  5. Verify walletname using the getwalletinfo command
  6. Import keypool importmulti '' (note ' caging)
  7. Rescan if TXNs are missing rescanblockchain 3

( C.I ) Grab Tesnet coins

  1. Select the Receive tab in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Select Create new receiving address and copy address
  4. Google "bitcoin testnet faucet" and visit a few sites
  5. Answer captcha and input your addressed copied from C.I.3

( D ) Spending funds with HWI

This is how you can spend funds in your Trezor using Bitcoin Core (testnet)

( D.I ) Create an unsigned PSBT

  1. Select the Send tab in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Verify your balance in Watch-only balance
  4. Rescan if balance is wrong (see B.II.7) 3
  5. Craft your TXN as usual, then click Create Unsigned
  6. Copy the PSBT to your clipboard when prompted

( D.II ) Sign your PSBT

  1. In HWI-QT click Sign PSBT
  2. Paste what you copied in D.I.6 in PSBT to Sign field
  3. Click Sign PSBT
  4. Copy the text for PSBT Result

( D.III ) Broadcast your TXN

  1. Select the Console window in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Finalize PSBT: finalizepsbt
  4. Copy the signed TXN hex from the hex field returned
  5. Broadcast TXN: sendrawtransaction

Final Thoughts

I did this all through the GUI interfaces for the benefit of the Windows users. Windows console is fine, but the quote escaping in windows console is nightmarish. Powershell would be good, but that throws this on a whole another level for most Windows folks.
There is also the need to use HWI-QT due to a bug in blank passphrases on the commandline. You can work around it by toggling passphrase off or on, but again, it's more than I wanted to spell out.
Footnotes:
  • 1. - Later version of python put the activate script under 'bin' instead of 'Script'
  • 2. - You can run pruned, but you need to have a fresh wallet
  • 3. - Rescan is automatic on 'importmulti' but I was pruned so it was wierd
submitted by brianddk to TREZOR [link] [comments]

List of GTA V Paid Mod Menus for PC

List of GTA V Pain Mod Menus for PC as of June 11th, 2020:
- 2take1 Menu https://2take1.menu/ - Apollo Menu https://www.apollomenu.xyz - Brave Menu https://bravecheats.com/ - Carbonate Menu https://carbonate.xyz/ - Cherax Menu https://cherax.vip/ - Darkness Menu https://darkness-gta.de/ - Delusional Menu https://delusionalcheats.com/ - Disturbed Menu https://www.w1tch.pro/ - Duality Menu https://discord.gg/PfMUC8h - Electric Plug Menu https://electricplug.xyz - Ephemeral Menu https://ephemeral.pro/ - Explosive Menu https://explosivemenu.com/ - Flame Menu https://flamemenu.site/ - GTA Elite Menu https://gtaelite.com/ - Gravity Menu https://gravitymenu.cf/ - Hani Menu https://hanigta.eu/ - Hypno Menu https://hypnomenu.tk/ (Gone) - Impulse Menu https://impulse.one/ - Indra Menu https://indra.menu/ - Kingping Menu https://kingpinmenu.com/ - Kitsune Menu https://kitsune.best/ - Luna Menu https://lunacheats.org/ - Lunar Menu https://lunarmenu.com/ - Maverick Menu https://maverickcheats.eu/ - Menace Menu https://discord.com/invite/gASc3yF - Next GTA Menu https://nextgta.menu/ - Paragon Menu https://paragonmenu.com/index.php - Phantom-X Menu https://vk.com/phantomcommunity - Photon Menu https://photon-cheats.com/ - Position Menu https://positionmenu.company/# - Powers Menu https://www.powersprx.com/ - Raine Menu https://discord.gg/4zx9Tsk - Robust Menu https://robustgta.com/forum/index.php - Savage Menu https://discord.gg/4zx9Tsk - Shock Menu https://shock.to/ - Sodium Menu https://sodium.menu/forum/index.php - Syslx VIP Menu https://discord.gg/h7fy9Sc - T3zz3r3t Menu https://t3zz3r3t.menu/forums/ - Unknown Menu https://unknownmenu.us/ 
The list of Mod Menus I have personally owned:
- Anomalous (Gone) - Apollo - Camelot (Gone) - Carbon (Currently offline - Formerly Camelot) - Endured (Gone) - Hades (Gone) - Hypno (Gone) - Indra (Formerly Zeus) - Lunar - Paragon (Formerly Wardens) - Phantom-X - Sodium (Formerly Endured) - Wardens (Gone) - Zap (Gone) - Zeus (Gone) 
When buying a Mod Menu you have to know what you want in it. If you want a menu with solely protection or one for griefing or one for recoveries, you got to know what you want and do research on the menus above to see which one suits you the best. You can't simply say one menu is better than the other because they all have different focuses. There is no best menu. There is only the menu that suits yourself the best. Anyone trying to tell you one or the other is better is being biased and you should only look for what is you need/want in a menu and not what is said about one.
Things to know about Modding in GTA V:
  1. Every Mod Menu has a chance to ban, you are never 100% safe. But the chances of you being banned are very slim. They only rise when you troll or grief and when you do recoveries.
  2. Most Menus accept Paypal payments but there are some who only accept bitcoin, gift cards, etc. If you can't buy bitcoin more often than not you can find someone who resells's the menu but at a marked up price since its more convenient for the buy and more cumbersome for the seller.
  3. If your antivirus or Windows Defender flags a menu for being a virus unless it's a free one, it is 99% of the time wrong. The reason it flags is because of the obfuscation and or because of an exe's since all AVs flag executables.

If there are any Mod Menu's I missed, private message me or comment on the thread and I will add it.
submitted by Pabs_b to Gta5Modding [link] [comments]

Ode to Testnet


I really would like to see new users try things with testnet. For those that don't know, testnet coins have no value but other than that testnet is like the main bitcoin network. There are nodes and transactions and blocks.

To run electrum in testnet mode, it depends on where it is installed. But you just give it the command line option --testnet.
On windows, I did command prompt and then:
"C:\Program Files (x86)\Electrum\electrum-3.3.8.exe" --testnet

It will allow you to create entirely separate wallets from your regular wallets, so no worried about using testnet on the same machine.
If you want testnet coin, just respond to this post or PM me.
submitted by fireduck to Electrum [link] [comments]

Test

Test
There is a fairly small subset of Bitcoin users that run a full node. I think the idea of running a full node has gotten a bad rap over the years since there is so much talk about running on a Raspberry Pi, or getting zippy SSDs. Although all of this can be fun, it is often not really required at all. Here are some ways to run a full node starting with the very simple. I'll get into more complex configs, but these are all optional.

Tech Skill Level: 0 (the basics)

  1. Download Bitcoin Core
  2. Launch the downloaded installer and install the app
  3. Launch the installed "Bitcoin Core" app and let it run overnight
In many cases, thats it. If your running a new machine with a fairly good internet connection, 8 or 9 hours will be enough to complete the "Initial Block Download" (IBD). This may fill up your drive a bit, but again, on most new machines, 300 GB of space isn't that hard to come by.

Tech Skill Level: 1 (encrypted wallet)

One thing we left out in the level-0 exercise is encrypting your wallet. It's easy enough to do well, but a bit more difficult to do right. The main challenge is that humans generate really poor passwords. If you want a good password, the best way is to use something called "diceware". Basically, you just grab 4 or 5 dice and each throw of the dice represents a certain word on a special list. The throw {1,4,5,3,1} for example would be the word camping on the EFF-diceware-wordlist. So you repeat this a few times until you have a list of 8 or so words which becomes the passphrase you use to encrypt your wallet. Write it down, it is always hard to remember at first. So at level-1 your list becomes:
  1. Download Bitcoin Core
  2. Launch the downloaded installer and install the app
  3. Launch the installed "Bitcoin Core" app and let it run overnight
  4. Choose Encrypt Wallet from the Settings Menu
  5. Enter your 8 word (or so) passphrase generated using the Diceware method

Wallet Encryption Dialog

Tech Skill Level: 2 (enable pruning if needed)

Though I said "300 GB of space isn't hard to come by", some times it actually is. If space is an issue, a simple way to fix it is to tell bitcoin to simple take less space. This is called "pruning" and can take that number from 300 GB down to below 5 GB. If you can't find 5 GB, then you'll have to read ahead to level-3 to add USB storage. But the good news is, enabling pruning is pretty easy, we just add another step to our working list:
  1. Download Bitcoin Core
  2. Launch the downloaded installer and install the app
  3. Launch the installed "Bitcoin Core" app and let it run overnight
  4. Do the wallet encryption steps here if you wish
  5. Choose Options from the Settings Menu
  6. Choose Prune block storage to: and select the max size for the blocks to use
  7. Exit and restart the bitcoin application for the changes to take effect

Pruning Dialog
Note, even setting this to 1 GB will still leave you with about a 4.5 GB install. The blocks take up a lot of space, but the chainstate and other folders eat up at least 3.5 GB and they can't be pruned. Also, be aware, to disable pruning requires you to perform the entire IBD again. While pruned some other functions my be disabled as well, so just know that pruning does limit some functionality.

Tech Skill Level: 3 (verify the installer)

Although this is arguably something that should be done at level-0, some find the intricacies of comparing hash (thumbprint) values to be tedious and beyond the scope of a beginner. You will find these types of hash compares suggested quite often as a way to prevent running tainted programs. Programs are often tainted by bad disk or network performance, but most often, taint is malicious code inserted by viruses or malware. This is a way to guard yourself against those types of attacks. What I cover here is a very basic comparison on the certificate, but a more thorough comparison advised by mosts uses a program called Gpg4Win, and is beyond the scope of this beginners guide. But regardless, most users should strive to do this minimum level of validation.
  1. Download Bitcoin Core
  2. Launch the downloaded installer
  3. When prompted "Do you want to allow..." click Show more details
  4. In the details section select Show information about the publisher's certificate
  5. In the certificate window select the Details tab
  6. In the Details tab Subject should start with "CN = Bitcoin Core Code Signing Association"
  7. Also ensure Thumbprint reads ea27d3cefb3eb715ed214176a5d027e01ba1ee86
  8. If the checks pass, click OK to exit the certificate window and Yes to allow the installer to run.
  9. Launch the installed "Bitcoin Core" app and let it run overnight
  10. Do the wallet encryption steps here if you wish
  11. Do the optional pruning steps here if you wish

Certification Validation Windows
Note: The certificate used to sign the current Bitcoin installer is only valid from March 2020 to March 2021. After that point the thumbprint on the certificate will change. This is by design and intentional. If your reading this post after March 2021, then it is understood that the thumbprint has changed.

Tech Skill Level: 4 (use secondary storage)

We glossed over the "new machine with fairly good internet" part. Truth me known many people do not have fairly new machines, and find the IBD to take longer than the "over night" best wishes. For most people the slowdown is the disk access when calculating what is called chainstate. This requires fast random reads and writes to the disk. If you have an SSD disk, this will be no problem, but if you have a non-SSD "spinning" disk, random writes are always slow. Though an SSD will speed things up, they are pricey, so a nice middle ground may be a simple high-end USB key drive. You can get some with 10 to 15 MB/s random writes which is usually a order of magnitude faster than a "spinning" disk. And with pruning (see level-2), a small USB drive should be fine.
Once you decide on a drive, the tricky part will be to enable external storage. It requires editing a configuration file and adding a few lines. The configuration file needs to be in both the default directory, and USB key drive, but before we do that, we want to create a directory on the key drive. You will need to determine the drive letter of your USB key drive. For the sake of this example, we will assume it is D:, but you must determine this yourself and correct the example. Once you know the drive letter, create a blank folder on the drive called Bitcoin. So for this example, creating Bitcoin on drive D: will create the path D:\Bitcoin. Once done, assuming that D: is your drive, here are the steps to edit the two configuration files:
  1. Download Bitcoin Core
  2. Launch the installer, verify it, then run it
  3. Launch the installed "Bitcoin Core" app and let it run overnight
  4. Do the wallet encryption steps here if you wish
  5. Do the optional pruning steps here if you wish
  6. Launch "Notepad" by typing "Notepad.exe" in the windows search bar then click Open
  7. Type the line datadir=D:\Bitcoin (depending on your drive letter) in the blank file
  8. Choose Save from the File menu in notepad
  9. Type %APPDATA%\Bitcoin\bitcoin.conf (note the percent signs) in the File name box
  10. Select All Files from the Save as type dropdown
  11. Click the Save button and overwrite the file if prompted
  12. Exit and restart the bitcoin application for the changes to take effect

Save As Dialog
Now that you've reached this level of technical expertise, there are many new configuration options that you can begin to modify if you wish. Most configuration data is contained in the bitcoin.conf file and learning how to maintain it is a key step for a node operator.

Tech Skill Level: 5 (all other customizations)

Here's a short list of various things you can ADD to your bitcoin.conf file. You generally just add a new line for each configuration settings.
  • addresstype=bech32
  • changetype=bech32
The addresstype / changetype allows your wallet to use the native-segwit (bech32) format. This is the most efficient and inexpensive way to spend bitcoin, and is a recommended configuration. The default uses something called p2sh-segwit which is more compatible with older wallets, but more expensive to spend.
  • minrelaytxfee=0.00000011
Changing the minrelaytxfee setting allows you to help propagate lower fee transactions. It will require more memory but TXN memory is capped at 300 MB by default anyways, so if you have enough memory, it is a good setting to choose.
  • dbcache=2048
The dbcache setting controls how many MB of memory the program will use for the chainstate database. Since this is a key bottleneck in the IBD, setting this value high (2048 MB) will greatly speed up the IBD, assuming you have the memory to spare
  • blocksdir=C:\Bitcoin
  • datadir=D:\Bitcoin
In level-4 we discussed moving the datadir to a fast external storage, but the majority of the space used for bitcoin is the blocks directory (blocksdir). Although you should always use for fastest storage for datadir, you are free to use slow storage for blocksdir. So if you only want to consume a small amount of your SSD (assumed D:) then you can keep your blocks on your slow "spinning" drive.
  • upnp=1
One of the harder challenges you may face running a node, is to get incoming connections. If you are lucky, you may find that your firewall and network HW support the uPnP protocol. If they do, this setting will allow bitcoin to configure uPnP to allow incoming connections to your node.
submitted by brianddk to brianddk [link] [comments]

List of CFML Vulnerabilities & Security Issues

This list is updated frequently as we detect more issues, also note that we can’t detect these issues in all cases on all servers, even if the issue has not been patched yet.
Here are some CFML Vulnerabilities & Security Issues that you might have faced-

  1. Jakarta Virtual Directory Exposed – The /jakarta virtual directory (which is required by CF10+ on Tomcat/IIS) is serving files such as isapi_redirect.properties or isapi_redirect.log. The only URI that should be served is /jakarta/isapi_redirect.dll – you can use Request Filtering to block.
  2. Bitcoin Miner Discovered – Found files in /CFIDE that match the signature of a bitcoin miner exploit. Look for /CFIDE/m /CFIDE/m32 /CFIDE/m64 and /CFIDE/updates.cfm among others.
  3. Hotfix APSB11-14 Not Installed – Apply the hotfixes located in Adobe Security Notice apsb11-14.
  4. Railo Security Issue 2635 – Input of Chr(0) to the ReplaceList function can cause infinate loop / crash. Fixed in Version 4.1.1.008
  5. XSS Injection in cfform.js – A document.write call was found in your /CFIDE/scripts/cfform.js file, an attacker may be injecting a javascript, please check your cfform.js file.
  6. Executable found in CFIDE – Found executable file(s) in /CFIDE with one of the following file extensions: dll, exe, bat, sh
  7. Heartbleed Vulnerability Detected – The heartbleed vulnerability is a bug in OpenSSL (the crypto library used by Apache, NGinx, and others) that can allow the leakage of private keys used for TLS/SSL encryption.
  8. OpenBD AdminAPI Exposed to the Public – The /bluedragon/adminapi/ directory is open to the public it should be locked down to prevent exploit.
  9. Security Hotfix APSB12-26 Not Installed – The security hotfix referenced in Adobe Security Bulletin APSB12-26 was not found to be installed on your server. This hotfix resolves a sandbox permission issue.
  10. Security Hotfix APSB17-30 Not Installed Or Partailly Installed – The security hotfix referenced in Adobe Security Bulletin APSB17-30 was not found to be fully installed on your server. For the hotfix to be effective you must have Java 8 update 121 or greater installed. This hotfix resolves two critical vulnerabilities CVE-2017-11286 and CVE-2017-11283 / CVE-2017-11284 and one important vulnerability CVE-2017-11285. The issues are resolved in ColdFusion 11 Update 13+ and ColdFusion 2016 Update 5+ with Java 8 update 121 or greater.
  11. ColdFusion Example Applications Installed – The ColdFusion example applications are installed at /cfdocs/exampleapps/ or /CFIDE/gettingstarted/, they should not be installed on a production server.
  12. Svn Hidden Directory Exposed – A request for /.svn/text-base/index.cfm.svn-base appears to resolve to a subversion repository, which could lead to source code disclosure. Please block .svn/
  13. Solr Search Service Exposed – CVE-2010-0185 detected. ColdFusion 9 Apache Solr services are exposed to the public. Any data in solr search collections may be exposed to the public. Follow the instructions in APSB10-04 to remedy, or upgrade to ColdFusion 9.0.1.
  14. TLS Compression Supported – TLS Compression should be disabled due to the CRIME TLS vulnerability.
  15. Security Hotfix APSB11-04 Not Installed – The security hotfix referenced in Adobe Security Bulletin APSB11-04 was not found to be installed on your server. This hotfix also contains most prior security hotfixes.
  16. Git Hidden Directory Exposed – A request for /.git/config appears to resolve to a git repository, wouch could lead to source code disclosure. Please block .git/
  17. Cross Site Scripting Vulnerability CVE-2011-4368 – CVE-2011-4368 detected. Apply the hotfix located in Adobe Security Notice apsb11-29.
  18. JVM Vulnerable to Java Null Byte Injection – The JVM that you are running is vulnerable to null byte injections (or null byte poisioning) in java.io file operations. Java 1.7.0_40+ or 1.8+ attempt to mitigate null byte injection attacks.
  19. Java 11 Security Update Available – The JVM that you are running contains security vulnerabilities that could be exploited in server side environments. Update to the latest version of Java 11. Note that Oracle Java 11 requires a commercial license. Adobe CF customers can download Oracle Java 11 from the ColdFusion Downloads Page. You can also use OpenJDK, Amazon Corretto, or other non-oracle JVMs for free.
  20. Security Hotfix APSB19-10 Not Installed – The security hotfix referenced in Adobe Security Bulletin APSB19-10 was not found to be installed on your server. This hotfix resolves 2 issues, one important (CVE-2019-7092) and one critical (CVE-2019-7091). The issues are resolved in ColdFusion 11 Update 16+ ColdFusion 2016 Update 8+ and ColdFusion 2018 Update 2+. For all security fixes to be effective you should also have Java 8 update 121 or greater installed.
  21. Cross Site Scripting Vulnerability CVE-2011-0583 – CVE-2011-0583 detected. Apply the hotfixes located in Adobe Security Notice apsb11-04. The detection of this vulnerability also indicates to a high degree of likelihood that the following vulnerabilities may also exist: CVE-2011-0580, CVE-2011-0581, CVE-2011-0582, CVE-2011-0584
  22. Apache 2.2 Security Update Available – The version of Apache you are running does not contain the most recent security fixes.
  23. BlaseDS/AMF External XML Entity Injection – CVE-2009-3960 detected. You must apply the hotfix specified in Adobe Security Bulliten APSB10-05, otherwise an attacker can read any file on the server that ColdFusion has permission to read. You need to do this even if you don’t use BlaseDS or Flash Remoting because it is enabled in CF by default.
  24. SSL Version 2 Enabled – Your Web Server is accepting SSL V2 connections, a weak protocol. For PCI compliance, and strong security you must disable this protocol on your web server.
  25. Missing Strict-Transport-Security Header – This domain supports HTTPS but does not send the HTTP Strict-Transport-Security response header (HSTS) to force HTTPS.
  26. The /CFIDE/scripts directory is in default location. – Consider changing the default location of /CFIDE/scripts/ by changing the value of the Default Script Src setting in the ColdFusion Administrator.
  27. Recalled Hotfix 10.0.3 Installed – You are running ColdFusion 10.0.3 which has been recalled by adobe due to bugs in the release. Please install the latest 10.0 hotfix.
  28. ComponentUtils Exposed to the Public – The /CFIDE/componentutils/ directory is open to the public it should be locked down to prevent exploit.
  29. ColdFusion Update Available – You may not be running the latest version of ColdFusion 8, consider updating to ColdFusion 8.0.1
  30. Security Hotfix APSB13-10 Not Installed – The security hotfix referenced in Adobe Security Bulletin APSB13-10 was not found on your server. This hotfix resolves authentication issues that could allow an attacker impersonate a user in your application, or a ColdFusion Administrator.
  31. CVE-2010-2861 Detected – Path Traversal Vulnerability detected (CVE-2010-2861 APSB10-18), this allows an attacker to read any file on the servers file system that ColdFusion has access to (within the same drive on windows).
  32. Security Hotfix APSB13-19 Not Installed – The security hotfix referenced in Adobe Security Bulletin APSB13-19 was not found on your server.
  33. Security Hotfix APSB12-15 Not Installed – The security hotfix referenced in Adobe Security Bulletin APSB12-15 was not found to be installed on your server. This hotfix resolves a HTTP response splitting vulnerability in the ColdFusion Component Browser CVE-2012-2041.
  34. Security Hotfix APSB16-16 Not Installed – The security hotfix referenced in Adobe Security Bulletin APSB16-16 was not found to be installed on your server. This hotfix addresses a XSS issue, a Java Deserialization Vulnerability and a TLS Hostname verification issue. This issue is fixed in ColdFusion 10 Update 19+, ColdFusion 11 Update 8+, and ColdFusion 2016 Update 1+
  35. Vulnerable PageSpeed Module – The Version of PageSpeed Module you are using may be vulnerable to one or more vulnerabilities. Update your PageSpeed web server module to the latest version to resolve.
  36. TLS 1.2 Is Not Enabled – Configure your server to accept TLS 1.2 connections for optimal HTTPS security. Note for IIS you must be running Windows 2008r2 or greater for TLS 1.2 support. You can use our IIS SSL / TLS configuration tool to toggle protocol support on your server.
  37. Java 13 EOL – Java 13 has reached end of life at the release of Java 14. It is not a LTS (Long Term Support Version), you can use Java 11 for LTS.
  38. Lucee Security Issue 2015-08-06 – Lucee fixed an XSS issue in version 4.5.1.023. This issue remains unpatched in Railo.
submitted by aligatorraid to coldfusion [link] [comments]

Building an Ethereum Mining Rig (13 GPU) - 4th part

Third update to the guide "Building a Mining Rig for Ethereum". The absolute first guide to building a RX Vega 64 8gb 13 GPU Mining Rig.
Reading this guide to building a 13 GPU Ethereum mining rig requires adequate knowledge of building and running an Ethereum Mining Rig. We therefore recommend a previous view of our Guide to build a Mining Rig and related updates.

Let's immediately list the hardware used:

- Asus Mining Master X370 mainboard
- Core i5 Coffee Lake CPU
- 480 or 500GB SSD
- 32Gb Ram
- 13 GPU RX Vega 64 8Gb
- 3 x 1000W power supplies
- 1 1200W power supply
- 8Gb USB stick

In this guide we will obviously not explain how to mount the hardware of a Rig. The only notes we wish to underline are the following:

- the 1200W power supply must be the primary one on which to connect 4 GPUs and the video output for the monitor

- all the risers, as well as obviously the GPUs, must be powered through the 8-pole connections of the power supplies. We strongly advise against the use of 6-pole ports. Therefore, have the appropriate number of cables available for all connections. Risers can also be powered in pairs.

- the model of the video card used is the Asus Rog Strixx Gaming RX Vega 64 8Gb


The operating system is Windows 10 updated to the latest version available. The tool for creating installation media is available at the following link https://www.microsoft.com/it-it/software-download/windows10 to be able to use the USB key as a launcher for installing Windows 10 .

With the Asus Mining Master, the GPU risers can be connected directly to the motherboard via the USB cable, thus making one of the small components of the riser kits unusable.

After making all the connections on the motherboard, check that all GPUs are highlighted in green when the PC starts up. If not, move the USB cable on the motherboard one position. It may take at least 2 or 3 attempts.

Ethereum mining with 13 GPUs
Having solved this possible small inconvenience, let's proceed with the installation of the AMD Adrenaline 2020 drivers, always updated to the latest version, relating to the RX Vega Series.

If you want to proceed with more caution, the advice is to disconnect all the GPUs (remembering the locations of the USB cables) except one before installing the drivers.

The mining will be carried out on the Ethermine pool, our favorite, using the Claymore 15 software.


Once the download is complete, you will have to unzip the folder on the desktop and open the start.bat file contained in the Claymore folder using Notepad. The procedure is the usual one: delete the content and copy-paste the following command string:

start config.dll -epool eu1.ethermine.org:14444 -ewal "your ETH wallet address" -epsw x -worker "worker"
EthDcrMiner64.exe

Where EthDcrMiner64.exe is the executable, -epool indicates the pool to mine and its port, -ewal is the wallet address and -epsw is the password that we leave blank (X).

In place of "your wallet address" you will have to put your Ethererum wallet and instead of worker you will enter an identification number in case you plan to build more RIGs (such as RIG1, RIG2, etc ...).

At the following link, many other useful commands for your Rig:
https://github.com/Claymore-Dual/Claymore-Dual-Miner

Try to run mining and check that the system is stable.

In the Payouts section, after a few minutes of mining, you can decide the minimum amount of Ether to be sent to your wallet by simply entering the IP address of the RIG.

We performed the mining directly on the Ethereum address of the Exodus wallet. Coinbase is not supported.

Overclocking with OverdriveNTool
Let's proceed now with the download of OverdrivenTool at the following link: https://forums.guru3d.com/threads/overdriventool-tool-for-amd-gpus.416116/


For those unfamiliar with it, we recommend reading our software guide.

For those who do not intend to experiment or do not completely trust their software experience, at the following link you can view the settings on the parameters of the GPUs and the RAM of the GPUs - and other small tricks - to obtain the best possible performance without forcing the cards too much. video.

On our Youtube channel (subscribe numerous !!!) you will now be able to see the video relating to the start of mining and the one concerning the stabilization phase.

To better cool the Rig we have also installed fans for the extraction of heat as caution is never too much. Moreover, there is also an aesthetic gain.

Conclusions on the guide to build a 13 gpu ethereum mining rig.
Finally, we conclude this guide by reporting what everyone was waiting for (we do not say how long we had to wait before obtaining this result) the video link complhttps: //www.youtube.com/watch? V = k53XZn3zc9I & t = 61seto del Rig e del Mining .

We remain available for any advice, both on pools, on yield and on consumption.

Feel free to contact us in case you run into any problems where our guide to Building a 13 GPU Ethereum Mining Rig has not been completely helpful.

See you soon.


If you liked this article and would like to contribute with a donation:

Bitcoin: 1Ld9b165ZYHZcY9eUQmL9UjwzcphRE5S8Z
Ethereum: 0x8D7E456A11f4D9bB9e6683A5ac52e7DB79DBbEE7
Litecoin: LamSRc1jmwgx5xwDgzZNoXYd6ENczUZViK
Stellar: GBLDIRIQWRZCN5IXPIKYFQOE46OG2SI7AFVWFSLAHK52MVYDGVJ6IXGI
Ripple: rUb8v4wbGWYrtXzUpj7TxCFfUWgfvym9xf

By: cryptoall.it
Telegram Channel: t.me/giulo75
Netbox Browser: https://netbox.global/PZn5A
Horizen Faucet: https://getzen.cash/auth/register?ref=153228
submitted by Giulo75 to u/Giulo75 [link] [comments]

Tron v11.1.1 (2020-05-25) // Fix -pmb switch behavior; remove deprecated telemetry-removal tasks; prevent CCleaner from wiping Taskbar Jump Lists

Background

Tron is a script that "fights for the User."
It aims to automate ~87% of the tedious work in getting a badly-running Windows system back on its feet (clicking "next" in a/v scan windows, etc); with much left to the discretion of the tech.
It is built with heavy reliance on community input and updated regularly.
It is NOT a system optimization or "baseline" script.
Read the instructions.

Sequence of operation

Prep > Tempclean > De-bloat > Disinfect > Repair > Patch > Optimize > Wrap-up | Manual tools
Saves a log to C:\logs\tron\tron.log (configurable).
screenshots of Tron in action

Changelog

(significant changes in bold; full changelog on Github)
v11.1.1 (2020-05-25)
! Fix -pmb switch behavior
* CCleaner: Disable clearing of Taskbar Jump Lists. Thanks to u/D00shene
- Telemetry removal: Remove outdated job that used to uninstall "bad" updates
- Remove post-run restore point creation

Download

  1. Primary method: Download the .torrent.
  2. Secondary: Download a self-extracting .exe pack from one of the mirrors:
    Mirror HTTPS HTTP Location Host
    Official link link US-DC u/SGC-Hosting
    #1 link link US-NY u/danodemano
    #3 link link DE u/bodrino
    #4 link link US/EU u/mxmod
    #5 link --- US-MI u/ajcutshall
    #6 link --- AU u/agent-squirrel
    #7 link --- GB-LND u/FreezerMoosh
    #8 link --- US-MO u/OlderGeeks
    #9 link --- Amazon CDN u/helpdesktv
    #10 link --- Global CDN Softpedia
  3. Tertiary: Connect to the Syncthing repo (instructions) to get fixes/updates immediately. This method has some risks and you should only use it if you understand them.
  4. Quaternary: Source code
    Source code is available on Github (Note: this doesn't include many of the utilities Tron relies on to function). If you want to view the code without downloading a ~600MB package, Github is a good place to do it.

Command-Line Support

Tron has full command-line support. Switches are optional, can be used simultaneously, and override their respective default when used. See here for a list of command-line switches.

Pack Integrity

SHA-256 hashes are in \tron\integrity_verification\checksums.txt and are signed with my PGP key; included. Use this to verify pack integrity.

Donations

Tron will always be free and open-source. If you'd like to buy me a beer or more importantly ... scotch ... you can do so here:
  • Patreon
  • Bitcoin: 1Biw8gx2kD7mZf66ZdNgB9tG1pE9YA3kEd
  • Bitcoin Cash: 18sXTTrAViPZVQtm63zBK6aCK3XfJpEThk
  • Monero (preferred): 4GG9KsJhwcW3zapDw62UaS71ZfFBjH9uwhc8FeyocPhUHHsuxj5zfvpZpZcZFHWpxoXD99MVt6PnR9QfftXDV8s6HbYdDuZEDZ947uiEje
These addresses go directly to u/vocatus. If you wish to support another volunteer (e.g. the incredibly generous u/SGC-Hosting) please contact them directly.

Problems and Support

Please look here first for a list of common issues (Tron appearing to be stalled, etc). If it doesn't answer your issue, make a top-level post to TronScript and myself or one of the community members will look at the issue. Additionally, you can reach me 24/7 on Keybase.
\integrity verification contains checksums.txt and is signed with my PGP key (0x07d1490f82a211a2, pubkey included). Use this to verify the pack.
"Do not withhold good from those to whom it is due, when it is in your power to act." -p3:27
submitted by vocatus to TronScript [link] [comments]

Building an Ethereum Mining Rig - Part 2

First update to the guide "Building a 6Gpu Mining Rig for Ethereum" - Let's talk about Claymore.
This update supplements and does not replace the Guide to Build a 6GPU Mining Rig for Ethereum published on our site.

The substantial differences are due to the installation of the latest version of the Windows 10 Operating System, the mining on the Ethermine pool (in our opinion simpler than Dwarfpool) and the use of the XFX RX 580 8gb GPUs.

The first variant is found in Part 4 of the guide: the environment variables are not to be entered as they will be integrated directly into the bat file to start mining.

The second variant is found in Part 7 of the guide and leads us to "mine" on a different pool using the Claymore software.
Download the latest version at the following link: https://github.com/Claymore-Dual/Claymore-Dual-Miner

Once downloaded, unzip everything on a folder on your desktop and open the start.bat file with notepad. Clear the contents and copy the following command:

start config.dll -epool eu1.ethermine.org:14444 -ewal "your ETH wallet address" -epsw x -worker "worker"
EthDcrMiner64.exe

Where instead of "your wallet address" you will have to put your Ethererum wallet - obviously without the quotes - and instead of worker you will put an identification number in case you build more RIGs (such as RIG1, RIG2, etc ...). We opted for the eu1 pool even if some on the discussion forums believe that the us1 is more profitable.

At the following link, many other useful commands for your Rig:
https://github.com/Claymore-Dual/Claymore-Dual-Miner


The Ethermine pool offers a very well crafted and descriptive interface. In the Payouts section, after only 5 minutes of mining, you can decide the minimum amount of Ether to be transferred to your wallet by simply entering the IP address of the RIG.

We have decided to mine directly on the Ethereum address of our Exodus wallet. It is not recommended to mine directly on Coinbase, as reported on the site itself. Sin.

Nothing should be left to chance when you decide to build a mining rig for Ethereum.
The third variant is the most difficult of all. Once you have reached Part 5 of the guide, you can decide whether to continue or follow this update / variant. If you are here it is probably because you have run into some problem that the guide does not allow you to solve.

With the latest version of Windows 10, you may run into a kernel conflict between the operating system and AMD's Radeon Software Crimson ReLive Edition Beta for Blockchain Compute drivers. This conflict will prevent you from using Atiflash after installing the drivers.

Important: Before making any changes to the BIOS, please backup each GPU.

Important: first of all flash the GPUs with the original bios if for any reason you are forced to reinstall the operating system.


Still on Atiflash.
The advice would therefore be to flash the GPUs and then install the AMD drivers. Let's say it would be because you may run into another problem this time related to the GPUs themselves. Since each video card is different from any other, the bios mod of the GPU could crash the operating system showing the classic blue screen and displaying an error related to the Atimkdag.sys file.

This could be due to the fact that some GPUs have significantly higher performance in the calculation phase than others. We could call it a factory overclock but not using them for gaming we cannot say it with absolute certainty.

Having assessed these two drawbacks, the only safe solution is to flash all the GPUs, disconnect them except for the first one, install the Blockchain drivers (plus Atimkdag patch) and launch the mining command verifying that the operating system does not go into crash in the next 5 minutes.

Turn off the rig again and connect the second GPU so on up to the sixth. In the event that one or more video cards should crash the system, disconnect them. After that, it uses DDU from the provisional mode and flashes these GPUs with their original bios. At this point, connect them again, reinstall the Blockcain drivers (plus Atimkdag patch) and start mining definitively.

All the operations related to the use of Atiflash, DDU and driver installation are reported in Part 5 and Part 6 of our guide.
A little bit of Overclocking.
You will certainly find significant differences in performance between the GPUs.

At this point all that remains is to "operate" with an overclocking software. We opt for OverdriveNtool. Our constantly updated guide is available at the following link: https://www.cryptoall.it/2019/10/12/complete-guide-to-overdriventool/

Link to the official YouTube channel for verification: https://www.youtube.com/channel/UCdE9TTHAOtyKxy59rALSprA

GPUs with modified bios will not leave much room for modification. You will have to proceed with the most extreme overclocking on those that mount the original bios; obviously always in small steps by saving the profile for each GPU. Our guide explains in detail how to do it.

Hoping to have been of help, we give everyone an appointment for the second part of the update on how to build an Ethereum mining rig in which we will explain in detail the dual mining on the Ethermine pool.

See you soon.


If you liked this article and would like to contribute with a donation:

Bitcoin: 1Ld9b165ZYHZcY9eUQmL9UjwzcphRE5S8Z
Ethereum: 0x8D7E456A11f4D9bB9e6683A5ac52e7DB79DBbEE7
Litecoin: LamSRc1jmwgx5xwDgzZNoXYd6ENczUZViK
Stellar: GBLDIRIQWRZCN5IXPIKYFQOE46OG2SI7AFVWFSLAHK52MVYDGVJ6IXGI
Ripple: rUb8v4wbGWYrtXzUpj7TxCFfUWgfvym9xf

By: cryptoall.it Telegram Channel: t.me/giulo75 Netbox Browser: https://netbox.global/PZn5A
submitted by Giulo75 to u/Giulo75 [link] [comments]

Bitcoin Tor

Subject: PSA: Make your node reachable by using Tor
There is usually a post every few months with someone asking for tips on how to make their node reachable. It's always a hard question to answer since its impossible to know what type of routers and firewalls they are going to have to punch through. This is especially difficult in college dorms. One cheap (and easy) way around it is to to just jump through a few extra steps to make your bitcoin node a bitcoin onion node. Tor is great about traversing routers and firewalls like a hot knife through butter.
  1. Download, verify1, install and initialize Gpg4win
  2. Download, verify2, install, and launch Tor Browser
  3. Download, verify3, install, and launch Bitcoin Core
  4. Launch an Admin command console in the directory with tor.exe
  5. Install the Tor service: tor.exe --service install
  6. CD to service dir: cd %windir%\ServiceProfiles\LocalService\AppData\Roaming\tor
  7. Create and edit a file called torrc with the contents suggested below
  8. Restart tor: tor --service stop && tor --service start
  9. Record your onion hostname: type .\HiddenService\hostname as
  10. Add the bitcoin.conf options suggested below
  11. Restart the bitcoin-qt program
  12. Verify node connectivity at https://bitnodes.io/nodes/-8333/

torrc file: (replace c:\windows with the proper path as needed)

```

Change to C:\Windows\ServiceProfiles\LocalService\AppData\Roaming

Log notice file \tor\service.log HiddenServiceDir \tor\HiddenService HiddenServiceVersion 2 HiddenServicePort 8333 127.0.0.1:8333 HiddenServicePort 18333 127.0.0.1:18333 ```

bitcoin.conf file: (entries to be ADDED)

```

Change to what you recorded earlier

onion=127.0.0.1:9050 listen=1 externalip= discover=1 ```
Footnotes:
  • 1 - Cert-Subject: "Intevation GmbH"  ;  Cert-SHA1: c13a65963ad53e78694dd223d518007791a05fe4
  • 2 - PGP Signing Key: 0xEF6E286DDA85EA2A4BA7DE684E2C6E8793298290
  • 3 - PGP Signing Key: 0x01EA5486DE18A882D4C2684590C8019E36C2E964
submitted by brianddk to brianddk [link] [comments]

Tron v11.1.0 (2020-04-25) // Remove Malwarebytes installation by default (-pmb to preserve); French language fix; definition and de-bloat updates

Background

Tron is a script that "fights for the User."
It aims to automate ~87% of the tedious work in getting a badly-running Windows system back on its feet (clicking "next" in a/v scan windows, etc); with much left to the discretion of the tech.
It is built with heavy reliance on community input and updated regularly.
It is NOT a system optimization or "baseline" script.
Read the instructions.

Sequence of operation

Prep > Tempclean > De-bloat > Disinfect > Repair > Patch > Optimize > Wrap-up | Manual tools
Saves a log to C:\logs\tron\tron.log (configurable).
screenshots of Tron in action

Changelog

(significant changes in bold; full changelog on Github)
v11.1.0 (2020-04-25)
/ Change REMOVE_MALWAREBYTES to PRESERVE_MALWAREBYTES (-pmb) as the new default behavior is to remove it at the end of the script
* Fix for Internet connection check on French language systems
* Minor definition updates for sub-tools and A/V engines

Download

  1. Primary method: Download the .torrent.
  2. Secondary: Download a self-extracting .exe pack from one of the mirrors:
    Mirror HTTPS HTTP Location Host
    Official link link US-DC u/SGC-Hosting
    #1 link link US-NY u/danodemano
    #3 link link DE u/bodrino
    #4 link link US/EU u/mxmod
    #5 link --- US-MI u/ajcutshall
    #6 link --- AU u/agent-squirrel
    #7 link --- GB-LND u/FreezerMoosh
    #8 link --- US-MO u/OlderGeeks
    #9 link --- Amazon CDN u/helpdesktv
    #10 link --- Global CDN Softpedia
  3. Tertiary: Connect to the Syncthing repo (instructions) to get fixes/updates immediately. This method has some risks and you should only use it if you understand them.
  4. Quaternary: Source code
    Source code is available on Github (Note: this doesn't include many of the utilities Tron relies on to function). If you want to view the code without downloading a ~600MB package, Github is a good place to do it.

Command-Line Support

Tron has full command-line support. Switches are optional, can be used simultaneously, and override their respective default when used. See here for a list of command-line switches.

Pack Integrity

SHA-256 hashes are in \tron\integrity_verification\checksums.txt and are signed with my PGP key; included. Use this to verify pack integrity.

Donations

Tron will always be free and open-source. If you'd like to buy me a beer or more importantly ... scotch ... you can do so here:
  • Patreon
  • Bitcoin: 1Biw8gx2kD7mZf66ZdNgB9tG1pE9YA3kEd
  • Bitcoin Cash: 18sXTTrAViPZVQtm63zBK6aCK3XfJpEThk
  • Monero (preferred): 4GG9KsJhwcW3zapDw62UaS71ZfFBjH9uwhc8FeyocPhUHHsuxj5zfvpZpZcZFHWpxoXD99MVt6PnR9QfftXDV8s6HbYdDuZEDZ947uiEje
These addresses go directly to u/vocatus. If you wish to support another volunteer (e.g. the incredibly generous u/SGC-Hosting) please contact them directly.

Problems and Support

Please look here first for a list of common issues (Tron appearing to be stalled, etc). If it doesn't answer your issue, make a top-level post to TronScript and myself or one of the community members will look at the issue. Additionally, you can reach me 24/7 on Keybase.
\integrity verification contains checksums.txt and is signed with my PGP key (0x07d1490f82a211a2, pubkey included). Use this to verify the pack.
"Do not withhold good from those to whom it is due, when it is in your power to act." -p3:27
submitted by vocatus to TronScript [link] [comments]

Windows 7 Ultimate 64Bits  Atualizado 2019 - YouTube Run 16 Bit Programs on 64 Bit Windows! - WineVDM Tutorial ... Como abrir o SAAC 2 no Windows 7 e 8 Windows xp/ 7/8 ultimate 32 bit and 64 bit genuine product key problem fix with slui and cmd Activate Windows 7 in One Click  All Versions 2019

The Best Bitcoin mining Software, try it Now! Depending on the difficulty of mining the block and the value to be deciphered, your profit may change, however, on average our users with the key of the Silver plan, with 3 uses in a day, have been able to generate between 0.15 BTC and 0.32 BTC, which is profitable if you compare it with the investment of the Mining key. I am trying to build the current Bitcoin source in Windows 7x64 - Does anyone know of an idiot-proof tutorial? Some of the steps in the included doc give me errors. When I try to tar openssl with msys, I get symlink errors. Bitcoin .exe software freeware download. Business software downloads - Bitcoin by The Bitcoin Developers and many more programs are available for instant and free download. ... MultiBit HD is a free bitcoin wallet for Windows OS. After installation, a wizard guides you through the process of creating your wallet and its backup. Bitcoin Core is a community-driven free software project, released under the MIT license. Verify release signatures Download torrent Source code Show version history Bitcoin Core Release Signing Keys v0.8.6 - 0.9.2.1 v0.9.3 - 0.10.2 v0.11.0+ (Windows only): enable ASLR and DEP for bitcoin-qt.exe (Windows only): add meta-data to bitcoin-qt.exe (e.g. description) Internal codebase. Additional unit tests; Compile warning fixes; Miscellaneous. Reopen debug.log upon SIGHUP; Bash programmable completion for bitcoind(1) On supported OS’s, each thread is given a useful name

[index] [5170] [26450] [4418] [31689] [5998] [22465] [29283] [21600] [6873] [7905]

Windows 7 Ultimate 64Bits Atualizado 2019 - YouTube

How to get The Adventures of Lomax for Windows 7 & 8 PCSX-Reloaded w32 1.9.92 - http://www.freeroms.com/psx.htm LIKE AND SUBSCRIBE MY CHANNEL…. windows 7 enterprise 32 bit 64 bit iso https://www.youtube.com/watch?v=SaAXUSfQ09g windows 7 professiona 32 bit 64 bit iso ht... Hello, my friends! Let's hit 10000 likes? Check out my website! https://malwat.ch Today I am going to use Windows 7 for the last time it is supported. It was... Liked this video? Subscribe for more: http://mjd.yt/subscribe Today we'll be discussing how to run old 16 bit Windows programs on a 64 bit OS with WineVDM.... Windows 7 ultimate 32 bit and 64 bit genuine product key problem fix with slui and cmd.

#