Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Please RED Implement this in the next firmware.

Björn Benckert

Björn Benckert

Well-known member
Joined
Dec 5, 2007
Messages
7,423
Reaction score
74
Points
48
Age
52
Website
www.syndicate.se
As you might have heard.
Our Dragon Package was stolen two weeks ago on a music video shoot here in Stockholm.
A few weeks before that another Dragon package was stolen also here in Stockholm.
And last week a full set of brand new COOKE S4´s was stolen in a storage room, a fully kitted alexa XT was left behind by the breakin thieves.
Then today, there was a Fully Kitted ALEXA XT with a master prime stolen on the street. As I understand the AC and assistant was pushed over and the camera was stolen pretty much from the tripod.


So please RED. To make the cameras less desirable as stolen could you please implement a security code.

I Think it would help if there was a time lock that could be set in between dates. For example 23-25th of feb. To start the camera in between those dates you would need the master code or client code.

This way we could also have better control over rental clients that rent the gear with "5 travel days and 1 shooting day" and such. Basically preset the entry code so they only get access to the camera for the booked shooting days.


I think our dragon would still be home if this had already been implemented. :(
 
YES.

http://www.digitaltrends.com/mobile/smartphone-kill-switch-success-nyc-london-san-francisco/

Ever since the iPhone added a kill switch, iPhone thefts in the three cities have decreased significantly, reports the BBC. Phone thieving dropped 50 percent in London, 40 percent in San Francisco, and 25 percent in New York over the 12 months after the feature was added.

Read more: http://www.digitaltrends.com/mobile...ccess-nyc-london-san-francisco/#ixzz3Rvpf2jrR
Follow us: @digitaltrends on Twitter | digitaltrendsftw on Facebook
Click to expand...
 
Bjorn - you must be completely in despair.

I agree you should be able to engage system like this :
+) "Camera Unlocked for N days" splash screen on startup that user (Optionally) has to dismiss. (When in Time lock mode)
+) When down to Zero days - A message appears on camera startup saying please contact www.Red.com/enable.com entering "12345" (serial number of camera)
+) The designated owner in red.com has the option of setting the camera as stolen (In which case a 'stolen' token is given), or if they wish the camera to be unlocked for another N days - then a suitable token is created.
+) Red.com would send an email of the IP address of the camera to the designated owner - and keep the last 3 IP addresses online for easy reference (and provide a geotag of the IP physical location)
+) if the Token is invalid when entered into the brain the user is advised this is invalid. Max of 5 Attempts . Then 10 minute gap between each attempt.
+) If the 'this camera is stolen' token is entered ... A message advised to call "0123456799 with the code #1234567" is shown. This
A service that Red.com charge the own if called (say $50). RED can unlock the camera with another token - or bring the police into help recover the camera / arrest the person who made the call.
+) Upgrading the Firmware with a lock on should Keep the Timelock settings. Changing the Cameraa date should be independent of the RTC.
+) When camera is locked Current date is displayed. User is able to change this Date - But must visit www.red.com (to get an authorising token). - The Resulting token incorporates the today's Day (and Also If the camera is stolen!).

AJ
 
Fantastic idea.

But you would need a code for changing the firmware as well.
 
Good idea Björn! This is a fantastic idea for camera rentals and for safety. Wonder why no one thought of this before?
This and a GPS inside a module or camera would be perfect :)
 
Antony Newman said:
Bjorn - you must be completely in despair.

