I Installed the New Firmware with Password (R8)

[Pierre Lagarde]

Turning on the camera after installing I was asked my preferred language and then I was asked to set a numerical password. A numerical keyboard pops up. Confirm the password. Upon turning on the camera again I was asked to enter the password. After entering the password I had chosen I was given the option to never have the password asked for again. Having chosen that, upon the next turn on, no password was asked for. And my settings were not lost.

Am I the only one who finds the concept of setting a password for a camera deeply worrying, even if it’s not asked for again - perhaps at some point it will be needed again? I hope you wrote it down…

PS I just read the long thread on security, and I think there may be some useful answers there.

No. I think the use of a password to access your camera is ridiculous. What security concerns are there in photos you have taken? I’m not upgrading. Hope there is a way to bypass or eliminate it.

You seem to have misunderstood what the password is protecting, it's not for images. You can pull out the card and the images are not protected in any way. There is a way to eliminate it if all you are worried about it being asked for taking photos, it offers to do just that right after you set the password

Sorry, but why shouldn't it just offers the ability to not set a password, simply ? This implementation is abysmal.

Perhaps, abysmal. But bypassing it at boot doesn't equal not setting it. You still need it when accessing network functions which is the main driver.

Then why not adding the password feature at network functions level, not camera level, and still, even in this condition, why not allow to not set it ?

Implementation choice. What's the problem setting it? If you use network functions, you will anyway need to. If you don't, what's the problem?

Then bad implementation choice, uselessly restrictive and messy.

If password is to be used at network functions level, then add the feature at this point, and still allow the user to have the choice not to set it, and/or also to not use network functions (airplane mode or so).

That wouldn't confirm with the requirements as I understand. We have to implement similar things across network connected devices.

BTW, I would rather link all network/device connections to an airplane mode setting, that way, in one switch, you'd have the choice to have access or not to all that functions with the choice to protect them with a password or not, letting these choices to user.

The password would only be needed if you want to switch off airplane mode and if you set it.

So I can return the question to you : what's the problem with that ?

As above.

Ok more constructive answer, thank you .

It was a little brief but thanks I appreciate it

Anyway, what are those requirements ?.

That links to the EU cyber reliance act, which is in turn linked to the updated RED (European Union's Radio Equipment Directive) debated act. These have been formalised within three updates BSEN standards.

If the requirements is to have a password set anyway (so not to have the choice to not set it), then still nothing prevents to set it at network functions level, unless some European official has decided otherwise, of course, and forced the manufacturers to have it set at device level (which **** but still is possible).

That's not a simple answer and depends on the system it's being applied to and then to be able to validate internally and by an external test body that it fulfills the standards. For us we really need it at boot up. We could move it but it would have some significant consequences on updating the application layers, calibration functions and so forth.

I can only assume this is the sensible route for Canon given they have there software and hardware architecture already in place. Could it be done a different way from scratch? Yes I think so and I am aware of some IOT systems powered by WiFi that do this (some work out of the University of Liverpool).

I am at a loss to explain better Canon's systems as I simply know very little about them (it's not published understandably). I think only they could perhaps give you a more fruitful answer.

No doubt. Thanks for all that.

 

[David Hull]

Turning on the camera after installing I was asked my preferred language and then I was asked to set a numerical password. A numerical keyboard pops up. Confirm the password. Upon turning on the camera again I was asked to enter the password. After entering the password I had chosen I was given the option to never have the password asked for again. Having chosen that, upon the next turn on, no password was asked for. And my settings were not lost.

Am I the only one who finds the concept of setting a password for a camera deeply worrying, even if it’s not asked for again - perhaps at some point it will be needed again? I hope you wrote it down…

Mines easy. 1 2 3 4 5 6

Thats fine but 1 1 1 1 1 1 would be easier. The trouble is, each time you pick the camera up, you have to flip the little flip screen out and punch in the number. Apparently, that's true even if it has been hanging around your neck for a while and has powered down. By that time, that elusive once-in-a-lifetime shot is gone.

