Stack Exchange Network

Stack Exchange network consists of 174 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange

Questions tagged [present]

PRESENT is a lightweight block cipher with a 64-bit block size and an 80 or 128 bit key.

1
vote
3answers
187 views

What is the time complexity of the basic components of a symmetric cipher?

I have a very basic knowledge on time complexity and even less on programming, so please bear with me. I am interested to know the time complexity in big-O notation of some of the basic operations in ...
3
votes
1answer
94 views

Are there recommended modes of operation for lightweight ciphers?

There are many recommended modes of operation for block ciphers as described by NIST here, e.g. for DES and AES. However, I am struggling to find any for lightweight ciphers. I am particularly ...
4
votes
3answers
401 views

In what cases might PRESENT be implemented as encryption-only?

In the paper, under section 4.1 Goals and environment of use we read: In applications that demand the most efficient use of space, the block cipher will often only be implemented as encryption-only. ...
4
votes
1answer
89 views

What is the reasoning behind the PRESENT key schedule?

It seems there are few books on PRESENT and even fewer that give any reasoning behind the mechanics of the key schedule. I understand how it works to the extent that I made a simple Excel program of ...
1
vote
0answers
17 views

Can we protect PRESENT from the Statistical Saturation Attack if we change the permutation layer to a random permutation layer?

This is continuation-question based on: If PRESENT had different permutations s would that protect it against Statistical Saturation Attack? Can we protect PRESENT from Statistical Saturation Attacks ...
4
votes
1answer
404 views

If PRESENT had different permutations s would that protect it against Statistical Saturation Attack?

The block cipher PRESENT is vulnerable to the Statistical Saturation Attack for up to 15 rounds (PDF) and a simple example is here. So my questions are, if some (or all) of the permutations were ...
1
vote
2answers
167 views

What affect does the permutation layer have on the avalanche effect?

If the permutation is not well thought out, how will this effect the cipher's avalanche effect. For example, if the permutation in PRESENT was in some way different (just made up without any thought) ...
0
votes
1answer
124 views

What is the role of the round counter in the key schedule of PRESENT?

Currently I am working on PRESENT block cipher implementation (Hardware) and I am unable to understand the role of round counter in key scheduling part of cipher. Can some share some insight on round ...
2
votes
1answer
69 views

What does it mean when 1 bit goes into an s-box but two (or more) come out?

I am trying to understand how bits are spread in the PRESENT cipher. The bits that enter the permutation of PRESENT return to their original position after only three rounds. But I am told that in ...
1
vote
1answer
113 views

How does the PRESENT cipher's permutation affect all rounds when it repeats after every three rounds?

I heard that the permutation in PRESENT affects all bits after only a few rounds. However, when I looked at it the bits return to their original position after only three rounds. For example, in round-...
2
votes
1answer
116 views

Why is PRESENT 31 rounds?

I tried a number of different inputs and keys and checked their respective hamming distances after each round. It seems PRESENT has an ideal or near ideal hamming distance (31 to 33) after only a few ...
1
vote
0answers
128 views

How to apply linear cryptanalysis to PRESENT?

Can someone help me implement linear cryptanalysis of the PRESENT block cipher? How should I start with 64 bits of plaintext and 80 bits of key?
2
votes
2answers
1k views

Test vectors for PRESENT algorithm?

I'm looking for Test Vectors to test my implementation of PRESENT. I would like to test a different input from the usual where the key and the plaintext are either 000..000 or FFF...FFF.