Review

When a DataOutputStream instance wraps an underlying OutputStream instance,
it is recommended to flush or close the DataOutputStream before operating on the OutputStream.
Although in these cases this is not strictly necessary because the
DataOutputStream's close and flush method has no effects. However, it is a good practice to call
flush/close explicitly as mentioned for example here.
This pull request adds a call to flush.

• missing/call

net/sf/ntru/encrypt/EncryptionParameters.java

writeTo(OutputStream)

class EncryptionParameters {
    /**
     * Writes the parameter set to an output stream
     * @param os an output stream
     * @throws IOException
     */
    public void writeTo(OutputStream os) throws IOException {
        DataOutputStream dos = new DataOutputStream(os);
        dos.writeInt(N);
        dos.writeInt(q);
        dos.writeInt(df);
        dos.writeInt(df1);
        dos.writeInt(df2);
        dos.writeInt(df3);
        dos.writeInt(db);
        dos.writeInt(dm0);
        dos.writeInt(maxM1);
        dos.writeInt(c);
        dos.writeInt(minCallsR);
        dos.writeInt(minCallsMask);
        dos.writeBoolean(hashSeed);
        dos.write(oid);
        dos.writeBoolean(sparse);
        dos.writeBoolean(fastFp);
        dos.write(polyType.ordinal());
        dos.writeUTF(hashAlg);
    }

}

class FlushStreamBeforeGetBytes {
  void pattern(OutputStream out) throws IOException {
    DataOutputStream dout = new DataOutputStream(out);
    dout.writeInt(0);
    dout.flush();
  }
}