As much as I love google hate, the bigger problem is people thinking work devices are private. They are not. Your messages/thoughts/ideas belong to the organization.
Yup! Just cuz your employer isn’t physically there looking over your shoulder while using the device doesn’t mean they are oblivious to what you are doing on it.
You would be mistaken if you think that every work phone is paid for by the employer. A lot of companies have a BYOD policy and still require loading their restrictive bullshit onto it. I have worked at two places like this and I refused to let them do it, but most went along with it. The funniest part if that they still wanted me on the on call rotation, but wouldn't pay for a decent device so they dug out an ancient Nextel phone for me to use. I have no idea how it still worked.
Good! That’s exactly how you should react to that request. BYOD is only okay if the company is subsidizing your monthly bill, even then it’s a grey area to me.
In fairness, that is a different situation than this.
This is google basically providing a mechanism for employers and parents to pull text messages on devices on their plans. That wouldn't impact BYOD as that is still not on their plan.
But all the management software and spyware already have those capabilities. Which... is the other aspect of this karma-bate post.
Every work phone, BYOD or not, has had the corporate profile stuff installed which already let them see most of everything. I just assumed this was more of the same. Shame on me for not reading the article.
I'm glad to hear that the BYOD trend didn't take off in every country. Many of the companies would act like they were doing you a favor so you didn't have the "hassle" of carrying two phones around. Oh that is a hassle, but this was just them shoveling their costs onto the worker.
My old boss logged onto her private investment bank account on the work computers/network and bought and sold stock, for example. God knows what else she did. She got fired for using the company card for private purchases. Good fucking riddance. :D
Yeah this is the bigger issue here really. Fuck Google and their invasive bullshit, absolutely, but work devices should never be used for personal/private use, and vice versa. Keep that shit completely separate as much as possible.
GrapheneOS. Use a work profile. Segregate your work from your personal information. As far as the employer is concerned, they have full control over your device. They can even send a wipe command to it and it would only affect the work partition, leaving your personal data alone.
My favorite tool for managing this is an app called Shelter. Graphene has robust profiling support, but I don't want to have to swap in and out of something to see info. Shelter allows you to clone apps from your main profile to your work profile. You don't even have to set up Google Play Services with an account if you don't want.
Yeah... having to reprovision a phone because it just got reformatted is going to raise a red flag. And if you are installing a rogue OS on your work phone to prevent your employer from seeing what you are doing... I actually side with them when they fire your ass.
Your nonsense makes sense if it is a personal device that you are using for work purposes. Which... I strongly oppose for a range of reasons. If your work wants you "on call" then they can provide a device. Otherwise you can never be off call.
Ah. So graphene DOES have a system where it takes your entire existing OS, shrinks all the partitions on disk, installs itself around that, AND prevents the monitoring software from reporting that your 512 GB device is now actually a 128 GB one?
Well color me surprised.
Or, you know, more likely you end up wiping the existing OS by effectively factory resetting it. And then you ping the management software server saying "I need to reinstall your spyware" which triggers a flag that IT may or may not care about. Similarly, said spyware now wonders why your phone's storage shrunk so massively and raises another flag.
Considering I have to deal with these kinds of security concerns on the regular as part of my professional life... kind of.
But you are just switching to ad hominem because your non sequitor "gimme updoots" response to a thread title is nonsense and you can't admit that. So... I strongly encourage you to wipe your work phone and install graphene with an isolated partition for google/work android and see what happens.
Inform yourself before making these statements. It's a more secure, hardened version of the official OS. It is not rooted nor is it displayed to the employer as anything other than Android.
This has nothing to do with the way the OS works, and everything to do with corporate policy. This would be against the IT policy at most companies, and circumventing their ability to remotely manage the device could easily get you fired.
I'm just being realistic. Some companies will fire you over this, at it will be "for cause" so you won't even be eligible for unemployment. If you can afford to lose your job, you can afford to buy your own phone for personal use. But if you want to take that risk, I won't stop you.
Would be fine if the person is having to BYOD as the phone is already theirs (which is how I took it at least). Obviously flashing a custom ROM of any sort without approval on a device that you don't own, and would have to give back to the company is a bad idea. The same would apply to installing a different OS on a work PC (which tend to have the BIOS locked to prevent changing things or being able to simply boot an install USB). But I think managed phones with the level of being able to wipe the device remotely would also already be blocking access to developer options. Along with other stuff needed to unlock the needed stuff for flashing other ROMs (though I haven't flashed a ROM in a while and never had a work phone so I might be wrong).
But if the company tries to take "ownership" of your personal device that you pay/paid for without providing a company owned device. Then it would be best to try and find a different employer, and/or use an old phone you don't use or get a low-end/cheap phone while working for them. But only go with that option if they provide a SIM/eSIM
... Show more...
Would be fine if the person is having to BYOD as the phone is already theirs (which is how I took it at least). Obviously flashing a custom ROM of any sort without approval on a device that you don't own, and would have to give back to the company is a bad idea. The same would apply to installing a different OS on a work PC (which tend to have the BIOS locked to prevent changing things or being able to simply boot an install USB). But I think managed phones with the level of being able to wipe the device remotely would also already be blocking access to developer options. Along with other stuff needed to unlock the needed stuff for flashing other ROMs (though I haven't flashed a ROM in a while and never had a work phone so I might be wrong).
But if the company tries to take "ownership" of your personal device that you pay/paid for without providing a company owned device. Then it would be best to try and find a different employer, and/or use an old phone you don't use or get a low-end/cheap phone while working for them. But only go with that option if they provide a SIM/eSIM for service that they are paying for.
A work phone is a perk because it means you don't have to install Teams, Slack, and a bunch of proprietary nonsense you've never heard of onto your personal phone.
Pearl
in reply to ☆ Yσɠƚԋσʂ ☆ • • •nothx [he/him]
in reply to Pearl • • •sidebro
in reply to nothx [he/him] • • •zod000
in reply to sidebro • • •nothx [he/him]
in reply to zod000 • • •zod000
in reply to nothx [he/him] • • •NuXCOM_90Percent
in reply to zod000 • • •In fairness, that is a different situation than this.
This is google basically providing a mechanism for employers and parents to pull text messages on devices on their plans. That wouldn't impact BYOD as that is still not on their plan.
But all the management software and spyware already have those capabilities. Which... is the other aspect of this karma-bate post.
zod000
in reply to NuXCOM_90Percent • • •sidebro
in reply to zod000 • • •zod000
in reply to sidebro • • •nothx [he/him]
in reply to sidebro • • •sidebro
in reply to nothx [he/him] • • •nothx [he/him]
in reply to sidebro • • •nfreak
in reply to Pearl • • •ORbituary
in reply to ☆ Yσɠƚԋσʂ ☆ • • •GrapheneOS. Use a work profile. Segregate your work from your personal information. As far as the employer is concerned, they have full control over your device. They can even send a wipe command to it and it would only affect the work partition, leaving your personal data alone.
My favorite tool for managing this is an app called Shelter. Graphene has robust profiling support, but I don't want to have to swap in and out of something to see info. Shelter allows you to clone apps from your main profile to your work profile. You don't even have to set up Google Play Services with an account if you don't want.
NuXCOM_90Percent
in reply to ORbituary • • •Yeah... having to reprovision a phone because it just got reformatted is going to raise a red flag. And if you are installing a rogue OS on your work phone to prevent your employer from seeing what you are doing... I actually side with them when they fire your ass.
Your nonsense makes sense if it is a personal device that you are using for work purposes. Which... I strongly oppose for a range of reasons. If your work wants you "on call" then they can provide a device. Otherwise you can never be off call.
ORbituary
in reply to NuXCOM_90Percent • • •NuXCOM_90Percent
in reply to ORbituary • • •Ah. So graphene DOES have a system where it takes your entire existing OS, shrinks all the partitions on disk, installs itself around that, AND prevents the monitoring software from reporting that your 512 GB device is now actually a 128 GB one?
Well color me surprised.
Or, you know, more likely you end up wiping the existing OS by effectively factory resetting it. And then you ping the management software server saying "I need to reinstall your spyware" which triggers a flag that IT may or may not care about. Similarly, said spyware now wonders why your phone's storage shrunk so massively and raises another flag.
ORbituary
in reply to NuXCOM_90Percent • • •NuXCOM_90Percent
in reply to ORbituary • • •Considering I have to deal with these kinds of security concerns on the regular as part of my professional life... kind of.
But you are just switching to ad hominem because your non sequitor "gimme updoots" response to a thread title is nonsense and you can't admit that. So... I strongly encourage you to wipe your work phone and install graphene with an isolated partition for google/work android and see what happens.
Ajen
in reply to ORbituary • • •ORbituary
in reply to Ajen • • •Again, someone who knows nothing about the OS.
Inform yourself before making these statements. It's a more secure, hardened version of the official OS. It is not rooted nor is it displayed to the employer as anything other than Android.
Stop making uniformed statements.
Ajen
in reply to ORbituary • • •This has nothing to do with the way the OS works, and everything to do with corporate policy. This would be against the IT policy at most companies, and circumventing their ability to remotely manage the device could easily get you fired.
ORbituary
in reply to Ajen • • •Oh, no. Anyway...
Seriously, people shilling for business policy over privacy in this commentary is wild.
Ajen
in reply to ORbituary • • •d-RLY?
in reply to Ajen • • •Would be fine if the person is having to BYOD as the phone is already theirs (which is how I took it at least). Obviously flashing a custom ROM of any sort without approval on a device that you don't own, and would have to give back to the company is a bad idea. The same would apply to installing a different OS on a work PC (which tend to have the BIOS locked to prevent changing things or being able to simply boot an install USB). But I think managed phones with the level of being able to wipe the device remotely would also already be blocking access to developer options. Along with other stuff needed to unlock the needed stuff for flashing other ROMs (though I haven't flashed a ROM in a while and never had a work phone so I might be wrong).
But if the company tries to take "ownership" of your personal device that you pay/paid for without providing a company owned device. Then it would be best to try and find a different employer, and/or use an old phone you don't use or get a low-end/cheap phone while working for them. But only go with that option if they provide a SIM/eSIM
... Show more...Would be fine if the person is having to BYOD as the phone is already theirs (which is how I took it at least). Obviously flashing a custom ROM of any sort without approval on a device that you don't own, and would have to give back to the company is a bad idea. The same would apply to installing a different OS on a work PC (which tend to have the BIOS locked to prevent changing things or being able to simply boot an install USB). But I think managed phones with the level of being able to wipe the device remotely would also already be blocking access to developer options. Along with other stuff needed to unlock the needed stuff for flashing other ROMs (though I haven't flashed a ROM in a while and never had a work phone so I might be wrong).
But if the company tries to take "ownership" of your personal device that you pay/paid for without providing a company owned device. Then it would be best to try and find a different employer, and/or use an old phone you don't use or get a low-end/cheap phone while working for them. But only go with that option if they provide a SIM/eSIM for service that they are paying for.
scoutfdt
in reply to ☆ Yσɠƚԋσʂ ☆ • • •Since when is a work phone a perk. They have horrible battery performance, only function between 9 and 5 and call quality is absolute fuckin shit.
cenzorrll
in reply to scoutfdt • • •kkj
in reply to scoutfdt • • •monovergent
in reply to scoutfdt • • •sunshine
in reply to ☆ Yσɠƚԋσʂ ☆ • • •Saapas
in reply to ☆ Yσɠƚԋσʂ ☆ • • •>Microsoft triggered a viral furor when it revealed a Teams update to tell your company when you’re not at work.
This is the funniest thing, people mad that Teams tracks if you're actually doing work lol
lllIII000IIIlll
in reply to ☆ Yσɠƚԋσʂ ☆ • • •