• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

RC5 as a security feature?

Windogg

Lifer
IIRC, a member that had his laptop stolen was able to recover it because his system was faithfully flushing blocks in the hands of the thief. Anyone have a link to the thread? I hoping to use this as evidence that distributed computing has many uses. In my office, over 80% of all systems are laptops and travel quite often. I was wondering if having each system crack maybe 100 block per day and flushing it would be a good security measure? Just a though to get more systems cracking for TA.


Windogg
 
Another good feature is that the newer clients have an option to not crack while running on battery power. Not having that option before was a major deterrent to me putting the client on laptops.
 
I know about the story and did a search on the forum.

I found this thread for you.

There also must be a press release somewhere on the internet by one of the leading news agencies, but I can't find it.
It pretty much boils down to what is said in the above thread. 🙂

Good luck with convincing your companies decision makers on installing the client.
Keep us posted. More of us are interested in this.

CU, Peter.
 
Thanks PeterN 🙂

Ok, need some help here now. All company traffic passes through a proxy. As of right now, individual desktops connect to the main keyserver on their own to fetch and flush. Loading the DNet client like this would be useless since blocks can only be flushed within the company network. Should the laptop be stolen, the block would go unflushed because the proxy cannot be found.

What are my options?

Windogg

 
have the cows flush to a public pproxy through the firewall using port 80.
I havent had to do this so I wont be of help.
Also I remind reading that the latest clients allow several proxies.
If it works you could set the local proxy as primary, and add a public proxy as secondary. should the laptop be stolen, it would start dumping to the secondary, and it's IP be tracked.
 
Also, if the client cannot reach its designated proxy after several attempts, it will attempt to connect to a distributed.net keyserver anyway, unless you specifically configure it not to (nofallback=true).
 
Back
Top