dotgnu-general
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[DotGNU]Re: Developers digest, Vol 1 #1028 - 8 msgs


From: eanï
Subject: [DotGNU]Re: Developers digest, Vol 1 #1028 - 8 msgs
Date: Mon, 11 Aug 2003 09:12:38 +0200

----- Original Message ----- 
From: <address@hidden>
To: <address@hidden>
Sent: Monday, August 11, 2003 12:55 AM
Subject: Developers digest, Vol 1 #1028 - 8 msgs


> Send Developers mailing list submissions to
> address@hidden
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://dotgnu.org/mailman/listinfo/developers
> or, via email, send a message with subject or body 'help' to
> address@hidden
>
> You can reach the person managing the list at
> address@hidden
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Developers digest..."
>
>
> Today's Topics:
>
>    1. Re: Reminder - Weekly DotGNU Meeting (DrDiettrich)
>    2. Re: Dotgnu written in C#? (DrDiettrich)
>    3. Re: Re: proposal: DotGNU Trademark License (DrDiettrich)
>    4. Re: Dotgnu written in C#? (Fergus Henderson)
>    5. Fwd: Re: [Savannah-hackers] submission of VCG graph visualization
for DotGNU Pnet/ - savannah.nongnu.org (James Michael DuPont)
>    6. [PNET][ILASM/ILALINK][LINKERERRORS] Problems linking in sqrt, please
help (James Michael DuPont)
>    7. ANN : Call for help with a porting of VCG to Dotgnu pnet/c (James
Michael DuPont)
>    8. [DGEE][AUTHENTICATION] RFC for a new auth engine (James Michael
DuPont)
>
> --__--__--
>
> Message: 1
> Date: Sat, 09 Aug 2003 15:27:49 +0200
> From: DrDiettrich <address@hidden>
> To: DotGNU <address@hidden>
> Subject: Re: [DotGNU]Reminder - Weekly DotGNU Meeting
>
> Rich Baumann wrote:
> > It's not my fault if you're using a broken operating system.
>
> Start an flame war? ;-)
>
> Who are you that you can dictate which OS everybody else has to use?
>
> > Since the
> > date command is, as far as I know, a part of the Portable Operating
> > System Interface standard, you should complain to your OS vendor if your
> > OS doesn't have it.
>
> I don't know whether my system has such a command, and I felt happy
> without it for more than 30 years.
>
> > If you're using windows, you can install cygwin
> > (cygwin.com), which supplies many of the core missing (broken) parts of
> > your OS, after which you can install the GNU coreutils package
> > (gnu.org/software/coreutils) which contains the date program.
>
> This is just a topic which I would like to discuss, but not restricted
> to the date command. See my parallel mail about the make process of GNU
> software...
>
> If I ever wanted to use Unix, then I would use it, but in fact I want to
> use a different OS, which follows different standards. Every criticism
> on that decision is arrogant and futile.
>
> > Alternatively, you can check the "world clock" at timeanddate.com
> > (scroll down to find UTC).
>
> I also don't want to be connected to the Web all the time, because I
> cannot afford such luxury.
>
> > UTC is the international time standard; GMT is not.
>
> Both are international standards.
>
> > That's why there's no "date -g" option.
>
> I hate such broken tools ;-)
>
> > UTC has no daylight savings adjustments, so you can
> > do the calculation yourself, based on current GMT (which does have such
> > adjustments). The only difference between the two IS daylight savings
> > adjustments.
>
> Finally a serious point. I understand the advantage of a time base,
> which is independent from daylight saving shifts.
>
> But I don't understand why such a long comment on UTC is posted with
> every meeting time, telling the user which tool how to use for time
> conversion. Plus another lengthy comment about how to make this tool
> available on non-Unix platforms. Aren't we humans alltogether, which can
> and prefer to perform such simple calculations even without computer
> assistance? Herefore a description of tools is absolutely inappropriate,
> whereas the last sentence of your reply contains all required
> information:
>
> "The difference between UTC and GMT is daylight savings adjustments."
>
> Peace? ;-)
>
> DoDi
>
>
>
> --__--__--
>
> Message: 2
> Date: Sat, 09 Aug 2003 16:35:18 +0200
> From: DrDiettrich <address@hidden>
> To: DotGNU <address@hidden>
> Subject: Re: [DotGNU]Dotgnu written in C#?
>
> Rhys Weatherley wrote:
> > Try getting an application written by a Windows or Mac programmer to
compile
> > on *anything* except the original platform, even if they aren't using
the
> > GUI.  Porting from Unix to Windows/Mac is difficult.  Porting in the
opposite
> > direction is impossible.
>
> Let me take the date tool as an example. I see no reason why such a tool
> could not be compiled on any platform, without modifications. The build
> process may be different, but that's the task of the development system
> of the platform, not of the tool. The code can retrieve all required
> information by standard (ANSI/POSIX/GNU...) calls, which of course must
> and can be implemented once for every platform.
>
> In the next step the UI dependencies also should be separated from the
> working stuff, so that the kernel code of every tool can be used in any
> environment, be it as a stand alone program or only as a set of
> procedures in another program.
>
> > I'm sorry to see that you've had problems getting GNU code to compile.
It is
> > important to remember that "make it work for GNU first, Unix next, and
other
> > platforms later" is one of the standard GNU coding guidelines.
>
> A reasonable decision, but what's the definition of "GNU" in the above
> context?
>
> Perhaps we are talking primarily about an inappropriate or even
> inexistent definition of a GNU environment, which could be much more
> simpler and platform independent itself?
>
> > I will note that before the introduction of automake/autoconf, this was
a
> > *lot* worse.  What we have now in the Free Software community is heaven
> > compared to before.  There is always room for improvement of course and
if
> > you manage to come up with a way, then a lot of people will be very
happy.
>
> This really is a topic where I would like to spend some time. It looks
> to me as if GNUish people are somewhat helpless in downsizing, and
> instead prefer to invent additional tools over and over again, only to
> cure symptoms instead of the real disease.
>
> > Portability is hard, and it isn't just a dependency or tools issue.
It's
> > primarily an API issue - if you can't rely upon the API's being the
same,
> > then it is hard to make the code portable.  No matter what scheme is
devised
> > to describe the API differences, it will eventually tend towards
spaghetti.
> > The set of exceptions to the rules is too great.
>
> That's why I think that "describing the differences" simply is the wrong
> way to go. Better were "defining an GNU API", which then can be
> implemented on every platform, and which eliminates every platform
> dependencies in the source code.
>
> > One of the goals of pnetC is to address this by creating a uniform
Posix-like
> > API on all CLI-compatible platforms.  That will resolve a lot of
portability
> > problems.  But at the end of the day, it is the programmer that has to
write
> > portable code - the tools cannot do it for him/her.
>
> The tools could prevent the programmer from writing NON-portable code,
> by flagging all non-ANSI or non-CLI or non-GNU constructs in the source
> code. Add information about the proper API to be used instead to every
> message, and any platform dependent code will turn out as being created
> willingly by a dumb or malevolent programmer.
>
> Writing platform independent code only requires the existence of a
> platform independent API. GNU failed to both define a GNU platform and
> API, and that's the only reason why GNUish code in fact is not freely
> portable. Provided that you have no more precise description for the GNU
> platform and API, that environment is made up from all the tools around
> the build process. This obviously is an unusable definition, which is
> extended with every new tool or revision, since everybody might want to
> use such new extensions in the build process of his program.
>
> If we don't restrict the build process of DotGNU programs to a minimum
> set of related tools, then the same mess with platform specific build
> procedures will occur in DotGNU projects, too, sooner or later. That's
> why I feel an urgent need for a definition of an platform independent
> standard build process.
>
> DoDi
>
>
>
> --__--__--
>
> Message: 3
> Date: Sat, 09 Aug 2003 17:22:03 +0200
> From: DrDiettrich <address@hidden>
> To: Norbert Bollow <address@hidden>, address@hidden
> CC: address@hidden
> Subject: Re: [DotGNU]Re: proposal: DotGNU Trademark License
>
> Norbert Bollow wrote:
> >    (b) You must provide your customers with a written offer, valid for
> >        at least three years, to give them upon request, at no extra
> >        charge, on a medium customarily used for software interchange,
> >        licensed under the terms of the GNU General Public License,
> >        a complete machine-readable copy of the source code of the
> >        webservice program plus any compilers and libraries which are
> >        needed to translate the webservice program into executable
> >        form.
>
> This description IMO is not appropriate. At least the term "compilers"
> must be extended into all tools (and everything else), which are
> required to build the program. Since the build process for a program is
> heavily platform dependent, the provider of the service should not be
> burdened with such details. Instead everything, which is required to
> build the program, should be freely available from some trusted source,
> under <above> conditions. For the program specific items a similar
> delegation to a trusted source should be possible, which can guarantee
> the availability of all components independently from the service
> provider. If the service provider "dies" before the time mentioned
> above, whom would anybody hold liable then?
>
> The intention should be to guarantee a recompilation of the service,
> independently from the service provider. Any specification of
> what-must-be-provided can be used to make the build process dependent on
> something which is not explicitly mentioned. I also would replace
> "provide" by "make available".
>
> DoDi
>
>
> --__--__--
>
> Message: 4
> Date: Mon, 11 Aug 2003 03:07:20 +1000
> From: Fergus Henderson <address@hidden>
> To: DrDiettrich <address@hidden>
> Cc: DotGNU <address@hidden>
> Subject: Re: [DotGNU]Dotgnu written in C#?
>
> On 09-Aug-2003, DrDiettrich <address@hidden> wrote:
> > Rhys Weatherley wrote:
> > > Portability is hard, and it isn't just a dependency or tools issue.
It's
> > > primarily an API issue - if you can't rely upon the API's being the
same,
> > > then it is hard to make the code portable.  No matter what scheme is
devised
> > > to describe the API differences, it will eventually tend towards
spaghetti.
> > > The set of exceptions to the rules is too great.
> >
> > That's why I think that "describing the differences" simply is the wrong
> > way to go. Better were "defining an GNU API", which then can be
> > implemented on every platform, and which eliminates every platform
> > dependencies in the source code.
>
> How should this proposed GNU API differ from POSIX?
>
> Note that defining a GNU API would not solve the problem.
> Many programs would still want to make use of additional features
> provided by some environments that are not part of the GNU API.
> So either the GNU API would have to be extended for every such program
(this
> approach doesn't scale), or something like autoconf would still be needed.
>
> > Writing platform independent code only requires the existence of a
> > platform independent API. GNU failed to both define a GNU platform and
> > API, and that's the only reason why GNUish code in fact is not freely
> > portable.
>
> I don't agree.  Your analysis is overly simplistic, and ignores the
> competitive pressures on applications to make use of non-portable
features.
>
> If what you say were true, then the Posix standard and its GNU/Linux
> implementation would have solved the problem.  But it didn't, because --
> guess what -- most applications wanted to make use of additional features
> not provided by Posix.
>
> -- 
> Fergus Henderson <address@hidden>  |  "I have always known that the
pursuit
> The University of Melbourne         |  of excellence is a lethal habit"
> WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.
>
> --__--__--
>
> Message: 5
> Date: Sun, 10 Aug 2003 15:57:36 -0700 (PDT)
> From: James Michael DuPont <address@hidden>
> To: address@hidden
> Cc: address@hidden
> Subject: [DotGNU]Fwd: Re: [Savannah-hackers] submission of VCG graph
visualization for DotGNU Pnet/ - savannah.nongnu.org
>
> Does anyone object to me naming a project vcgdotgnu, to represent the
> fact that it is an application of dotgnu?
>
> mike
> --- Rudy Gevaert <address@hidden> wrote:
> > From Rudy Gevaert Sun Aug 10 15:22:20 2003
> > X-Apparently-To: address@hidden via 66.218.93.91; Sun, 10 Aug
> > 2003 15:23:41 -0700
> > Return-Path: <address@hidden>
> > Received: from 199.232.76.164  (EHLO fencepost.gnu.org)
> > (199.232.76.164)
> >   by mta115.mail.scd.yahoo.com with SMTP; Sun, 10 Aug 2003 15:23:41
> > -0700
> > Received: from rudy by fencepost.gnu.org with local (Exim 4.20)
> > id 19lyZw-0002Ji-Sy; Sun, 10 Aug 2003 18:22:20 -0400
> > Date: Sun, 10 Aug 2003 18:22:20 -0400
> > From: Rudy Gevaert <address@hidden>
> > To: James Michael DuPont <address@hidden>
> > CC: Rudy Gevaert <address@hidden>, address@hidden
> > Subject: Re: [Savannah-hackers] submission of VCG graph visualization
> > for DotGNU Pnet/ - savannah.nongnu.org
> > Message-ID: <address@hidden>
> > Mail-Followup-To: Rudy Gevaert <address@hidden>,
> > James Michael DuPont <address@hidden>,
> > address@hidden
> > References: <address@hidden>
> > <address@hidden>
> > Mime-Version: 1.0
> > Content-Type: text/plain; charset=us-ascii
> > Content-Disposition: inline
> > In-Reply-To: <address@hidden>
> > User-Agent: Mutt/1.3.28i
> > X-Operating-System: GNU/Linux 2.4.20-19.9smp
> > X-Home-Page: http://www.webworm.org
> > X-PGP-Public-Key: 1024D/24DC49C6
> > X-PGP-Fingerprint: 264F CD1D 7F06 7B34 DBE0  6E54 FFEE 4906 24DC 49C6
> > Content-Length: 665
> >
> > On Sun, Aug 10, 2003 at 02:18:26PM -0700, James Michael DuPont wrote:
> > > I will be redoing all of the file headers.
> > > The code that I am checking in right now has non at all.
> > > that will change.
> > >
> > > One thing, about the name, I should have pointed out that vcgdotgnu
> > > contains dotgnu in it. that also contains gnu.
> > >
> > > is that a problem?
> >
> > Not for me, it's a different case as e.g. gnurudy.  I read it
> > vcg-dotgnu, not vcg-dot-gnu.
> >
> >
> > -- 
> > Rudy Gevaert                address@hidden
> > Web page                    http://www.webworm.org
> > GNU/Linux for schools       http://www.nongnu.org/glms
> > Savannah hacker             http://savannah.gnu.org
> >
>
>
> =====
> James Michael DuPont
> http://introspector.sourceforge.net/
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
>
> --__--__--
>
> Message: 6
> Date: Sun, 10 Aug 2003 16:10:08 -0700 (PDT)
> From: James Michael DuPont <address@hidden>
> To: address@hidden
> Subject: [DotGNU][PNET][ILASM/ILALINK][LINKERERRORS] Problems linking in
sqrt, please help
>
> Dear all,
> I am having problems linking in sqrt,
>
> here is my IL code, it was extracted from my pnet/c code,
> but I boiled it down to something simple :
>
> .module '<Module>'
>
> .method public static void 'foo'() cil managed
> {
>
> call       float64 '<ModuleExtern>'::'sqrt'(float64)
> }
>
>
> here are the results :
> ilasm testsqrt.il
> ilalink testsqrt.obj
> a.out: no entry point specified
> float64 '<Module>'::sqrt(float64) : unresolved method reference
>
> how can i link in sqrt ?
>
> rhys, I know you might be pissed off with me,
> I have been trying to contribute more productivly to the project.
> please if you can take a minute and give me a push in the right
> direction?
>
> thanks,
>
> mike
>
> =====
> James Michael DuPont
> http://introspector.sourceforge.net/
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
>
> --__--__--
>
> Message: 7
> Date: Sun, 10 Aug 2003 16:32:50 -0700 (PDT)
> From: James Michael DuPont <address@hidden>
> To: address@hidden
> Subject: [DotGNU]ANN : Call for help with a porting of VCG to Dotgnu
pnet/c
>
> --0-1732078107-1060558370=:57167
> Content-Type: text/plain; charset=us-ascii
> Content-Id:
> Content-Disposition: inline
>
> Dear Dotgnuers,
>
> I have spent most of my day today compiling the visualization of
> compiler graphs automatic graph layout VCG tool for pnet/C.
> After reporting many bugs and wondering about many messages, i have
> been able to get it to compile.
>
> Now I need help linking it into all the great stuff you are working on.
>
> Specifically the x11# and windforms. This vcg could be used as the most
> kick ass winforms control you have ever seen with auto graph
> layout!!!!!!
>
> Maybe someone wants to help out? Send me your savannah ID and I will
> sign you up.
>
> Here is the new project page with the files in it :
> https://savannah.nongnu.org/projects/vcgdotgnu/
>
> here is the (wiki) webpage
> http://gnufans.net/intrspctr.pl?VcgInterface
>
> Here is the snapshot with il files (2mb)
> 33e613f75b84ac7b65c2905279186a8d  vcgdotgnu-pre-alpha.tgz
>
http://savannah.nongnu.org/download/vcgdotgnu/vcgdotgnu.pkg/0.0.0.1/vcgdotgnu-pre-alpha.tgz
>
> I wonder how to get the makefile right, and would appreciate some tips
> on that  (attached)
>
> The problem is however, the set of problems with the system libs, there
> are lots of linker errors :
>
> Here are the system calls :
> token 0x0A00000B: member `<Module>.sqrt' not found
> token 0x0A0000B8: member `<Module>.atof' not found
> token 0x0A0000BB: member `<Module>._IO_getc' not found
> token 0x0A000104: member `<Module>.gettimeofday' not found
> token 0x0A000109: member `<Module>.sleep' not found
> token 0x0A00010A: member `<Module>.system' not found
> token 0x0A000113: member `<Module>.__builtin_memcpy' not found
> token 0x0A00004A: member `<Module>.__ctype_b_loc' not found
> token 0x0A000073: member `<Module>.getcwd' not found
> token 0x0A000074: member `<Module>.opendir' not found
> token 0x0A000075: member `<Module>.stat' not found
> token 0x0A000077: member `<Module>.asctime' not found
> token 0x0A00007B: member `<Module>.getgrgid' not found
> token 0x0A00007C: member `<Module>.readdir' not found
> token 0x0A00007D: member `<Module>.closedir' not found
> token 0x0A00007E: member `<Module>.qsort' not found
> token 0x0A00005E: member `<Module>.atoi' not found
> token 0x0A000062: member `<Module>.exp' not found
>
> Here are X11 calls that I want to replace with calls to x11#
> token 0x0A00001D: member `<Module>.XOpenDisplay' not found
> token 0x0A00001E: member `<Module>.XDisplayName' not found
> token 0x0A00001F: member `<Module>.XDefaultScreen' not found
> token 0x0A000020: member `<Module>.XDisplayPlanes' not found
> token 0x0A000021: member `<Module>.XDisplayWidth' not found
> token 0x0A000022: member `<Module>.XDisplayHeight' not found
> token 0x0A000023: member `<Module>.XDefaultColormap' not found
> token 0x0A000024: member `<Module>.XWhitePixel' not found
> token 0x0A000025: member `<Module>.XBlackPixel' not found
> token 0x0A000027: member `<Module>.XSetForeground' not found
> token 0x0A000028: member `<Module>.XFillRectangle' not found
> token 0x0A00002A: member `<Module>.XSetInputFocus' not found
> token 0x0A00002D: member `<Module>.XMoveResizeWindow' not found
> token 0x0A00002F: member `<Module>.XCopyArea' not found
> token 0x0A000030: member `<Module>.XSync' not found
> token 0x0A000031: member `<Module>.XResizeWindow' not found
> token 0x0A000032: member `<Module>.XNextEvent' not found
> token 0x0A000037: member `<Module>.XCreateWindow' not found
> token 0x0A000038: member `<Module>.XCreateBitmapFromData' not found
> token 0x0A000039: member `<Module>.XLoadQueryFont' not found
> token 0x0A00003C: member `<Module>.XSetStandardProperties' not found
> token 0x0A00003D: member `<Module>.XMapRaised' not found
> token 0x0A00003E: member `<Module>.XFlush' not found
> token 0x0A00003F: member `<Module>.XCreateFontCursor' not found
> token 0x0A000040: member `<Module>.XDefineCursor' not found
> token 0x0A000041: member `<Module>.XDestroyWindow' not found
> token 0x0A000042: member `<Module>.XCloseDisplay' not found
> token 0x0A000045: member `<Module>.XDrawString' not found
> token 0x0A000046: member `<Module>.XAllocColor' not found
> token 0x0A000047: member `<Module>.XGetWindowAttributes' not found
> token 0x0A000048: member `<Module>.XParseGeometry' not found
> token 0x0A00004D: member `<Module>.XMapWindow' not found
> token 0x0A00004E: member `<Module>.XDefaultGC' not found
> token 0x0A00004F: member `<Module>.XChangeGC' not found
> token 0x0A000050: member `<Module>.XCreatePixmap' not found
> token 0x0A000051: member `<Module>.XSetFont' not found
> token 0x0A000052: member `<Module>.XCreateSimpleWindow' not found
> token 0x0A000053: member `<Module>.XTextWidth' not found
> token 0x0A000054: member `<Module>.XDrawLine' not found
> token 0x0A000055: member `<Module>.XFillPolygon' not found
> token 0x0A000056: member `<Module>.XSetLineAttributes' not found
> token 0x0A000057: member `<Module>.XSetDashes' not found
> token 0x0A000058: member `<Module>.XDrawArc' not found
> token 0x0A000059: member `<Module>.XFillArc' not found
> token 0x0A00005A: member `<Module>.XLookupString' not found
> token 0x0A00005C: member `<Module>.XMoveWindow' not found
> token 0x0A00005D: member `<Module>.XSetWindowBorderWidth' not found
>
> token 0x0A000064: member `<Module>.XUnmapWindow' not found
> token 0x0A000065: member `<Module>.XIconifyWindow' not found
> token 0x0A000067: member `<Module>.XQueryPointer' not found
> token 0x0A000068: member `<Module>.XStoreName' not found
> token 0x0A000069: member `<Module>.XSetNormalHints' not found
>
> token 0x0A000088: member `<Module>.XCreateGC' not found
> token 0x0A000089: member `<Module>.XSetBackground' not found
> token 0x0A00008A: member `<Module>.XCopyPlane' not found
>
>
> Here are internal problems :
>
> token 0x0A000049: member `struct
> (BtYgtrQRVUDUqztrB1hBnA).default_screen' not found
> token 0x0A00008C: member `struct gs_scroll_bar.is' not found
> token 0x0A00008D: member `struct gs_scroll_bar.glob' not found
> token 0x0A00002E: member `<Module>.log' not found
> token 0x0A00007F: member `struct gs_scroll_bar.wl' not found
> token 0x0A000080: member `struct gs_scroll_bar.wr' not found
> token 0x0A000081: member `struct gs_scroll_bar.xt' not found
> token 0x0A000082: member `struct gs_scroll_bar.xv' not found
> token 0x0A000083: member `struct gs_scroll_bar.xb' not found
> token 0x0A000084: member `struct gs_scroll_bar.y' not found
> token 0x0A000036: member `struct (BtYgtrQRVUDUqztrB1hBnA).screens' not
> found
>
>
> thanks,
>
> mike
>
> =====
> James Michael DuPont
> http://introspector.sourceforge.net/
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
> --0-1732078107-1060558370=:57167
> Content-Type: application/octet-stream; name=Makefile
> Content-Transfer-Encoding: base64
> Content-Description: Makefile
> Content-Disposition: attachment; filename=Makefile
>
> YWxsIDogbGlua2VycmVwb3J0LnR4dAoJY2F0IGxpbmtlcnJlcG9ydC50eHQK
> CnRyZWUubyA6IHRyZWUuYwoJZm9yIHggaW4gKi5jOyBkbyBjc2NjIC1nIC1j
> ICR4OyBkb25lCgp0cmVlLm8uaWwgOiB0cmVlLm8KCXNoIC4vZG9pbGRhc20u
> c2gKCmEub3V0IDogdHJlZS5vCglpbGFsaW5rICoubwoKCmxpbmtlcnJlcG9y
> dC50eHQgOiBhLm91dAoJaWx2ZXJpZnkgYS5vdXQgPiBsaW5rZXJyZXBvcnQu
> dHh0IDI+JjEKCg==
>
> --0-1732078107-1060558370=:57167--
>
> --__--__--
>
> Message: 8
> Date: Sun, 10 Aug 2003 16:54:05 -0700 (PDT)
> From: James Michael DuPont <address@hidden>
> To: address@hidden
> Subject: [DotGNU][DGEE][AUTHENTICATION] RFC for a new auth engine
>
> Dear All,
>
> I propose the following simple solution to our auth problems :
>
> 1. The signing of xmlrpc requests as an outer layer of xmlrpc :
> the header of the packet contains the uri of the signed foaf
> of the user on the local sever, and a uri of the session.
> the session uri contains the ip of the client the port and the
> username.
> the payload is the orignal xmlrpc request.
> the signature is an smime signature of the header and the payload.
>
>     +------------------------------------+
>     | |
>     |   +Header |
>     |   +------+--UserID        |
>     |   |       +--SessionID  |
>     |   |       |
>     |   |-+Payload     |
>     |   |     +----------------------+ |
>     |   |     |           | |
>     |   |     |   data        | |
>     |   |     |   ######             | |
>     |   |     |              | |
>     |   |     |              | |
>     |   |     +----------------------+ |
>     |   |-+-Signature        |
>     | |
>     +------------------------------------+
>
> 2.
> the client talks to the the auth server,
> it authenticate the client, and packages the request.
> it is then sent to the dgee server that uses ssl to verify the
> signature of the pacakge and processes the request.
> the dgee can send a datapackage or querty to the data server that will
> do permanent storage of any needed data.
>
>  +-----------+      +---------+      +---------+
>  |   auth    |  req |   dgee  |  req |  data   |
>  |   service +----|>| service |----|>|  server |
>  +-----------+      +---------+      +---------+
>
>
> This idea is so simple and can be implemented using standard http tools
> such as perl for the auth and data service. the communication is
> standard and based on xmlrpc. the ssh/smime tools to sign and verify
> the signatures are simple to implment using openssl.
>
> what do you think?
>
> mike
>
> =====
> James Michael DuPont
> http://introspector.sourceforge.net/
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
>
>
> --__--__--
>
> _______________________________________________
> Developers mailing list
> address@hidden
> http://dotgnu.org/mailman/listinfo/developers
>
>
> End of Developers Digest
>
>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]