Quote from: RVienz on July 09, 2014, 12:19:49 PM

stunna am i join this Sign Campaign ??

i need bitcoin for donate

You'll probably get banned if you continue to post like you have done. Not to mention you just copied and pasted another post verbatim:

Quote from: grod on October 02, 2011, 08:29:22 PM

It's hard enough to get the half-baked alt chain software to run at all (and speed is of the essence knowing they are all quickly collapsing pyramids) never mind configuring a VM with appropriate hardware access. Here are steps I've taken which I think are "good enough" to be advice -- it's worked for me for 4 shitcoin chains so far.

1. Don't use Windows and pre-built .exes. Just don't. Ever. Nothing inherently wrong with Microsoft software, but it is well understood and commonly used by the botnet types. Staying out of the monoculture is a form of security by obscurity.
2. Create a new account with no group membership. I call mine "goatse" for obvious but nostalgic reasons. Make absolutely sure that account doesn't have read or write access outside of their home directory. Make doubly sure they can't read the raw hard drive device.
3. Log out of your main account and into that account whenever compiling or running the alt chain software. Remember that compilation & installation scripts are code!
4. Do not browse exchange sites you have coinage in and definitely do not save passwords in the browser when logged in as this account.
5. If you log into this account via ssh DO NOT enable X proxying. It's trivial to read your keystrokes, do screen captures, etc when X is proxied. Let me repeat this one, make sure X proxying is disabled. If you can type 'xterm' and see it show up on your main account's screen you're vulnerable.

And yes, I even follow this for official bitcoin software. On a different account than "goatse" of course.

Quote from: RVienz on July 09, 2014, 08:19:01 AM

It's hard enough to get the half-baked alt chain software to run at all (and speed is of the essence knowing they are all quickly collapsing pyramids) never mind configuring a VM with appropriate hardware access. Here are steps I've taken which I think are "good enough" to be advice -- it's worked for me for 4 shitcoin chains so far.

1. Don't use Windows and pre-built .exes. Just don't. Ever. Nothing inherently wrong with Microsoft software, but it is well understood and commonly used by the botnet types. Staying out of the monoculture is a form of security by obscurity.
2. Create a new account with no group membership. I call mine "goatse" for obvious but nostalgic reasons. Make absolutely sure that account doesn't have read or write access outside of their home directory. Make doubly sure they can't read the raw hard drive device.
3. Log out of your main account and into that account whenever compiling or running the alt chain software. Remember that compilation & installation scripts are code!
4. Do not browse exchange sites you have coinage in and definitely do not save passwords in the browser when logged in as this account.
5. If you log into this account via ssh DO NOT enable X proxying. It's trivial to read your keystrokes, do screen captures, etc when X is proxied. Let me repeat this one, make sure X proxying is disabled. If you can type 'xterm' and see it show up on your main account's screen you're vulnerable.

And yes, I even follow this for official bitcoin software. On a different account than "goatse" of course.