I agree you should be able to engage system like this :
+) "Camera Unlocked for N days" splash screen on startup that user (Optionally) has to dismiss. (When in Time lock mode)
+) When down to Zero days - A message appears on camera startup saying please contact www.Red.com/enable.com entering "12345" (serial number of camera)
+) The designated owner in red.com has the option of setting the camera as stolen (In which case a 'stolen' token is given), or if they wish the camera to be unlocked for another N days - then a suitable token is created.
+) Red.com would send an email of the IP address of the camera to the designated owner - and keep the last 3 IP addresses online for easy reference (and provide a geotag of the IP physical location)
+) if the Token is invalid when entered into the brain the user is advised this is invalid. Max of 5 Attempts . Then 10 minute gap between each attempt.
+) If the 'this camera is stolen' token is entered ... A message advised to call "0123456799 with the code #1234567" is shown. This
A service that Red.com charge the own if called (say $50). RED can unlock the camera with another token - or bring the police into help recover the camera / arrest the person who made the call.
+) Upgrading the Firmware with a lock on should Keep the Timelock settings. Changing the Cameraa date should be independent of the RTC.
+) When camera is locked Current date is displayed. User is able to change this Date - But must visit www.red.com (to get an authorising token). - The Resulting token incorporates the today's Day (and Also If the camera is stolen!).

AJ
Click to expand...

I think we could leave RED out of the unlocking procedures.

Would be enough with the following:
Time lock between dateX and date Y: code1 (for example here I can put the name for the given rental client as a code)
Then additional X days: code2 (here i can give X number of additional days with another code, and also tap in how many days.
Then super user, code3: owner can set his own code to unlock / change / remove / add time locks etc.


With the above I could for example, set a lock on the camera for a booking, then when the client call and ask for more days. I have an option to a: give hime the code2... And if the shit hits the fan and a client is standing on set not able to shoot and I forgot to set the time locks correctly or such and I deal with a client I can trust then I could just give him the super user cod... And he can then open the camera for all future use if wanted and when camera comes back home I can reset/change that code to something new and go on to the next client.

And off course this should be a click in option, for those who think it´s a bad idea to put any kind of locks on their camera they just tap in their superuser code and change or initiate none of the above.

Basically then we could all have our cameras on a time lock at all times and those F€%#€ing thieves would know that a stolen RED camera is only a couple of weeks of fun at best.

So with the above and having the change date feature underneath the superuser password. Thieves would at least need to hack the camera to use it for any extended time periods.

So it does not need to be much more advanced than the code lock on an Iphone for super user and then a few definable codes underneath. We already have our login codes for the firmware downloads... so possibly that could be our superuser codes to start with.
 
I also vote for GPS modules. I just bought a couple of these: http://www.traxfamily.com
Works really well so to make them last they need to sit on a USB power source... But imagine a V lock reseller that implemented this things inside of the Vlock casings... and made them so the tracker went on only when power was taken from the battery... Or yes, possibly put something in that new RED SKULL, or side handle or screen, or +1 module or pretty much every module... they cost about 150 USD each with a 2 year contract so I could definitely see that being added to just about anything.
 
Björn Benckert said:
As you might have heard.
Our Dragon Package was stolen two weeks ago on a music video shoot here in Stockholm.
A few weeks before that another Dragon package was stolen also here in Stockholm.
And last week a full set of brand new COOKE S4´s was stolen in a storage room, a fully kitted alexa XT was left behind by the breakin thieves.
Then today, there was a Fully Kitted ALEXA XT with a master prime stolen on the street. As I understand the AC and assistant was pushed over and the camera was stolen pretty much from the tripod.

:(
Click to expand...

BJörn,
Very sorry to hear the bad news, good luck man.
 
I agree. It's a shame that once peaceful and crime less Scandinavian countries are getting all these issues.
RED should implement something to protect its owners...
 
+1 from me.

Björn's idea seems very 'light' in terms of new code sitting in an existing framework... so RED should go for this - it would certainly be added 'safety' feature and act as a deterrent.
 
Maybe its not possible if "the hold button in to restore factory defaults" or such overwrites it but even so I think it could be use full.
 
Sad to hear about the mess and hoping all works out well.
Positive vibes headed to Stockholm.

I recall proposing this in similar form a bunch of years back, not sure but it might have even been before REDuser on DVXuser and one of the ThinkTanks. The discussion brought up the issues with logistics and accidental lock outs and bunch of potential issues for Red.

One option could be an external dongle sitting in the office, used for camera unlocking.
So no pass codes are forgotten. Just setting the time frame for security check and dongle does the rest and camera is unusable without it past the pre-set date. Or weekly/monthly auto security check features.
 
You must log in or register to reply here.
Back
Top