(for that is not is not his name)
... So his name *is* Ben then?!
44 posts • joined 8 Mar 2019
You kind of can...
Have the same basic password for each site (complexpassword@$% for example) and then add on the website / company to it for each site so for example Registercomplexpassword@$% etc etc).
Then have a dedicated one for your email / bank.
Should protect you from one site being hacked (the same password with your email address won't work on any other site) but is still easy to remember.
Obviously if enough sites get cracked and someone compares all of the passwords associated with a given email then you may be in trouble....
Simply change your login landing page (if it's a cloud portal then it is the company you are siging in to that controls that page) into something that shows images of the latest Russian War crime. Then make sure that anyone signing in from Russia has to re authenticate at least weekly.
I'm pretty sure the company will be banned pdq from the customer end and you have done nothing that you could be taken to court for.
...and that is of itself one of the problems. The old systems (and i'm not just talking about government here, a lot of businesses have them too) just keep going and going so it's very hard to convince upper management to spend the big bucks to replace them.
In the mean time the cludges and fixes needed to get the old systems talking to newer systems that are also being brought online (and newer user desktops which fail and need replacement much more regularly) get more and more complex and likely to fail. That's where the real weakness usually is.
Probably so that they could prove to the squaddie guarding the door to said plane / gate to the airfield where the plane was taking off from that they were one of the people that we thought would be murdered and not some random chancing their luck.
But yes I know what you mean.
If you're using Exchange 365 then at some point older versions of Windows are going to be cut off.
There are ways around this of course (OWA etc..) but many people like Outlook (well need, nobody likes Outlook).
I suppose there are also security considerations as well if you have a fleet of PCs to look after..
I think that (and I may well be wrong on this) they are not looking at a photo and making a decision on whether that is child sex abuse or not. I think what they are doing is generating a signature of the photo in a standardised way and then comparing that signature against signatures already made (in the same industry standard way) of known sex abuse images. If the signatures match then that should mean it is the same photo. I don;t *think* this is designd to catch new images just flag up the presence of old already known and flagged ones.
Agree geocaching works. unfortunately (near us at any rate) there are only about 4 within the walking distance of a 7 year old. Once we've done those then you're into travelling further and further afield.
Ideally this would be something that you can take on the same walk over and over but give different results to keep young'ens entertained...
"Admins: give your users plaintext email.
Or filter out all links that don't point at local intranet, eg. your sharepoint etc or other whitelisted stuff."
Is a great suggestion and would solve the problem. However the first time a (legitimate) customer sends a link to an urgent order they want to place that is not on a whitelist (their Sharepoint or Google drive for example) and you as the one person who can send it through happens to be off for the day then the stuff really will hit the fan..
Security and useability are always going to be at opposing ends of the see-saw. The trick is getting the blooming thing to balance..
That is odd. We don't use any security software like that (just standard AV - ESET) we do use a cisco firepower but it still didn't work when I brought one of the affected laptops home so bypassed that completely...
It's definitely lit a fire under our windows 10 roll out, part of me wonders if that was the plan!
I've never been employed as first line support but apparently having a technical bent and being in proximity to anything with a power supply immediately makes it my problem...
Indeed, my favorite was being asked to fix the coffee machine "because it has a log in code on it..."
You need to delete the DWORD entry for com.squirrel.Teams.Teams from Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
That should stop it.
There is also a PreventTeams Install that can go in HKLM\software\Policies\MIcrosoft\Office\16.0\common\officeupdate that should stop it if you've not had an affected Office Update applied yet...
Biting the hand that feeds IT © 1998–2022