It looks like you have the option of telling it to ignore the PW but then what is the purpose of having it in the first place.

Because some features such as changing network connections, connecting to networks still require the password. You are not telling it to ignore the password except on boot up where you can opt not to type it in

So, in that condition, if you don't use networking connections, radios, or Ethernet (BT perhaps), you never have to deal with the PW after that first time?

And... if you DO decide to turn that stuff on and use it, you will have to remember your PIN, and punch it in, I guess.

They should just ask "do you want to set a PW... Y/N"

I would like to hear from those who actually fired up this new FW how it actually works.

PS I just read the long thread on security, and I think there may be some useful answers there.

 

[Zeee]

Turning on the camera after installing I was asked my preferred language and then I was asked to set a numerical password. A numerical keyboard pops up. Confirm the password. Upon turning on the camera again I was asked to enter the password. After entering the password I had chosen I was given the option to never have the password asked for again. Having chosen that, upon the next turn on, no password was asked for. And my settings were not lost.

Am I the only one who finds the concept of setting a password for a camera deeply worrying, even if it’s not asked for again - perhaps at some point it will be needed again? I hope you wrote it down…

Mines easy. 1 2 3 4 5 6

Thats fine but 1 1 1 1 1 1 would be easier. The trouble is, each time you pick the camera up, you have to flip the little flip screen out and punch in the number. Apparently, that's true even if it has been hanging around your neck for a while and has powered down. By that time, that elusive once-in-a-lifetime shot is gone.

It looks like you have the option of telling it to ignore the PW but then what is the purpose of having it in the first place.

They should just ask "do you want to set a PW... Y/N"

I would like to hear from those who actually fired up this new FW how it actually works.

Powering down/up and sleep did not ask for the password as I instructed it.

PS I just read the long thread on security, and I think there may be some useful answers there.

 

[Pierre Lagarde]

Nothing too dramatic

Indeed And sorry if I looked only critical.

What's buzzing me is the risk that represents this implementation in bricking your camera in fact. With a solution more dedicated to its target functions, the step of entering a password at startup (or wake up) would be avoided as it is functionally useless.

I don't like the idea that my camera won't be accessible if I need only to protect network connections. It's not a simple problem and I wonder finally if European officials may have been a bit "disconnected" on that one, and even Canon just p####d off by the requirements, if so, in the end .

This has been driven by standards bodies who act as advisors in this instance. The standards have been in progress for some time.

But that's another story I guess.

Thank you for your answer.

I bet they are... nothing's fast with them

 

[Ephemeris]

Turning on the camera after installing I was asked my preferred language and then I was asked to set a numerical password. A numerical keyboard pops up. Confirm the password. Upon turning on the camera again I was asked to enter the password. After entering the password I had chosen I was given the option to never have the password asked for again. Having chosen that, upon the next turn on, no password was asked for. And my settings were not lost.

Am I the only one who finds the concept of setting a password for a camera deeply worrying, even if it’s not asked for again - perhaps at some point it will be needed again? I hope you wrote it down…

PS I just read the long thread on security, and I think there may be some useful answers there.

No. I think the use of a password to access your camera is ridiculous. What security concerns are there in photos you have taken? I’m not upgrading. Hope there is a way to bypass or eliminate it.

You seem to have misunderstood what the password is protecting, it's not for images. You can pull out the card and the images are not protected in any way. There is a way to eliminate it if all you are worried about it being asked for taking photos, it offers to do just that right after you set the password

Sorry, but why shouldn't it just offers the ability to not set a password, simply ? This implementation is abysmal.

Perhaps, abysmal. But bypassing it at boot doesn't equal not setting it. You still need it when accessing network functions which is the main driver.

Then why not adding the password feature at network functions level, not camera level, and still, even in this condition, why not allow to not set it ?

Implementation choice. What's the problem setting it? If you use network functions, you will anyway need to. If you don't, what's the problem?

Then bad implementation choice, uselessly restrictive and messy.

If password is to be used at network functions level, then add the feature at this point, and still allow the user to have the choice not to set it, and/or also to not use network functions (airplane mode or so).

