I am fairly new to apache and was a SQL Server database admin in a former life so please forgive my ignorance. I am trying to set up an apache(HP-UX flavor) server to conform with the DOD STIGs required for this project. I have the following items configured within my httpd.conf file:
LoadModule...
I am fairly new to apache and was a SQL Server database admin in a former life so please forgive my ignorance. I am trying to set up an apache(HP-UX flavor) server to conform with the DOD STIGs required for this project. I have the following items configured within my httpd.conf file:
LoadModule...
I am fairly new to apache and was a SQL Server database admin in a former life so please forgive my ignorance. I am trying to set up an apache(HP-UX flavor) server to conform with the DOD STIGs required for this project. I have the following items configured within my httpd.conf file:
LoadModu...
@diagprov There is no central resource for understanding hash design because we, in truth, have no idea how such things should be done. We do not even know if secure hash function can actually exist at all.
Fun fact: Homebrewing has fewer questions than the total number of questions tagged [homebrew] across SE, which are mostly about the OSX package manager
What you can have is, in each paper describing a hash function proposal, some rationale about why that function is made that way, but this does not mean that any other method is bad.
@RoryAlsop I would actually have a lot to answer there, and would probably enjoy some of the answers - but as you say, the community would annoy me too much
@ThomasPornin would you generally recommend this also for regular devs, who just want to use the crypto correctly, without knowing how to implement the algorithms?
The real trick is to understand that there is a huge difference between implementing a crypto algorithm to learn it, and implementing a crypto algorithm to use it.
I've also learned this the hard way - even without getting into the cipher maths, I used to explain the cipher modes. This led to many bad ideas and poor decisions (only a few on my part).
To make a metaphor, you should not make illegal the selling of knives to people who are not professional cooks, even though you know that there are some people who will use them poorly enough that they succeed at stabbing themselves, their neighbour, and all small furry animals within a 20km radius.
I'm doing a theoretical exercise for a class. We are given this snippit of UNIX C code which is vulnerable to race conditions between the access() call and the open() call.
/* vulp.c */
#include <stdio.h>
#include<unistd.h>
#define DELAY 10000
int main()
{
char * fn = "/tmp/XYZ";
char...
@AviD Actually I do work with regular programmers. My learning advice, by definition, is for programmers who want to learn, i.e. not regular programmers. Regular programmers will just keep on being regular and I cannot do anything about it (that is, anything which is not violent and illegal).