jema...@gnu.org writes:
> Hi David.
>
>I have unassign the task FS#102 since I am busy and I think someone
>could to take the task and finish it soon. I hope to speed up the
>development so.
>
> Thanks for letting us know.
>
>Previously this is required some changes to the filesyst
Hello,
I have unassign the task FS#102 since I am busy and I think someone
could to take the task and finish it soon. I hope to speed up the
development so.
Previously this is required some changes to the filesystem module API.
I will take more tasks soon. I apologize for any inconveniences.
G
99%: Checks: 611, Failures: 2, Errors: 0
base/fsys/pdf-fsys-file-open.c:127:F:pdf_fsys_file_open:
pdf_fsys_file_open_003:0: Failure 'pdf_fsys_file_open(NULL, path,
PDF_FSYS_OPEN_MODE_WRITE, &file) != PDF_EBADPERMS' occured
base/fsys/pdf-fsys-file-close.c:60:F:pdf_fsys_file_close:pdf_fsys_file_cl
: e502aa8ad611e47770d8c7441a2509b9d8a38d40
# timestamp: 2009-09-15 05:34:21 +0200
# base_revision_id: jema...@gnu.org-20090908210654-o6ji6npmzf2efhmn
#
# Begin patch
=== modified file 'ChangeLog'
--- ChangeLog 2009-09-08 21:06:54 +
+++ ChangeLog 2009-09-15 03:32:37 +
@@ -1,3 +1,8 @@
+2009-09-15 Dav
Hi,
Some gnupdf modules like crypt, text and time have initialization
procedures. Currently they are public procedures and they are
described in the reference manual.
Since they should be called once at startup, I think we should hide
the initialization procedures to the user. The `pdf_init' proc
>
> The rationale after the existence of that function, and also after the
> existence of two different types pdf_fsys_t and pdf_fsys_impl_s, is
> that pdf_fsys_t is intended to be opaque. We may want to expand its
> definition to hold data not related to an specific implementation.
>
Well, then
Ok sorry, the pdf_fsys_s structure exists. In this case I will
provide:
struct pdf_fsys_s pdf_fsys_http;
and a macro:
#define PDF_FSYS_HTTP &pdf_fsys_http
This does not require changes to the filesystem module.
Thanks.
Juan Pedro Bolivar Puente writes:
> David Vazquez wrote:
>> Is there any reason to we have got the `pdf_fsys_create' procedure?
>> It is supposed do:
>>
>> -- Function: pdf_fsys_t pdf_fsys_create (struct pdf_fsys_impl_s
>> IMPLEMENTATION)
>>
Is there any reason to we have got the `pdf_fsys_create' procedure?
It is supposed do:
-- Function: pdf_fsys_t pdf_fsys_create (struct pdf_fsys_impl_s IMPLEMENTATION)
Create and return a new filesystem variable that will use a given
implementation.
which copy the `pdf_fsys_impl_s' s
jema...@gnu.org writes:
>If win32-pthreads is GPLv3+ compatible I would go for the second
>option, since almost any platform is supporting POSIX threads
>nowadays, except mingw32.
>
> The pthreads-win32 software is distributed under the terms of the LGPL
> v1.2, so we can link with it
Hi, I have just started the task about http backend for the file
system module, and I would want to discuss a issue.
If I understand well, RIA is a request for cache a block which be read
later. The task description suggests libcurl to implement it. However,
it seems libcurl does not support asyn
Michael Gold writes:
> On Tue, May 26, 2009 at 00:53:46 +0200, jema...@gnu.org wrote:
> ...
>> We need to be able to determine the boundaries of a token that has
>> been read, for error reporting. We cannot rely on the stm used by the
>> token reader to determine the beginning position of a read
Hi JP,
Juan Pedro Bolivar Puente writes:
> Hi David,
>
> My original implementation is based on the algorythm described here [1]
> which is quite efficient, I see no special benefit in using hash tables.
> I had planned to finish porting the code to the new filters API this
> summer (I know I t
I am working on LZW filter and I will change to use pdf-hash in order
to stand for the string dictionary. It is known this table never will
be longer of 4096 entries. It would be good we could specify a
estimated size the hash tables for performance. I suppose gnulib has
support this.
# timestamp: 2009-05-19 20:37:29 +0200
# base_revision_id: jema...@termi-20090513113335-kllaz0z2vuk048rk
#
# Begin patch
=== modified file 'ChangeLog'
--- ChangeLog 2009-05-11 14:47:49 +
+++ ChangeLog 2009-05-19 18:37:15 +
@@ -1,3 +1,11 @@
+2009-05-19 David Vazquez
+
+ * sr
In order to avoid gcc (>= 4.3.2) warnings about using of static inline
functions in extern inline, I do static inline the functions of
pdf-list and pdf-crypt modules.
# Bazaar merge directive format 2 (Bazaar 0.90)
# revision_id: jema...@termi-20090513113335-kllaz0z2vuk048rk
# target_branch: http
I attach the patch here.
patch
Description: Patch
Hi,
I get warnings from gcc 4.3.2 when compile a module which require the
pdf-list module. The errors are related to C99 and they are of the
kind:
In file included from ./base/pdf-hash.h:30,
from ./base/pdf-stm.h:54,
from base/pdf-stm.c:31:
./base/pdf-list.h: In
The syntax-check script warns pdf-fp-func.c file include assert.h. In
order to avoid it, I have written a PDF_ASSERT_* macro for each layer,
which use PDF_DEBUG_* macros. I document this in the manual.
Indeed, I have export to the public API these both PDF_DEBUG as
PDF_ASSERT macros. I think the
I attach the patch for this task.
docpatch
Description: Binary data
I attach the patch for the task #96.
docpatch
Description: Patch
> What `bad type' errors are those?
Numerical functions will not fail if we pass them a boolean value as
argument.
cl-pdf is another library for pdf generation. It is written in Common
Lisp and it has a freebsd style license.
http://www.fractalconcept.com/asp/mQG3/sdataQvAv8kImQIvQDM==/sdataQucgleAq9b==
There is also a link in order to use pdf forms with cl-pdf:
http://www.cl-user.net/asp/html-docs/p
> Would be useful to return more detailed information: it would be
> really difficult to fix a buggy function facing something like
> "Internal error". But it would be quite difficult to do it in a
> generic way.
>
> What about adding a new specific `pdf_fp_func_4_eval' function? It
> would break t
Well, I tell you points of the task description.
On the one hand, we need a list of syntax errors and a way to
report them in `pdf_fp_func_4_new'. I think that a PDF_BADSYNTAX
return value would works fine. But if more defailed errors are
required, an extra argument is valid. Anyway, the syntax
c
ge...@gnu.org writes:
> Hi all,
>
> If I understand correctly the following lines (1498 and 1511) from
> pdf-fp-func.c
> aren't considering the case when "stack[sp] == 0".
> ##
> case OPC_div:
> if (sp < 1) goto stack_underflow;
> stack[sp-1] /= stack[sp];
>
Hi,
I have taken the task #86. Just as description task suggests I will send
an email with information about several points. Meanwhile, every idea
will be welcome.
Hi,
I have generated pdf files from texinfo manuals and both
`gnupdf-arch.texi' and `gnupdf-hg.texi' contains figures which are show
wrongly. They are not scaled and therefore they do not fit to the page
size. A solution is to specify by each image the size in the texinfo
`...@image' command, th
SPAM Ranking: (4.3 points, 4.0 required)
Text in Spanish, Italian and English
SPANISH:
Spamassassin ha detectado este correo como posible spam. Aunque el sistema
descarta por comodidad los correos con valor mayor de 5, mantenemos un margen
de seguridad para evitar falsos positivos.
Si este corr
jema...@gnu.org writes:
> In that case the number of bytes to write is a function of the number
> of processed bytes. The filter can count how many bytes it processed
> after the last reset, in a local way.
>
> Consider:
>
>
> -> filter1 -> aesv2 -> filter2 ->
>
>
> Both filter1 and filter
jema...@gnu.org writes:
> Currently it is not possible for a filter to know how much information
> has been written by a writing stream. I don't see how that information
> would be useful for a filter: the filter can record how much data was
> filtered at the moment.
I mean it could be required d
jema...@gnu.org writes:
> Hi David.
>
> It seems that the filters never return PDF_EEOF when finish_p equals
> to true: they return either PDF_ENINPUT or PDF_ERROR.
>
> + if (aux_size > out_size)
> +{
> + /* We should can return PDF_ENOUTPUT. However the
> +
Hi jemarch,
The question is we have created an abstraction in the crypt module which
is useful in order to encrypt/decrypt buffers, while the crypt filters
need a more lower level of abstraction. However, this level is hardly
common to AES and RC4 algorithms. So, we are trying to adjust crypt
mod
Ok jemarch. I have written some examples for libgcrypt and I can do it
works incrementally, but we would change the crypt API. So, I propose
the following changes:
1. Edit crypt module (AESV2 only) in order to it doesn't pad the
content.
2. Provide a function:
void pdf_crypt_cipher_pad (C
jema...@gnu.org writes:
> On the other hand, should be a reason for libgcrypt to not provide a
> suitable API for AES to perform de/encryption without having to store
> all the data in memory. It is a restriction imposed by the underlying
> algorithm?
>
It seems I misunderstood a point of the sem
Yes, it semms a good idea.
What do you think about cache all input? Can we do this by the moment?
In that case, I will edit it according to your suggestions.
I forgot to say that I wrote the `pdf_stm_buffer_resize' function and I
documented in the wiki.
Greetings.
Hello,
I include a patch for the crypt filters support. This patch adds:
- AESV2 encoder/decoder filters
- V2 encoder/decoder filters
- MD5 encoder filter
- Fix several bugs in crypt module
It is not complete. Although it works, it needs love. :)
I tell you a couple of issue.
On the f
Hi all,
I have watched a strange behaviour in the filter support implementation
while I was writing AESv2 filter. My _apply function is being called
several times with the input buffer at EOB. I don't how to manage this
in AESv2 filter, since an empty buffer is a valid input. May anyone
explain b
jema...@gnu.org writes:
> pdf_status_t pdf_stm_buffer_resize (pdf_stm_buffer_t BUFFER, pdf_size_t
> NEW_SIZE);
>
> Resize a given buffer.
>
> If NEW_SIZE is larger than the actual size of @var{buffer} then BUFFER->size
> will be increased, while both BUFFER->rp and BUFFER->wp will remain
> uncha
ych writes:
> Hi,
>
>
>
> I need a method of resize
"Vivek Paradkar" <[EMAIL PROTECTED]> writes:
> How do we test the filters we have implemented?
Hi Vivek
We are writing the tests in torture/unit/base/stm/pdf-stm-{write,read}.c.
I would like to take this opportunity to see you that CK_FORK
environment variable does not work now. From Check manu
Hi all,
I report that it is a bug, I think. The `pdf_stm_install_filter'
function returns PDF_OK even when filter's _init function failed. It
would useful since some filters could fail if it is missing parameters.
Greetings
[EMAIL PROTECTED] writes:
>I think it would not give us troubles in a future, since it could be
>thought as an interface nicer than crypt module. However if it is not a
>problem I have not objection.
>
>What do we do?
>
> I would write filters for all the cryptographic algorithms
[EMAIL PROTECTED] writes:
> It would not be a problem to delay the development of these filters.
> Anyway, let's see what David works out.
I think it would not give us troubles in a future, since it could be
thought as an interface nicer than crypt module. However if it is not a
problem I have n
Hello all
I am writing crypt filter and it arises a doubt related to
gnupdf's design. According to PDF Reference, encrpytion is defined
(mostly) by a global dictionary. This dictionary holds a list of crypt
filters will
be used in the rest of the document.
I suppose crypt filter module will recei
I have written some examples for crypt module API.
jemarch, I could take a simple task, any suggestion?
# Bazaar merge directive format 2 (Bazaar 0.90)
# revision_id: [EMAIL PROTECTED]
# target_branch: http://bzr.savannah.gnu.org/r/pdf/libgnupdf/branches\
# /trunk/
# testament_sha1: 8cadf9b6dc7
: 6b31f6effd712715a5592066a6c69e65d582ff71
# timestamp: 2008-10-03 18:08:34 +0200
# base_revision_id: [EMAIL PROTECTED]
#
# Begin patch
=== modified file 'ChangeLog'
--- ChangeLog 2008-10-02 20:49:15 +
+++ ChangeLog 2008-10-03 16:08:19 +
@@ -1,3 +1,7 @@
+2008-10-03 David Vazquez <[EM
: dd399a071183ce13b42717ac370fc31be72d5547
# timestamp: 2008-09-13 17:45:45 +0200
# base_revision_id: [EMAIL PROTECTED]
#
# Begin patch
=== modified file 'ChangeLog'
--- ChangeLog 2008-09-12 03:03:25 +
+++ ChangeLog 2008-09-13 15:44:46 +
@@ -1,3 +1,7 @@
+2008-09-13 David Vazquez <[EMAIL PROTECTED]>
[EMAIL PROTECTED] writes:
> Hi David.
>
>I have written some fixes.
>What is your opinion?
>
> I think the API is ok. I just installed your patch into the
> trunk. Please mark the task #59 as closed.
>
> Many thanks.
Thanks jemarch. Let me know when you think we should start to
implement
I have written some fixes.
patch
Description: Binary data
What is your opinion?
[EMAIL PROTECTED] writes:
> I would be happy to introduce the use of such a tool in GNU PDF but,
> due to the workflow we use (first design the API of the module and
> document it in the refman, then implement it) we really need to have
> some place to document the API before to write any code. If
[EMAIL PROTECTED] writes:
> Thanks :) Some comments about the patch follows.
>
> [EMAIL PROTECTED] Initializating the module
> [EMAIL PROTECTED] Initializating the module
> +
> +The encryption module must be initialized when Libgnupdf library was
> +loaded It is *NOT* safe-thread.
>
> What kind o
ChangeLog'
--- ChangeLog 2008-08-06 21:45:28 +
+++ ChangeLog 2008-08-09 03:27:32 +0000
@@ -1,3 +1,9 @@
+2008-08-09 David Vazquez <[EMAIL PROTECTED]>
+
+ * doc/gnupdf.texi (Encryption, Initializating the module)
+ (Creating and destroying Ciphers, Encryption and decryption)
+ (Utils fu
I have written a draft of encryption module wiki page[1]. Operations
must be described yet. I would like someone will revise for spelling
mistakes, etc. Thanks a lot.
Suggestions are welcome.
[1] http://www.gnupdf.org/Lib:Architecture/Base_Layer/Crypt_Module
--
[EMAIL PROTECTED] writes:
>> Does OUTSIZE not function as a guard to make it easier to avoid
>> overflowing the 'out' buffer?
>
>Yes, it is true. But I mean, we can provide a function or macro
>which return the size of the encrypted output buffer. So we avoid
>caller need know
[EMAIL PROTECTED] writes:
>Just a note that Acrobat 9 includes a new encryption option that is
>based on AES256, but with a completely different methodology for
>generating the seed/initialization vector _AND_ which also now supports
>Unicode passwords.
>
> David, do libgcrypt sup
Hello jemarch,
> /* Initialize module */
> pdf_status_t pdf_crypt_init (void);
>
> Please remember in this point that, since the library should be
> thread-safe, you cannot maintain any global state.
>
However libgcrypt requires initialization. It must be called once at
startup. I wi
Hi all
I have read the PDF Reference in deeper to define our
requirements. The situation is the following. API Reference offers two
methods to decrypt data.
- V2 method uses the RC4 algorithm, which is a stream cipher.
- AESV2 method uses AES128 and Cipher Block Chaining (CBC) operation
[EMAIL PROTECTED] writes:
> David, maybe would be a good idea to create a new module 'pdf-crypt'
> in the base layer containing functions to:
>
> - de/encrypt pdf_text_t values.
> - de/encrypt memory regions (buffers). This interface would be used in the
>implementation of the crypt stm filt
Juan Pedro Bolivar Puente <[EMAIL PROTECTED]> writes:
> Are you David the developer of Pleim in the CUSL? It seems so :) I am
> the maintainer of Psychosynth.
>
> I liked your project -I hope you find time to continue it eventually-
> and your programming style quite a lot. Welcome abroad :)
Yea
[EMAIL PROTECTED] writes:
>A crypt filter dictionary contains (amongst others) a key named CFM,
>whose value could be one of three:
> - None
> - V2 (for RC4/ARC4)
> - AESV2 (for AES)
>
> So in the end we would need to write stm filters for RC4/ARC4 and AES,
> isnt it?
>
Hi!
There are several files in the base layer whose header contains
Time-stamp: "". However GNU/Emacs requires a whitespace so:
Time-stamp: " " in order to update it.
The list of files is:
pdf-text.c
pdf-text-context.c
pdf-text-context.h
pdf-text-encoding.c
pdf-text-encoding.h
pdf-te
[EMAIL PROTECTED] writes:
> Could you please write down a summary of all the needed parameters
> for both filters?
Of course :)
In the encryptation dictionary, both filters involves the use of
following parameters:
- The entry V specifies the type of algorithm to be used. It should
be 4
Well, it seems it was a misundertanding. I thought you mean libcrypt
indeed of libgcrypt. At version 1.4.0 of the 6 December 2007,
libgcrypt supports both AES and ARC4 encryptation algorithms, and md5
hashing function. :)
--
Hello!
My name is David and I would like learn and contribute with you.
I am a spanish student of mathematics, a programming enthusiast and a
Emacs user :). I usually develop in C and Lisp, although it is my
first approach to a real free software project really. So I hope you
will have enough pa
66 matches
Mail list logo
