Topic: [ANN]❁ KORE Tor Masternodes, Browser, VoIP, Aether OS, KOREPhone, KOREbay Funded - page 83. (Read 152401 times)
January 10, 2018, 04:12:40 AM
s this coin available on any major coin exchange? I would like to purchase a few coins but I do not want to test any new exchanges. Do not believe in them
January 10, 2018, 04:08:34 AM
I'm a little worried that I will have difficulties with launching the nodes, in Russia there is absolutely no information on Kore.
And the level of my English leaves much to be desired.
And the level of my English leaves much to be desired.
January 10, 2018, 04:06:34 AM
Hello from Russia.) If I buy 500 coins, I will not regret it?=)
as always, invest at your own risk...do your research
Go KORE, Go BTC!!!
What a childish question.
Children take no responsibility for their actions.
Awesome to hear from Russia!
MikeMike
Above there was a bit of Russian humor)
January 10, 2018, 03:08:45 AM
Hi
I updated my wallet conf file with more nodes and its all working fine over here.
I updated my wallet conf file with more nodes and its all working fine over here.
The update will include a new nodes list.
January 10, 2018, 02:32:12 AM
Hello from Russia.) If I buy 500 coins, I will not regret it?=)
as always, invest at your own risk...do your research
Go KORE, Go BTC!!!
What a childish question.
Children take no responsibility for their actions.
Awesome to hear from Russia!
MikeMike
January 10, 2018, 12:42:14 AM
Hello from Russia.) If I buy 500 coins, I will not regret it?=)
as always, invest at your own risk...do your research
Go KORE, Go BTC!!!
January 09, 2018, 11:35:01 PM
Hello from Russia.) If I buy 500 coins, I will not regret it?=)
January 09, 2018, 09:26:46 PM
Hey guys, how you doing?
Stopping by to wish a great week to everyone.
The team is working hard on the Kore projects.
Go Kore, Go BTC
Stopping by to wish a great week to everyone.
The team is working hard on the Kore projects.
Go Kore, Go BTC
January 09, 2018, 03:44:23 PM
For whatever reason I am getting multiple errors when trying to setup my masternode with Digital Ocean. After executing ./test/sh it begins.
hash.cpp: in function 'unsigned int MurmurHash3 (unsigned int, const std::vector&':
hash.cpp:50:16 warning this statement my fall through [Wimplicit-fallthrough=] and so on and so on.
An clue what is going on? Tried Ubuntu v16 and v17 but still the same issues.
Lost at the moment...
Thanks,
Hank
hash.cpp: in function 'unsigned int MurmurHash3 (unsigned int, const std::vector
hash.cpp:50:16 warning this statement my fall through [Wimplicit-fallthrough=] and so on and so on.
An clue what is going on? Tried Ubuntu v16 and v17 but still the same issues.
Lost at the moment...
Thanks,
Hank
Make sure you use the swapfile script to make your VPS.
January 09, 2018, 03:05:22 PM
Texus Huck still around? haven't read anything from him as of late 
January 08, 2018, 09:36:56 PM
For whatever reason I am getting multiple errors when trying to setup my masternode with Digital Ocean. After executing ./test/sh it begins.
hash.cpp: in function 'unsigned int MurmurHash3 (unsigned int, const std::vector&':
hash.cpp:50:16 warning this statement my fall through [Wimplicit-fallthrough=] and so on and so on.
An clue what is going on? Tried Ubuntu v16 and v17 but still the same issues.
Lost at the moment...
Thanks,
Hank
hash.cpp: in function 'unsigned int MurmurHash3 (unsigned int, const std::vector
hash.cpp:50:16 warning this statement my fall through [Wimplicit-fallthrough=] and so on and so on.
An clue what is going on? Tried Ubuntu v16 and v17 but still the same issues.
Lost at the moment...
Thanks,
Hank
You are most likely not in root, doing something wrong or not following the guide directly.
Go to the Discord KORE support thread for help for Linux from the Community
and we are offering an automated setup service soon.
https://discord.gg/VD2kytE
For windows we do not offer support due to the unreliability of security of windows.
The do it yourself Masternode Setup guide can be found on the website.
http://kore.life
MikeMike
January 08, 2018, 04:38:49 PM
For whatever reason I am getting multiple errors when trying to setup my masternode with Digital Ocean. After executing ./test/sh it begins.
hash.cpp: in function 'unsigned int MurmurHash3 (unsigned int, const std::vector&':
hash.cpp:50:16 warning this statement my fall through [Wimplicit-fallthrough=] and so on and so on.
An clue what is going on? Tried Ubuntu v16 and v17 but still the same issues.
Lost at the moment...
Thanks,
Hank
hash.cpp: in function 'unsigned int MurmurHash3 (unsigned int, const std::vector
hash.cpp:50:16 warning this statement my fall through [Wimplicit-fallthrough=] and so on and so on.
An clue what is going on? Tried Ubuntu v16 and v17 but still the same issues.
Lost at the moment...
Thanks,
Hank
January 08, 2018, 10:54:22 AM
Hey guys just wanted to give you guys a quick update, I'm working on a system for you guys to easily check up on your masternodes (or regular nodes) without needing to open up a shell connection. After a ton of research and tests I'v finally been able to create a working concept and basic system. Once I add a little bit to the UI I will release the basic system for everyone free of charge. After that I will build a full control system straight from the UI which will be a paid system and will help support development.
Matrix
Matrix
Awesome!
January 07, 2018, 09:54:07 PM
Hey guys just wanted to give you guys a quick update, I'm working on a system for you guys to easily check up on your masternodes (or regular nodes) without needing to open up a shell connection. After a ton of research and tests I'v finally been able to create a working concept and basic system. Once I add a little bit to the UI I will release the basic system for everyone free of charge. After that I will build a full control system straight from the UI which will be a paid system and will help support development.
Matrix
Matrix
January 07, 2018, 08:38:52 PM
I just wanna say thanks for all that helped me get my 1st set of masternodes rolling!! its great to be part of a great group!
January 07, 2018, 11:23:26 AM
Hello everybody,
So the flaws on the Cpus that came to light are very bad and you definetly should take the time to patch it up as good as you can, here is a quick explanation of the problems found.
Meltdown, applicable to virtually every Intel chip made for many years, along with certain high-performance ARM designs, is the easier to exploit and enables any user program to read vast tracts of kernel data. The good news, such as it is, is that Meltdown also appears easier to robustly guard against. The flaw depends on the way that operating systems share memory between user programs and the kernel, and the solution—albeit a solution that carries some performance penalty—is to put an end to that sharing.
Spectre, applicable to chips from Intel, AMD, and ARM, and probably every other processor on the market that offers speculative execution, too, is more subtle. It encompasses a trick testing array bounds to read memory within a single process, which can be used to attack the integrity of virtual machines and sandboxes, and cross-process attacks using the processor's branch predictors (the hardware that guesses which side of a branch is taken and hence controls the speculative execution). Systemic fixes for some aspects of Spectre appear to have been developed, but protecting against the whole range of fixes will require modification (or at least recompilation) of at-risk programs.
Here is some good tips to better protect yourself from these cpu flaws that were found:
https://www.pcworld.com/article/3245810/security/how-to-protect-your-pc-meltdown-spectre-cpu-flaws.html
Here some good info on this problem:
https://arstechnica.com/gadgets/2018/01/meltdown-and-spectre-heres-what-intel-apple-microsoft-others-are-doing-about-it/
These problems are a good example of why we need a more secure OS like AetherOS to protect our freedom and privacy.
Go Kore, Go BTC
Cheers
So the flaws on the Cpus that came to light are very bad and you definetly should take the time to patch it up as good as you can, here is a quick explanation of the problems found.
Meltdown, applicable to virtually every Intel chip made for many years, along with certain high-performance ARM designs, is the easier to exploit and enables any user program to read vast tracts of kernel data. The good news, such as it is, is that Meltdown also appears easier to robustly guard against. The flaw depends on the way that operating systems share memory between user programs and the kernel, and the solution—albeit a solution that carries some performance penalty—is to put an end to that sharing.
Spectre, applicable to chips from Intel, AMD, and ARM, and probably every other processor on the market that offers speculative execution, too, is more subtle. It encompasses a trick testing array bounds to read memory within a single process, which can be used to attack the integrity of virtual machines and sandboxes, and cross-process attacks using the processor's branch predictors (the hardware that guesses which side of a branch is taken and hence controls the speculative execution). Systemic fixes for some aspects of Spectre appear to have been developed, but protecting against the whole range of fixes will require modification (or at least recompilation) of at-risk programs.
Here is some good tips to better protect yourself from these cpu flaws that were found:
https://www.pcworld.com/article/3245810/security/how-to-protect-your-pc-meltdown-spectre-cpu-flaws.html
Here some good info on this problem:
https://arstechnica.com/gadgets/2018/01/meltdown-and-spectre-heres-what-intel-apple-microsoft-others-are-doing-about-it/
These problems are a good example of why we need a more secure OS like AetherOS to protect our freedom and privacy.
Go Kore, Go BTC
Cheers
Thanks MXRider for the information. Here is another link to read.
https://www.coindesk.com/meltdown-spectre-cpu-flaws-mean-cryptocurrency/
Awesome to see what could be the result of some brave whistlblowers and decent people coming forward
and possibly forcing their hand to own up to these exploits.
January 06, 2018, 11:51:25 PM
Hello everybody,
So the flaws on the Cpus that came to light are very bad and you definetly should take the time to patch it up as good as you can, here is a quick explanation of the problems found.
Meltdown, applicable to virtually every Intel chip made for many years, along with certain high-performance ARM designs, is the easier to exploit and enables any user program to read vast tracts of kernel data. The good news, such as it is, is that Meltdown also appears easier to robustly guard against. The flaw depends on the way that operating systems share memory between user programs and the kernel, and the solution—albeit a solution that carries some performance penalty—is to put an end to that sharing.
Spectre, applicable to chips from Intel, AMD, and ARM, and probably every other processor on the market that offers speculative execution, too, is more subtle. It encompasses a trick testing array bounds to read memory within a single process, which can be used to attack the integrity of virtual machines and sandboxes, and cross-process attacks using the processor's branch predictors (the hardware that guesses which side of a branch is taken and hence controls the speculative execution). Systemic fixes for some aspects of Spectre appear to have been developed, but protecting against the whole range of fixes will require modification (or at least recompilation) of at-risk programs.
Here is some good tips to better protect yourself from these cpu flaws that were found:
https://www.pcworld.com/article/3245810/security/how-to-protect-your-pc-meltdown-spectre-cpu-flaws.html
Here some good info on this problem:
https://arstechnica.com/gadgets/2018/01/meltdown-and-spectre-heres-what-intel-apple-microsoft-others-are-doing-about-it/
These problems are a good example of why we need a more secure OS like AetherOS to protect our freedom and privacy.
Go Kore, Go BTC
Cheers
So the flaws on the Cpus that came to light are very bad and you definetly should take the time to patch it up as good as you can, here is a quick explanation of the problems found.
Meltdown, applicable to virtually every Intel chip made for many years, along with certain high-performance ARM designs, is the easier to exploit and enables any user program to read vast tracts of kernel data. The good news, such as it is, is that Meltdown also appears easier to robustly guard against. The flaw depends on the way that operating systems share memory between user programs and the kernel, and the solution—albeit a solution that carries some performance penalty—is to put an end to that sharing.
Spectre, applicable to chips from Intel, AMD, and ARM, and probably every other processor on the market that offers speculative execution, too, is more subtle. It encompasses a trick testing array bounds to read memory within a single process, which can be used to attack the integrity of virtual machines and sandboxes, and cross-process attacks using the processor's branch predictors (the hardware that guesses which side of a branch is taken and hence controls the speculative execution). Systemic fixes for some aspects of Spectre appear to have been developed, but protecting against the whole range of fixes will require modification (or at least recompilation) of at-risk programs.
Here is some good tips to better protect yourself from these cpu flaws that were found:
https://www.pcworld.com/article/3245810/security/how-to-protect-your-pc-meltdown-spectre-cpu-flaws.html
Here some good info on this problem:
https://arstechnica.com/gadgets/2018/01/meltdown-and-spectre-heres-what-intel-apple-microsoft-others-are-doing-about-it/
These problems are a good example of why we need a more secure OS like AetherOS to protect our freedom and privacy.
Go Kore, Go BTC
Cheers
Thanks MXRider for the information. Here is another link to read.
https://www.coindesk.com/meltdown-spectre-cpu-flaws-mean-cryptocurrency/
January 06, 2018, 03:16:19 PM
Hi guys,
I have been accumulating Kore for a while and have now enough for a Node!
Could anybody give me a hand setting it up?
I am at step 9 of the masternode setup guide and need to include a line at the bottom of masternode.config, however, there is no "masternode.config" in my Kore directory in Ubuntu.
Do I need to create a new file with "nano" like I did with kore.config a steps back?
Thanks!
I have been accumulating Kore for a while and have now enough for a Node!
Could anybody give me a hand setting it up?
I am at step 9 of the masternode setup guide and need to include a line at the bottom of masternode.config, however, there is no "masternode.config" in my Kore directory in Ubuntu.
Do I need to create a new file with "nano" like I did with kore.config a steps back?
Thanks!
Please go to the KORE Support thread in Discord.
When "TheMatrix101" gets in later today I'm sure he could help
but ask those in the thread. There are plenty of ones who are good.
https://discord.gg/VD2kytE
Hello, how you doing?
Please come to the Discord Kore support channel, im there and i can help you too
January 06, 2018, 03:15:16 PM
Hello everybody,
So the flaws on the Cpus that came to light are very bad and you definetly should take the time to patch it up as good as you can, here is a quick explanation of the problems found.
Meltdown, applicable to virtually every Intel chip made for many years, along with certain high-performance ARM designs, is the easier to exploit and enables any user program to read vast tracts of kernel data. The good news, such as it is, is that Meltdown also appears easier to robustly guard against. The flaw depends on the way that operating systems share memory between user programs and the kernel, and the solution—albeit a solution that carries some performance penalty—is to put an end to that sharing.
Spectre, applicable to chips from Intel, AMD, and ARM, and probably every other processor on the market that offers speculative execution, too, is more subtle. It encompasses a trick testing array bounds to read memory within a single process, which can be used to attack the integrity of virtual machines and sandboxes, and cross-process attacks using the processor's branch predictors (the hardware that guesses which side of a branch is taken and hence controls the speculative execution). Systemic fixes for some aspects of Spectre appear to have been developed, but protecting against the whole range of fixes will require modification (or at least recompilation) of at-risk programs.
Here is some good tips to better protect yourself from these cpu flaws that were found:
https://www.pcworld.com/article/3245810/security/how-to-protect-your-pc-meltdown-spectre-cpu-flaws.html
Here some good info on this problem:
https://arstechnica.com/gadgets/2018/01/meltdown-and-spectre-heres-what-intel-apple-microsoft-others-are-doing-about-it/
These problems are a good example of why we need a more secure OS like AetherOS to protect our freedom and privacy.
Go Kore, Go BTC
Cheers
So the flaws on the Cpus that came to light are very bad and you definetly should take the time to patch it up as good as you can, here is a quick explanation of the problems found.
Meltdown, applicable to virtually every Intel chip made for many years, along with certain high-performance ARM designs, is the easier to exploit and enables any user program to read vast tracts of kernel data. The good news, such as it is, is that Meltdown also appears easier to robustly guard against. The flaw depends on the way that operating systems share memory between user programs and the kernel, and the solution—albeit a solution that carries some performance penalty—is to put an end to that sharing.
Spectre, applicable to chips from Intel, AMD, and ARM, and probably every other processor on the market that offers speculative execution, too, is more subtle. It encompasses a trick testing array bounds to read memory within a single process, which can be used to attack the integrity of virtual machines and sandboxes, and cross-process attacks using the processor's branch predictors (the hardware that guesses which side of a branch is taken and hence controls the speculative execution). Systemic fixes for some aspects of Spectre appear to have been developed, but protecting against the whole range of fixes will require modification (or at least recompilation) of at-risk programs.
Here is some good tips to better protect yourself from these cpu flaws that were found:
https://www.pcworld.com/article/3245810/security/how-to-protect-your-pc-meltdown-spectre-cpu-flaws.html
Here some good info on this problem:
https://arstechnica.com/gadgets/2018/01/meltdown-and-spectre-heres-what-intel-apple-microsoft-others-are-doing-about-it/
These problems are a good example of why we need a more secure OS like AetherOS to protect our freedom and privacy.
Go Kore, Go BTC
Cheers
January 06, 2018, 02:59:08 PM
Hi guys,
I have been accumulating Kore for a while and have now enough for a Node!
Could anybody give me a hand setting it up?
I am at step 9 of the masternode setup guide and need to include a line at the bottom of masternode.config, however, there is no "masternode.config" in my Kore directory in Ubuntu.
Do I need to create a new file with "nano" like I did with kore.config a steps back?
Thanks!
I have been accumulating Kore for a while and have now enough for a Node!
Could anybody give me a hand setting it up?
I am at step 9 of the masternode setup guide and need to include a line at the bottom of masternode.config, however, there is no "masternode.config" in my Kore directory in Ubuntu.
Do I need to create a new file with "nano" like I did with kore.config a steps back?
Thanks!
Please go to the KORE Support thread in Discord.
When "TheMatrix101" gets in later today I'm sure he could help
but ask those in the thread. There are plenty of ones who are good.
https://discord.gg/VD2kytE
Jump to: