![[756] Sentry Safe Cut in Half FAST!](https://i.ytimg.com/vi/2guvwQvElA8/hqdefault.jpg)
[756] Sentry Safe Cut in Half FAST!
About this video
LockPickingLawyer shows a Sentry fire safe being cut in half with a saw in a few minutes. It is a short demonstration that these safes offer little protection against a determined thief.
Why it appears in the archive
Used to illustrate that fire safes protect against fire and not theft, and that brute force often defeats low-security containers.
AI-generated summary and labels from the source dataset; verify important details against the video. Source & credits.
From the Hacker News discussion
For surprise of tool used the saw vs safe are the best: [VIDEO] The main thing locks do is make it noisy to get in.
Read original comment ↗They are supposed to and apparently work well, they do nothing to stop a thief so the fire safety is all they are good for. [VIDEO]
Read original comment ↗Finding vulnerabilities in low security locks is just an academic exercise. If you need high security, you are buying a product very different than a master lock, and you need to consider the integrity of the entire system it is connected to. Low security locks work mainly by deterrent, and even if they were without vulnerability, the container you’re attaching it to probably is vulnerable. Brute force attacks are the much more common scenario against low security locks, and there’s not much of a low cost solution to that; it requires expensive materials: [VIDEO] If you put an unpickable lock on sheet metal box, you’re spending more money, but not actually improving security. The reason that master locks are popular is because they are fairly reliable, easy to get keys for, have useful feature sets, etc. These are the features that commercial users often care about the most. They don’t want to spend more money to get an unpickable lock that interrupts their daily business when it inevitably gets dirty, keys are lost, etc. especially if it provides no additional resistance against an angle grinder.
Read original comment ↗