Collaborate Disseminate
First of all I am not very familiar with the world of encryption so please be nice.
I have got a data that should store in an xml using NetDataContractSerializer. This xml file gets the size of from 5MB to 10MB. So I am zi… Continue reading Best way to encrypt user data stored in xml?
With more and more embedded systems being connected, sending state information from one machine to another has become more common. However, sending large packets of data around on the network can be bad both for bandwidth consumption and for power usage. Sure, if you are talking between two PCs connected with a gigabit LAN and powered from the wall, just shoot that 100 Kbyte packet across the network 10 times a second. But if you want to be more efficient, you may find this trick useful.
As a thought experiment, I’m going to posit a system that has a database …read more
Have you ever noticed how “one size fits all” often means “one size poorly fits all”? This became especially clear to me when I started using a compression sleeve on my arm. Like any hacker, this seemed like something I could fix, so I gave it a shot. Boy, did I learn a lot in the process.
A little over a year ago, I started dropping things. If I was holding something in my left hand, chances were good that it would suddenly be on the ground. This phenomenon was soon accompanied by pain and numbness, particularly after banging on …read more
Continue reading Stretching My Skills: How (and Why) I Made My Own Compression Sleeves
I have a single page application that is hosted at example.com that relies on api.example.com. The SPA sends user credentials (JWT token) in authorization header for every request.
Let’s suppose that the APIs have an endpoi… Continue reading BREACH attack against SPA
It was mentioned that JPEG should not be used between image creation and redaction of sensitive contents, because compression artifacts around the redacted area may leak information. Given how this lossy format works, this makes sense. Is … Continue reading JPEG artifacts leaking information about redacted contents
On the face of it, keeping fluids contained seems like a simple job. Your fridge alone probably has a dozen or more trivial examples of liquids being successfully kept where they belong, whether it’s the plastic lid on last night’s leftovers or the top on the jug of milk. But deeper down in the bowels of the fridge, like inside the compressor or where the water line for the icemaker is attached, are more complex and interesting mechanisms for keeping fluids contained. That’s the job of seals, the next topic in our series on mechanisms.
One of …read more
Currently, we know few compression attacks on the SSL/TLS protocol (such as Crime or Breach). I wonder for few days if these attacks are practicable on a mail server (smtp). Is CRIME attack practicable on a mail server ?
… Continue reading SSL/TLS compression attacks on mail servers (smtp)
BIG-IP provides Local Traffic Policies that simplify the way in which you can manage traffic associated with a virtual server. You can associate a BIG-IP local traffic policy to support selective compression for types of content that can benefit from compression, like HTML, XML, and CSS style sheets. These file types can realize performance improvements, […]
The post Selective Compression on BIG-IP appeared first on Security Boulevard.
In a previous posting on Which is a safe way to transfer a copy of a sensitive document?, I have received suggestions to compress and encrypt an attachment file using the options of utilities such as zip, rar, 7zip and suchlike.
Although the specifics are not important here, the manual page of zip alerted me that there is much more to it than choosing a compression utility and send. Very seriously, the page zip is cautious to the point of hinting that you are not getting any serious encryption (emphasis added)
-P password
–password passwordUse password to encrypt zipfile entries (if any). THIS IS INSECURE! Many multi-user
operating systems provide ways for any user to see the current command line of any
other user; even on stand-alone systems there is always the threat of over-the-shoulder
peeking. Storing the plaintext password as part of a command line in an automated
script is even worse. Whenever possible, use the non-echoing, interactive prompt to
enter passwords. (And where security is truly important, use strong encryption such as
Pretty Good Privacy instead of the relatively weak standard encryption provided by zip‐
file utilities.)
Forewarned is forearmed. I have browsed/scanned several postings in this community such as
It is a lot of (interesting, well-presented) information, and the problem has many dimensions: compression utility, encryption algorithms, archive handler, perhaps many more.
The drawback there is that I am a lay, moderately computer-savvy user, who faces the problem of choosing a compression utility that should have the following features:
Apparently, I need some guideline to navigate this problem and choose what to do for an informed guess.
Is there any ‘self-aid’ wiki resource that you would recommend to find what one is heading for when using this or that utility? Any other suggestions ideas allaying these sorts of headache?
Continue reading How can I select a compression utility that is popular and secure enough
In a previous posting on Which is a safe way to transfer a copy of a sensitive document?, I have received suggestions to compress and encrypt an attachment file using the options of utilities such as zip, rar, 7zip and suchlike.
Although the specifics are not important here, the manual page of zip alerted me that there is much more to it than choosing a compression utility and send. Very seriously, the page zip is cautious to the point of hinting that you are not getting any serious encryption (emphasis added)
-P password
–password passwordUse password to encrypt zipfile entries (if any). THIS IS INSECURE! Many multi-user
operating systems provide ways for any user to see the current command line of any
other user; even on stand-alone systems there is always the threat of over-the-shoulder
peeking. Storing the plaintext password as part of a command line in an automated
script is even worse. Whenever possible, use the non-echoing, interactive prompt to
enter passwords. (And where security is truly important, use strong encryption such as
Pretty Good Privacy instead of the relatively weak standard encryption provided by zip‐
file utilities.)
Forewarned is forearmed. I have browsed/scanned several postings in this community such as
It is a lot of (interesting, well-presented) information, and the problem has many dimensions: compression utility, encryption algorithms, archive handler, perhaps many more.
The drawback there is that I am a lay, moderately computer-savvy user, who faces the problem of choosing a compression utility that should have the following features:
Apparently, I need some guideline to navigate this problem and choose what to do for an informed guess.
Is there any ‘self-aid’ wiki resource that you would recommend to find what one is heading for when using this or that utility? Any other suggestions ideas allaying these sorts of headache?
Continue reading How can I select a compression utility that is popular and secure enough