Potential privacy issue with Canon cameras and copyright info setting

Jan 29, 2011
10,675
6,121
I sold a 1DX II that had all my copyright and contact info in it to another pro photographer. He didn’t normally enter his info in the camera just in post. One of his clients is a University sports team and in their contract they have to deliver the RAW files and the University has copyright of any images shot of their team members or on their property. He got in a ton of shit because he delivered RAW files with copyright info that was incorrect.

I know it isn’t directly related to the thread but close enough to mention it.
 
  • Haha
Reactions: 1 user
Upvote 0

SteveC

R5
CR Pro
Sep 3, 2019
2,678
2,592
Gen X thank you very much. And I learned Pascal in college on an original 128K Apple Macintosh! :)

OK, but pascal doesn't null terminate its strings...at least not the original pascal. the strings are indexed [1] to [255] and location [0] is actually the length of the string, so no termination needed. Maybe later versions of Pascal do something different, but this was Pascal as of 1983.

C and C++ do null terminate their strings, writing an ascii zero in the first position would give you an empty string.
 
Upvote 0

mdcmdcmdc

EOS R7, M5, 100 (film), Sony α6400
CR Pro
Sep 4, 2020
318
442
OK, but pascal doesn't null terminate its strings...at least not the original pascal. the strings are indexed [1] to [255] and location [0] is actually the length of the string, so no termination needed. Maybe later versions of Pascal do something different, but this was Pascal as of 1983.

C and C++ do null terminate their strings, writing an ascii zero in the first position would give you an empty string.

Yes that was the joke. When they set the first byte, the length byte, to zero, the string has zero length so it is ignored.
 
  • Like
Reactions: 1 user
Upvote 0

SteveC

R5
CR Pro
Sep 3, 2019
2,678
2,592
Yes that was the joke. When they set the first byte, the length byte, to zero, the string has zero length so it is ignored.

Oh THAT first byte. OK, gotcha!!! :ROFLMAO: (I was thinking of the first byte of the string proper, i.e., string[1].)

(Amusing, though how it ends up working the same way for Pascal and C for two totally different reasons!)
 
  • Like
Reactions: 1 user
Upvote 0

mdcmdcmdc

EOS R7, M5, 100 (film), Sony α6400
CR Pro
Sep 4, 2020
318
442
Oh THAT first byte. OK, gotcha!!! :ROFLMAO: (I was thinking of the first byte of the string proper, i.e., string[1].)

(Amusing, though how it ends up working the same way for Pascal and C for two totally different reasons!)

That is pretty funny. My mind immediately went to the Pascal length byte, but you’re right, putting the C null terminator there would have the same effect.

They probably actually wrote it in C++. To delete the strings, they called std::string::clear(), and their compiler implemented it that way.

Cheers!
 
Upvote 0

SteveC

R5
CR Pro
Sep 3, 2019
2,678
2,592
That is pretty funny. My mind immediately went to the Pascal length byte, but you’re right, putting the C null terminator there would have the same effect.

They probably actually wrote it in C++. To delete the strings, they called std::string::clear(), and their compiler implemented it that way.

Cheers!

Hmm...std::string supposedly works differently from the old school char * string, and as far as I know isn't null terminated. But on second thought, I should try some experiments, because I know that std::string's .c_str( ) function call does return a null-terminated string, so maybe, in fact, it does use a null terminator and all the class buys you is automagic resizing and concatenation operators. (If I can set some std::string's first character to zero and still have it return a length greater than zero when I call length( ), it's doing something different, regardless of whether c_str() returns an "empty" char * string [which I would expect it to do].) Such experiments should look at the actual address returned by c_str( ) as well as its referent....
 
  • Like
Reactions: 1 user
Upvote 0
I don't see the privacy issue here. If the camera is sold 2nd hand or stolen, and someone finds out the [previous] owner's name. So? People aren't secretive about their camera model.
Well that might be true for Canon cameras, but imagine someone found out you once had an affair with a Nikon camera, that could thoroughly taint your reputation. :LOL:
 
  • Like
  • Haha
Reactions: 1 users
Upvote 0

mdcmdcmdc

EOS R7, M5, 100 (film), Sony α6400
CR Pro
Sep 4, 2020
318
442
Well that might be true for Canon cameras, but imagine someone found out you once had an affair with a Nikon camera, that could thoroughly taint your reputation. :LOL:
When I was in between my last film SLR (EOS 100) and my first DSLR (EOS 20D), I had a brief fling with an Olympus C-5050. She was a hot little number with some great specs in those days (wink, wink)! And hoo-wee what a lens! But it didn't last long. She didn't have the fastest autofocus in the camera bag, if you know what I mean.
 
Upvote 0