BTW, I would rather link all network/device connections to an airplane mode setting, that way, in one switch, you'd have the choice to have access or not to all that functions with the choice to protect them with a password or not, letting these choices to user.

The password would only be needed if you want to switch off airplane mode and if you set it.

So I can return the question to you : what's the problem with that ?

I'll turn the question back. One has been implemented already, the other is a proposal. Who is going to implement it? What is most practical at this point?

One takes entering a password. Other some additional dev effort. If the purpose I'd being an armchair critic, I see your point

Airplane mode isn't on by default. Communications settings aren't centered around it, unless we are proposing a significant rewrite. Perhaps they could have asked "do you want to disable all communications functions completely or set a password" at start. Still a different implementation and arguably not a superior one

All this aside, I am not going to try and interpret what compliance with EU RED directive actually entails. Of course manufacturers lawyers will have to do their own interpretation that keeps them in the clear. We will have to see how different manufacturers handle this when 1 Aug arrives (assuming no further extensions)

This is the RED Delegated Act rather than the RED directive which adds the updates that are captured within the latest versions of EN 18031-1, -2, and -3. Sorry it's sounds pedantic but I wished for people to be clear.

There is a test strategy assigned and some labs have the capability to test against it and are accredited but not all that were previously accredited across 18031. Just take time.

I'll wait and see how different manufacturers handle it. If all of them do the exact same thing, then perhaps that is the only way. If there are differences in the end, there is perhaps some options exist on implementation. It's easier when different stakeholders put their best minds to it and we see the results, rather then each one of us trying to interpret the legalese around it.

