This forum is provided to promote discussion amongst students enrolled in
CITS3007 Secure Coding.
If posting a question, it's suggested you check first whether your question
is answered in the unit Frequently Asked Questions (FAQ) list, and use the search box
(on the right) to see if an answer to your question has already been posted.
Please consider offering answers and suggestions to help other students!
And if you fix a problem by following a suggestion here,
it would be great if other interested students could see a short
"Great, fixed it!" followup message.
Hi,
Just to clarify, my suggestion was that you come up with (ideally multiple) ways the apparent contradiction might be resolved the idea here is for students to actively engage with the project specification, and think about how project requirem...
Hi,
For students in today's 9am lab unfortunately the usual lab facilitator was not available, and I didn't realize this until it was too late to arrange for someone else to facilitate my apologies.
I've scheduled a replacement session for 2-3 30p...
Hi all,
Just FYI, exam venues have been confirmed. The main venue is the MATH 123 math123 lab, and students with alternative exam arrangements will be in one of the CSSE labs. I will post full details on the LMS.
math123 https link.mazemap.com ...
Just "Arran" is fine.
I'm going to ask you to reflect a bit more on your question. Can you think of any ways of resolving this possible contradiction? What are they? Suggest some ideas.
Cheers
Arran
Hello Sir,
If using assert() to check preconditions, doesn't this go against the project specification where it says never print to standard out or standard error? As I think assert() does print to stderr.
Thanks
Gotcha - the crypto.h version is the correct one (for the reasons I gave - the output parameter comes last).
So that's how you need to code your implementation - does that help?
Cheers
Arran
Hi Arran,
Apologies, I copied the wrong function in my initial question,
In the pdf the caesar decrypt declaration has plain text before cipher text
void caesar decrypt(char range low, char range high, int key, const char plain text, char cipher te...
Hi all,
I'll likely post the revised project spec towards the end of this week. After that point, the spec can be considered "frozen" (as per the guidelines here spec ).
spec https cits3007.github.io faq how-are-problems-with-the-project-specif...
Hi,
Sure, that sounds mostly right. The code really should be pretty easy, so there should be plenty of time to focus on making sure your code is correct, covers edge cases, and is clear and understandable. Therefore markers will expect a fairly hig...
Hi,
I'll amend the spec to clarify this the key must fall in the "encryptable range" specified by range low and range high . For each letter of the plaintext which is to be encrypted, we work out an appropriate caesar cipher by subtracting low ra...
Hi Taylah,
No, that's not a typo. Typically in related functions, we put input and output parameters in a consistent order. In the encryption function, cipher text is an output. But in the decryption function, plain text is the input, and ciphe...
Hi,
I think you may have a fairly major misunderstanding of the project specification and the header file you're provided with. My first suggestion would be to first make sure you've read through the whole of the specification and the provided heade...
Hi all, Just checking if I understand the project right,
so we need to implement encryption and decryption functions for both the Caesar and Vigenere ciphers, following the provided specifications in the crypto.h header file. Additionally, we'll crea...
Hey I think I've found another typo.
In the pdf the caesar decrypt declaration has plain text before cipher text
void caesar decrypt(char range low, char range high, int key, const char plain text, char cipher text);
But crypto.h has them the other...
Hey I think I've found another typo.
In the pdf the caesar decrypt declaration has plain text before cipher text
void caesar encrypt(char range low, char range high, int key, const char plain text, char cipher text);
But crypto.h has them the other...
Hi,
Can the key for the Vigenere encrypt and decrypt functions have spaces or punctuation characters in it? Or does it have to be a stream of alphabets? The project spec doesn't mention anything about this..
Hi,
I don't understand what the function call would look like if we were including punctuation within the range.
Would you be able to provide an example of this?
Thanks.