Indeed. Some heating controllers for homes are going through this (I'm sure lots of products) but how each finds solutions, how camera OEMs do will likely bring more changes and improvements. As it stands it seems okay to us at the moment. It's not as robust as what is required for OTA updates to vehicles, or V2V car Comms but then safety is involved.

I'm personally more interested in the other updates for the R52 and why it cannot have the same panning solution the R1 has just got (and r3 some time back).

--
PicPocket

 

[Zeee]

Turning on the camera after installing I was asked my preferred language and then I was asked to set a numerical password. A numerical keyboard pops up. Confirm the password. Upon turning on the camera again I was asked to enter the password. After entering the password I had chosen I was given the option to never have the password asked for again. Having chosen that, upon the next turn on, no password was asked for. And my settings were not lost.

Am I the only one who finds the concept of setting a password for a camera deeply worrying, even if it’s not asked for again - perhaps at some point it will be needed again? I hope you wrote it down…

Mines easy. 1 2 3 4 5 6

Thats fine but 1 1 1 1 1 1 would be easier. The trouble is, each time you pick the camera up, you have to flip the little flip screen out and punch in the number. Apparently, that's true even if it has been hanging around your neck for a while and has powered down. By that time, that elusive once-in-a-lifetime shot is gone.

It looks like you have the option of telling it to ignore the PW but then what is the purpose of having it in the first place.

They should just ask "do you want to set a PW... Y/N"

I would like to hear from those who actually fired up this new FW how it actually works.

Powering down/up and sleep did not ask for the password as I instructed it.

I’ll verify again when I get home.

PS I just read the long thread on security, and I think there may be some useful answers there.

 

[Ephemeris]

Turning on the camera after installing I was asked my preferred language and then I was asked to set a numerical password. A numerical keyboard pops up. Confirm the password. Upon turning on the camera again I was asked to enter the password. After entering the password I had chosen I was given the option to never have the password asked for again. Having chosen that, upon the next turn on, no password was asked for. And my settings were not lost.

Am I the only one who finds the concept of setting a password for a camera deeply worrying, even if it’s not asked for again - perhaps at some point it will be needed again? I hope you wrote it down…

Mines easy. 1 2 3 4 5 6

Thats fine but 1 1 1 1 1 1 would be easier. The trouble is, each time you pick the camera up, you have to flip the little flip screen out and punch in the number. Apparently, that's true even if it has been hanging around your neck for a while and has powered down. By that time, that elusive once-in-a-lifetime shot is gone.

It looks like you have the option of telling it to ignore the PW but then what is the purpose of having it in the first place.

Because some features such as changing network connections, connecting to networks still require the password. You are not telling it to ignore the password except on boot up where you can opt not to type it in

So, in that condition, if you don't use networking connections, radios, or Ethernet (BT perhaps), you never have to deal with the PW after that first time?

Camera reset and firmware update I think would be the times you would need to interact or perhaps if some actor tries to change your cameras network settings (part of the standard is being able to detect that but I don't know canons mechanism aside a menu that tells us when network settings were last changed).

And... if you DO decide to turn that stuff on and use it, you will have to remember your PIN, and punch it in, I guess.

Yep - 111111 or 123456 screwed if it's raining on your flip screen.

They should just ask "do you want to set a PW... Y/N"

I would like to hear from those who actually fired up this new FW how it actually works.

PS I just read the long thread on security, and I think there may be some useful answers there.

--
Flickr: http://www.flickr.com/photos/drhull
SmugMug: http://davidhull.smugmug.com/

 

[PicPocket]

Nothing too dramatic

Indeed And sorry if I looked only critical.

What's buzzing me is the risk that represents this implementation in bricking your camera in fact. With a solution more dedicated to its target functions, the step of entering a password at startup (or wake up) would be avoided as it is functionally useless.

Right when you set the password, it gives you an option whether to ask for it again. Again, I am fairly critical of Canon UX, but what it really means is whether you want to use the password to be entered when you start the camera every time. I understand most people may not want this, but good to know we can say yes / no here

So this takes away the bricking worry, except if firmware is buggy - which we should not be discussing in this context anyway, software that doesn't work correctly can brick for any failure really

I don't like the idea that my camera won't be accessible if I need only to protect network connections. It's not a simple problem and I wonder finally if European officials may have been a bit "disconnected" on that one, and even Canon just p####d off by the requirements, if so, in the end .

But that's another story I guess.

Well, this is always the story, but to be fair, even if regulators start off base, the industry reps have to educate them and curate things based on that. I'm keen to see implemehtations when all the camera manufacturers have tackled this. Then only we will really know what is set in stone and what was hushed along simply to comply. As you said, you can always have better UX for these things

 

[Pierre Lagarde]

Turning on the camera after installing I was asked my preferred language and then I was asked to set a numerical password. A numerical keyboard pops up. Confirm the password. Upon turning on the camera again I was asked to enter the password. After entering the password I had chosen I was given the option to never have the password asked for again. Having chosen that, upon the next turn on, no password was asked for. And my settings were not lost.

Am I the only one who finds the concept of setting a password for a camera deeply worrying, even if it’s not asked for again - perhaps at some point it will be needed again? I hope you wrote it down…

PS I just read the long thread on security, and I think there may be some useful answers there.

No. I think the use of a password to access your camera is ridiculous. What security concerns are there in photos you have taken? I’m not upgrading. Hope there is a way to bypass or eliminate it.

You seem to have misunderstood what the password is protecting, it's not for images. You can pull out the card and the images are not protected in any way. There is a way to eliminate it if all you are worried about it being asked for taking photos, it offers to do just that right after you set the password

Sorry, but why shouldn't it just offers the ability to not set a password, simply ? This implementation is abysmal.

Perhaps, abysmal. But bypassing it at boot doesn't equal not setting it. You still need it when accessing network functions which is the main driver.

Then why not adding the password feature at network functions level, not camera level, and still, even in this condition, why not allow to not set it ?

Implementation choice. What's the problem setting it? If you use network functions, you will anyway need to. If you don't, what's the problem?

Then bad implementation choice, uselessly restrictive and messy.

If password is to be used at network functions level, then add the feature at this point, and still allow the user to have the choice not to set it, and/or also to not use network functions (airplane mode or so).

BTW, I would rather link all network/device connections to an airplane mode setting, that way, in one switch, you'd have the choice to have access or not to all that functions with the choice to protect them with a password or not, letting these choices to user.

The password would only be needed if you want to switch off airplane mode and if you set it.

So I can return the question to you : what's the problem with that ?

I'll turn the question back. One has been implemented already, the other is a proposal. Who is going to implement it? What is most practical at this point?

One takes entering a password. Other some additional dev effort. If the purpose I'd being an armchair critic, I see your point

Airplane mode isn't on by default. Communications settings aren't centered around it, unless we are proposing a significant rewrite. Perhaps they could have asked "do you want to disable all communications functions completely or set a password" at start. Still a different implementation and arguably not a superior one

All this aside, I am not going to try and interpret what compliance with EU RED directive actually entails. Of course manufacturers lawyers will have to do their own interpretation that keeps them in the clear. We will have to see how different manufacturers handle this when 1 Aug arrives (assuming no further extensions)

This is the RED Delegated Act rather than the RED directive which adds the updates that are captured within the latest versions of EN 18031-1, -2, and -3. Sorry it's sounds pedantic but I wished for people to be clear.

There is a test strategy assigned and some labs have the capability to test against it and are accredited but not all that were previously accredited across 18031. Just take time.

I'll wait and see how different manufacturers handle it. If all of them do the exact same thing, then perhaps that is the only way. If there are differences in the end, there is perhaps some options exist on implementation. It's easier when different stakeholders put their best minds to it and we see the results, rather then each one of us trying to interpret the legalese around it

My thoughts !

Sorry for the naming here but just took a look at my Nikon's cameras, and it seems that at least, they prepared some kind of "network features isolation" in their menu.

I just wish it will be used the "right" way (at least, right in my mind at this point ).

 

[Ephemeris]

Tell me if I got this right -

This is a mandatory law, passed by the EU, to protect networks.

If I update the firmware, it's mandatory that I set a password, even if I never put a camera on the network.

If I choose to not use it, and have to do a factory reset for some reason, I have to pick another password.

So far, so good?

Question - If I skip this update, and a future update comes that I need, will this password BS be included in future updates? I'm thinking yes.

Yes, firmware are cumulative. So unless they remove this functionality in the next ones, you will have this with whatever else

I'm thinking the best solution for me will be to sit where I'm at with version 1.50 on the R7s. For what I do they are working fine right now.

That's a fine choice, unless you care for some bug fixes that were also included. Canon won't care, neither would EU for end users not keeping up to date. It's just about manufacturers having to provide

Canon didn't say anything about bug fixes on the R7.

--

From Canon UK. 1.6 1

3.Fixes an issue in which the camera may become unresponsive after simultaneously pressing a button assigned to [One-Shot AF→Servo AF] and the shutter button.
4. Fixes an issue in which image stabilization may stop working when using an EF lens.

Those who say it cannot be done
should stay out of the way of
those who are doing it.

 

[PicPocket]

Tell me if I got this right -

This is a mandatory law, passed by the EU, to protect networks.

If I update the firmware, it's mandatory that I set a password, even if I never put a camera on the network.

If I choose to not use it, and have to do a factory reset for some reason, I have to pick another password.

So far, so good?

Question - If I skip this update, and a future update comes that I need, will this password BS be included in future updates? I'm thinking yes.

Yes, firmware are cumulative. So unless they remove this functionality in the next ones, you will have this with whatever else

I'm thinking the best solution for me will be to sit where I'm at with version 1.50 on the R7s. For what I do they are working fine right now.

That's a fine choice, unless you care for some bug fixes that were also included. Canon won't care, neither would EU for end users not keeping up to date. It's just about manufacturers having to provide

Canon didn't say anything about bug fixes on the R7.

See #3 and #4

Firmware Version 1.7.1 incorporates the following enhancements and fixes:
1. Improves security features. A password must be set initially.
•Adds the ability to review the history of any changes made to the password, network information, or other settings.
*For more information, please refer to the 'Setting a Password' section in the Advanced User Guide on cam.start.canon.
2. Enables firmware updates to be performed when the camera is connected to the internet and new firmware is made available on Canon servers.
3. Fixes an issue in which the camera may become unresponsive after simultaneously pressing a button assigned to [One-Shot AF→Servo AF] and the shutter button.
4. Fixes an issue in which image stabilization may stop working when using an EF lens.

EOS R7 Firmware Update, Version 1.7.1 [macOS]

Firmware Version 1.7.1 incorporates the following enhancements and fixes:1. Improves security features. A password must be set initially. •Adds the ability to review ...

hk.canon

--

PicPocket

 

[Pierre Lagarde]

Nothing too dramatic

Indeed And sorry if I looked only critical.

What's buzzing me is the risk that represents this implementation in bricking your camera in fact. With a solution more dedicated to its target functions, the step of entering a password at startup (or wake up) would be avoided as it is functionally useless.

Right when you set the password, it gives you an option whether to ask for it again. Again, I am fairly critical of Canon UX, but what it really means is whether you want to use the password to be entered when you start the camera every time. I understand most people may not want this, but good to know we can say yes / no here

So this takes away the bricking worry, except if firmware is buggy - which we should not be discussing in this context anyway, software that doesn't work correctly can brick for any failure really

I don't like the idea that my camera won't be accessible if I need only to protect network connections. It's not a simple problem and I wonder finally if European officials may have been a bit "disconnected" on that one, and even Canon just p####d off by the requirements, if so, in the end .

But that's another story I guess.

Well, this is always the story, but to be fair, even if regulators start off base, the industry reps have to educate them and curate things based on that. I'm keen to see implemehtations when all the camera manufacturers have tackled this. Then only we will really know what is set in stone and what was hushed along simply to comply. As you said, you can always have better UX for these things

Ok, I'm now lost in threads of this very interesting discussion, but as I feel responsible of that, I'd say just "All fair"

 

[chipman02]

Tell me if I got this right -

This is a mandatory law, passed by the EU, to protect networks.

If I update the firmware, it's mandatory that I set a password, even if I never put a camera on the network.

If I choose to not use it, and have to do a factory reset for some reason, I have to pick another password.

So far, so good?

Question - If I skip this update, and a future update comes that I need, will this password BS be included in future updates? I'm thinking yes.

Yes, firmware are cumulative. So unless they remove this functionality in the next ones, you will have this with whatever else

I'm thinking the best solution for me will be to sit where I'm at with version 1.50 on the R7s. For what I do they are working fine right now.

That's a fine choice, unless you care for some bug fixes that were also included. Canon won't care, neither would EU for end users not keeping up to date. It's just about manufacturers having to provide

Canon didn't say anything about bug fixes on the R7.

From Canon UK. 1.6 1

3.Fixes an issue in which the camera may become unresponsive after simultaneously pressing a button assigned to [One-Shot AF→Servo AF] and the shutter button.
4. Fixes an issue in which image stabilization may stop working when using an EF lens.

Those who say it cannot be done
should stay out of the way of
those who are doing it.

Oops, right. Didn't apply to me, so I forgot.

 

[Zeee]

Turning on the camera after installing I was asked my preferred language and then I was asked to set a numerical password. A numerical keyboard pops up. Confirm the password. Upon turning on the camera again I was asked to enter the password. After entering the password I had chosen I was given the option to never have the password asked for again. Having chosen that, upon the next turn on, no password was asked for. And my settings were not lost.

Am I the only one who finds the concept of setting a password for a camera deeply worrying, even if it’s not asked for again - perhaps at some point it will be needed again? I hope you wrote it down…

Mines easy. 1 2 3 4 5 6

Thats fine but 1 1 1 1 1 1 would be easier. The trouble is, each time you pick the camera up, you have to flip the little flip screen out and punch in the number. Apparently, that's true even if it has been hanging around your neck for a while and has powered down. By that time, that elusive once-in-a-lifetime shot is gone.

It looks like you have the option of telling it to ignore the PW but then what is the purpose of having it in the first place.

They should just ask "do you want to set a PW... Y/N"

I would like to hear from those who actually fired up this new FW how it actually works.

Powering down/up and sleep did not ask for the password as I instructed it.

I’ll verify again when I get home.

Just tried it again. Powered off since yesterday. Just powered up and no password request. Same for sleep mode. I even took the battery out and no PW asked for after putting it back.

PS I just read the long thread on security, and I think there may be some useful answers there.

--
When you fail - always "Fail Forward".

 

[Daverich04]

I have an R5 Mark ll. Can someone explain what Networking information is in my camera that I need to be concerned about protecting? As far as I’m aware, the only way into my home network is through wi-fi which means someone would have to be in range to use it. Is there something else that could be a problem? I’m really not getting the reason for this other than the EU said so.

 

[Zeee]

Turning on the camera after installing I was asked my preferred language and then I was asked to set a numerical password. A numerical keyboard pops up. Confirm the password. Upon turning on the camera again I was asked to enter the password. After entering the password I had chosen I was given the option to never have the password asked for again. Having chosen that, upon the next turn on, no password was asked for. And my settings were not lost.

Am I the only one who finds the concept of setting a password for a camera deeply worrying, even if it’s not asked for again - perhaps at some point it will be needed again? I hope you wrote it down…

Mines easy. 1 2 3 4 5 6

Thats fine but 1 1 1 1 1 1 would be easier. The trouble is, each time you pick the camera up, you have to flip the little flip screen out and punch in the number. Apparently, that's true even if it has been hanging around your neck for a while and has powered down. By that time, that elusive once-in-a-lifetime shot is gone.

:-D Well so far it has not been asking me for a PS. I disabled it as per instructions.

It looks like you have the option of telling it to ignore the PW but then what is the purpose of having it in the first place.

They should just ask "do you want to set a PW... Y/N"

I would like to hear from those who actually fired up this new FW how it actually works.

Fired it up and it works.

I Installed the New Firmware with Password (R8)

Turning on the camera after installing I was asked my preferred language and then I was asked to set a numerical password. A numerical keyboard pops up. Confirm the password. Upon turning on the camera again I was asked to enter the password. After entering the password I had chosen I was given...

www.dpreview.com

PS I just read the long thread on security, and I think there may be some useful answers there.

 

[tbsteph]

Not sure I understand why you felt motivated to provide a Youtube video link that has absolutely nothing to do with the original post.

 

[Zeee]

I also did my R6II. Tried to stop the password from always asking but had to try a few times. You have to instruct it but also check the box beside it.
Now I see that Canon has advised to not install for the R1 and R5II. Is this across the board for all the bodies?

Just the r1 and r52 due to an issue recording and playing back video on >2tb cards.

We have the latest installed on all bodies now.

Thanks. Sorry for the late reply.

When you fail - always "Fail Forward".

 

[Zeee]

Turning on the camera after installing I was asked my preferred language and then I was asked to set a numerical password. A numerical keyboard pops up. Confirm the password. Upon turning on the camera again I was asked to enter the password. After entering the password I had chosen I was given the option to never have the password asked for again. Having chosen that, upon the next turn on, no password was asked for. And my settings were not lost.

Am I the only one who finds the concept of setting a password for a camera deeply worrying, even if it’s not asked for again - perhaps at some point it will be needed again? I hope you wrote it down…

PS I just read the long thread on security, and I think there may be some useful answers there.

No. I think the use of a password to access your camera is ridiculous. What security concerns are there in photos you have taken? I’m not upgrading. Hope there is a way to bypass or eliminate it.

Yes there is a way to bypass it. Instruct to not ask you for the PW. I can't see Canon dropping this and you can't avoid FW updates forever.

 

[Ephemeris]

I also did my R6II. Tried to stop the password from always asking but had to try a few times. You have to instruct it but also check the box beside it.
Now I see that Canon has advised to not install for the R1 and R5II. Is this across the board for all the bodies?

Just the r1 and r52 due to an issue recording and playing back video on >2tb cards.

We have the latest installed on all bodies now.

Thanks. Sorry for the late reply.

When you fail - always "Fail Forward".

--
When you fail - always "Fail Forward".