Menu
▾
▴
perl-ldap-dev
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(200) |
Jun
(129) |
Jul
(184) |
Aug
(204) |
Sep
(106) |
Oct
(79) |
Nov
(72) |
Dec
(54) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(83) |
Feb
(123) |
Mar
(84) |
Apr
(184) |
May
(106) |
Jun
(111) |
Jul
(104) |
Aug
(91) |
Sep
(59) |
Oct
(99) |
Nov
(100) |
Dec
(37) |
| 2002 |
Jan
(148) |
Feb
(88) |
Mar
(85) |
Apr
(151) |
May
(80) |
Jun
(110) |
Jul
(85) |
Aug
(43) |
Sep
(64) |
Oct
(89) |
Nov
(59) |
Dec
(42) |
| 2003 |
Jan
(129) |
Feb
(104) |
Mar
(162) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Chris W. <ch...@cw...> - 2002-02-23 19:01:42
|
A new version (0.57) of SPOPS (Simple Perl Object Persistence with Security) has been released to CPAN. SPOPS is a robust and powerful module that allows you to serialize objects to DBI, LDAP and GDBM datasources. You can create most objects without any code, just configuration. This release includes support for Oracle and the new Perl interface for the embeddable SQLite database. A number of small bugs are also fixed. URLs: Download (or use CPAN): http://prdownloads.sourceforge.net/openinteract/SPOPS-0.57.tar.gz Detailed changes: http://sourceforge.net/project/shownotes.php?release_id=76557 Chris -- Chris Winters (ch...@cw...) Building enterprise-capable snack solutions since 1988. |
|
From: Jennifer J. <lis...@su...> - 2002-02-21 22:56:58
|
We'd like to offer you the opportunity to list your website on= Yahoo=2E Click here if you're interested: http://www=2Esubmititright=2Ecom/?AID=3Dy4&Email=3Dperl-ldap%40mail=2Emed=2Ec= ornell=2Eedu Your site will be indexed and listed within 5 days=2E Best Regards, Jennifer Jenkins Customer Service ********************************************************** Note: If your e-mail program did not display the link correctly,= simply copy and paste the following line into your browser's= address bar and hit [ENTER]: http://www=2Esubmititright=2Ecom/?AID=3Dy4&Email=3Dperl-ldap%40mail=2Emed=2Ec= ornell=2Eedu ********************************************************** Why are you on our mailing list? You opted-in to our mailing list when you submitted your ad or= URL (either manually or through a submission service) to one of our search engines, FFA, or classified sites=2E To unsubscribe, please= click here: http://www=2Efuturevisiontoday=2Ecom/promotion/remove=2Easp?AID=3Dy4&Emai= l=3Dperl-ldap%40mail=2Emed=2Ecornell=2Eedu ********************************************************** |
|
From: Chris R. <chr...@me...> - 2002-02-21 15:07:09
|
Graham Barr <gb...@po...> wrote: > On Thu, Feb 21, 2002 at 08:40:05AM -0000, Chris Ridd wrote: >> Graham Barr <gb...@po...> wrote: >> > I think it is time that we stopped holding ourselves back and drop >> > support for running Net::LDAP under perl5.004 >> > >> > So unless someone speaks up with a very compelling argument, the >> > next release of perl-ldap will require at least perl5.005_03 >> > >> > Graham. >> > >> >> What are the differences between these 2 versions, and how do they affect >> Net::LDAP? > > Its mainly just syntax. I could easily make most of Net::LDAP be OK. > But Filter is using a regexp that 5.004 does not like (but we may find > a different solution) > > But also more and more of the modules we depend on are moving on. > The DSML module I am working on uses XML::SAX, which will not work > with 5.004 > > So its getting to the point where we say "we support 5.004, but if you > want to do this, that or the other your mileage will vary" OK, that makes sense. I'd be concerned if we were suddenly going to require 5.6 or something. You've got my vote for requiring 5.005_03. Cheers, Chris |
|
From: Graham B. <gb...@po...> - 2002-02-21 14:59:10
|
On Thu, Feb 21, 2002 at 08:40:05AM -0000, Chris Ridd wrote: > Graham Barr <gb...@po...> wrote: > > I think it is time that we stopped holding ourselves back and drop > > support for running Net::LDAP under perl5.004 > > > > So unless someone speaks up with a very compelling argument, the > > next release of perl-ldap will require at least perl5.005_03 > > > > Graham. > > > > What are the differences between these 2 versions, and how do they affect > Net::LDAP? Its mainly just syntax. I could easily make most of Net::LDAP be OK. But Filter is using a regexp that 5.004 does not like (but we may find a different solution) But also more and more of the modules we depend on are moving on. The DSML module I am working on uses XML::SAX, which will not work with 5.004 So its getting to the point where we say "we support 5.004, but if you want to do this, that or the other your mileage will vary" Graham. |
|
From: Norbert K. <nor...@da...> - 2002-02-21 13:55:32
|
--On Mittwoch, 20. Februar 2002 22:53 +0100 Stefan Walther=20 <wa...@bl...> wrote: > Dear Experts, > > I'm a relatively new to Perl and Perl-LDAP, so thanks for your help. > > I am using PERL-LDAP a Novell/NT directory, and everything works > fine exept the GUID I need to use; I only get things like = S=C3?H=C3?TT=C3?=11=C2=AF2 > returned but I cannot manage to use Convert::ASN1 The GUID attribute's syntax is octet string. So it will probably contain=20 binary data for which no human-readable string encoding exists.=20 (http://developer.novell.com/ndk/doc/ndslib/schm_enu/data/sdk1198.html) --=20 Norbert Klasen, Dipl.-Inform. DAASI International GmbH phone: +49 7071 29 70336 Wilhelmstr. 106 fax: +49 7071 29 5114 72074 T=FCbingen email: nor...@da... Germany web: http://www.daasi.de |
|
From: ¿©Çà°¡ÀÚ<te...@te...> - 2002-02-21 10:42:57
|
<html> <head> <meta http-equiv="content-type" content="text/html; charset=euc-kr"> <title>여행가자 오픈 기념으로 회원 가입시 [태국,필리핀,사이판] 무료 해외 여행권을 드립니다.</title> <meta name="generator" content="Namo WebEditor v5.0"> </head> <body bgcolor="white" text="black" link="blue" vlink="purple" alink="red"> <table align="center" cellpadding="0" cellspacing="0" width="600"> <tr> <td width="974"> <p align="center"><img src="http://my.dreamwiz.com/merzone/6.jpg" width="600" height="152" border="0" usemap="#ImageMap1"></p> </td> </tr> <tr> <td width="974"> <p align="center"><a href="http://www.honeymoonbest.com" target="_blank"><img src="http://my.dreamwiz.com/merzone/7.jpg" width="600" height="170" border="0"></a></p> </td> </tr> <tr> <td width="974" height="255"> <p align="center"><a href="http://www.honeymoonbest.com" target="_blank"><img src="http://my.dreamwiz.com/merzone/3.jpg" width="600" height="254" border="0"></a></p> </td> </tr> <tr> <td width="974"> <p align="center"><a href="http://www.honeymoonbest.com" target="_blank"><img src="http://my.dreamwiz.com/merzone/4.jpg" width="600" height="221" border="0"></a></p> </td> </tr> <tr> <td width="974"> <p align="center"><img src="http://my.dreamwiz.com/merzone/5.jpg" width="600" height="83" border="0"></p> </td> </tr> <tr> <td width="974"> <p align="center"><span style="FONT-SIZE: 9pt" ><br></span><span style="FONT-SIZE: 10pt"><b><font color="blue">여행가자 오픈 기념으로 회원 가입시 [태국,필리핀,사이판] 무료 해외 여행권을 드립니다.<br>기간 : 2002년 2월18일 ~ 4월 30일 까지<br>대상 : 여행가자 신규회원 가입자 전원증정 [항공권별도]</font></b></span><span style="FONT-SIZE: 9pt" ><br></span><span style="FONT-SIZE: 12pt"><b><a href="http://www.honeymoonbest.com" target="_blank"> 여행가자 홈페이지 바로가기</a><br> </b></span></p> </td> </tr> <tr> <td width="974"> <p> <span style="FONT-SIZE: 10pt" ><b>귀하의 승락없이 홍보성 전자 우편을 보내게 된 점 정중히 사과 드립니다.<BR>정보통신망이용촉진법 규정을 준수하여 광고메일임을 표시하였으며, 수신거부 장치를 마련하고 있습니다.<BR>귀하의 전자 우편 주소는 인터넷 상의 공개된 장소에서 습득하였으며, 저희는 귀하의 전자우편 주소 외 어떠한 개인정보도 가지고 있지 않으므로 안심하시기 바랍니다. 수신을 원치 않으시면 </b></span><A href="mailto:go...@ha..."><span style="FONT-SIZE: 10pt" ><b><IMG align=absMiddle border=0 height=21 src="http://my.dreamwiz.com/merzone/Btn_opt_out.gif" width=57></b></span></A><span style="FONT-SIZE: 10pt" ><b> 를 클릭해 주십시요. </b></span></p> </td> </tr> <tr> <td width="974"> <p> </p> </td> </tr> </table> <map name="ImageMap1"> <area shape="RECT" coords="346,27,570,60" href ="http://www.honeymoonbest.com" target="_blank"> </map> </body> </html> |
|
From: Chris R. <chr...@me...> - 2002-02-21 09:23:28
|
Stefan Walther <wa...@bl...> wrote: > Dear Experts, > =20 > I'm a relatively new to Perl and Perl-LDAP, so thanks for your help. > =20 > I am using PERL-LDAP a Novell/NT directory, and everything works > fine exept the GUID I need to use; I only get things like = S=C3=8DH=C3=99TT=C3=94?=C2=AF2 > returned but I cannot manage to use Convert::ASN1 > =20 > I have nearly tried everything (I am able to think about ;-)) > =20 > Thanks for your help > =20 > Greetings > =20 > Stefan The GUID attribute (a proprietary Novell attribute) appears to be defined as a 16 octet long octet string, according to the NDS online documentation. The structure of the value isn't obviously described by Novell online. I would be surprised if the syntax was described by ASN.1; I would guess that it is a simple packed array of bytes and words instead - see perl's unpack() function. Cheers, Chris |
|
From: Chris R. <chr...@me...> - 2002-02-21 08:40:21
|
Graham Barr <gb...@po...> wrote: > I think it is time that we stopped holding ourselves back and drop > support for running Net::LDAP under perl5.004 > > So unless someone speaks up with a very compelling argument, the > next release of perl-ldap will require at least perl5.005_03 > > Graham. > What are the differences between these 2 versions, and how do they affect Net::LDAP? Cheers, Chris |
|
From: Stefan W. <wa...@bl...> - 2002-02-20 21:55:14
|
RGVhciBFeHBlcnRzLA0KIA0KSSdtIGEgcmVsYXRpdmVseSBuZXcgdG8gUGVybCBhbmQgUGVybC1M REFQLCBzbyB0aGFua3MgZm9yIHlvdXIgaGVscC4NCiANCkkgYW0gdXNpbmcgUEVSTC1MREFQIGEg Tm92ZWxsL05UIGRpcmVjdG9yeSwgYW5kIGV2ZXJ5dGhpbmcgd29ya3MNCmZpbmUgZXhlcHQgdGhl IEdVSUQgSSBuZWVkIHRvIHVzZTsgSSBvbmx5IGdldCB0aGluZ3MgbGlrZSBTw41Iw5lUVMOUEcKv Mg0KcmV0dXJuZWQgYnV0IEkgY2Fubm90IG1hbmFnZSB0byB1c2UgQ29udmVydDo6QVNOMQ0KIA0K SSBoYXZlIG5lYXJseSB0cmllZCBldmVyeXRoaW5nIChJIGFtIGFibGUgdG8gdGhpbmsgYWJvdXQg Oy0pKQ0KIA0KVGhhbmtzIGZvciB5b3VyIGhlbHANCiANCkdyZWV0aW5ncw0KIA0KU3RlZmFuDQo= |
|
From: Graham B. <gb...@po...> - 2002-02-18 15:22:34
|
On Mon, Feb 18, 2002 at 12:44:24PM +0100, Norbert Klasen wrote: > http://www.daasi.de/staff/norbert/thesis/ Nice work. I especially like the PerLDAP / perl-ldap comparison :) Graham. |
|
From: Norbert K. <nor...@da...> - 2002-02-18 12:00:16
|
--On Montag, 18. Februar 2002 09:19 +0000 Carsten Cramer=20 <Car...@lr...> wrote: > Does anybody Know how to configure LDAP on a W2K Domain controller to > make ldap binds through net::ldap possible? You need to bind first before you can search AD, because by default=20 anonymous has no read permissions on the AD. > I tried the 'searchldap' client from the iPlanet SDK as well, who runs in > a verbose mode and returns error messages quit well. Which error messages do you get? > It seems to me that by default: > - simple bind is not supported (even if the ldap call is from an domain > integrated w2k-client. (kerberos authentication is wanted) > - hosts, which are not w2k domain enabled, are refused Simple bind is enabled by default. You neet the right DN though. Try=20 reading the namingContext attribute from the rootDSE (ldapsearch -h=20 ldap.example.com -s base -b "" objectclass=3D*). Your DN will probably be=20 something like "cn=3DCarsten Cramer, ou=3Dusers, dc=3Dlrz-muenchen, = dc=3Dde". For further information on SASL/GSSAPI/Krb5 see=20 http://www.daasi.de/staff/norbert/thesis/ > I couldn'd find any detailed LDAP logging option on the w2k Server, which > might be helpfull. Configuring LDAP on W2k is like fishing in muddy > whater... There exists a knowlegdebase article which describes a registry setting to=20 enable ldap logging. This does not provide very detailed information=20 though. The best way to see what happens is to run NETMON on the W2k = server. --=20 Norbert Klasen, Dipl.-Inform. DAASI International GmbH phone: +49 7071 29 70336 Wilhelmstr. 106 fax: +49 7071 29 5114 72074 T=FCbingen email: nor...@da... Germany web: http://www.daasi.de |
|
From: Carsten C. <Car...@lr...> - 2002-02-18 09:19:36
|
Does anybody Know how to configure LDAP on a W2K Domain controller to make ldap binds through net::ldap possible? I tried the 'searchldap' client from the iPlanet SDK as well, who runs in a verbose mode and returns error messages quit well. It seems to me that by default: - simple bind is not supported (even if the ldap call is from an domain integrated w2k-client. (kerberos authentication is wanted) - hosts, which are not w2k domain enabled, are refused I couldn'd find any detailed LDAP logging option on the w2k Server, which might be helpfull. Configuring LDAP on W2k is like fishing in muddy whater... Cheers -- +---------------------------------------------------------------+ | Dipl.Ing.(FH)Carsten Cramer | Leibniz Computing Centre of the | | CNE | Bavarian Academy of Sciences | | Tel. +49 +89 289 28790 | Barer Strasse 21 | | Fax. +49 +89 2809460 | 80333 Muenchen | | Mail cr...@lr... | Germany | +---------------------------------------------------------------+ |
|
From: <ric...@ao...> - 2002-02-15 17:30:15
|
<html> <head> <title>Untitled Document</title> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> </head> <body bgcolor="#FFFFFF" text="#000000"> <font face="Arial, Helvetica, sans-serif" size="2"> I noticed your email address on a physician list serve related to growing your practice. With your permission, we would like to send you information regarding new approaches to improving and/or growing your patient base, business tips for private practice physicians, and workshops and events for healthcare practitioners. To opt-in to our monthly e-newsletter and events calendar <a href="http://195.235.97.200/personal5/promote14/pb/">click here</a>.<br> <br> Sincerely, </font> <p><font face="Arial, Helvetica, sans-serif" size="2">Victor Black<br> Practice Growth Consultant<br> </font></p> </body> </html> |
|
From: Bergeron, J. <jar...@op...> - 2002-02-13 21:40:13
|
This worked great...thanks! Also thanks to all for all the different solutions given Regards, ------------------------------------------ Jared -----Original Message----- From: Chris Covell [mailto:ch...@ka...] Sent: Wednesday, February 13, 2002 12:46 PM To: PERL-LDAP List Subject: Fwd: Ldap without the module? Hello there, I had the same problem with my IPS, i.e. they would not let me install the perl ldap module on the web server. So what I did was to copy each of the module files to a part of my user space and then added the following lines to each of my perl scripts: use lib qw(local_perl_dir/lib/perl5/ local_perl_dir/lib/perl5/site_perl/5.005/); This tells perl to also look for the libraries locally. Hope this helps you. Chris... ---------- Forwarded Message ---------- Subject: Ldap without the module? Date: Wed, 13 Feb 2002 07:22:11 -0800 From: "Bergeron, Jared" <jar...@op...> To: per...@li... Anyone here know how to use ldap on a box that doesn't have the LDAP module? Is there a way to do it right from Perl? Office politics wont allow installing of modules on this box :( Thanks -Jared ------------------------------------------------------- |
|
From: Chris C. <ch...@ka...> - 2002-02-13 20:47:07
|
Hello there, I had the same problem with my IPS, i.e. they would not let me install the perl ldap module on the web server. So what I did was to copy each of the module files to a part of my user space and then added the following lines to each of my perl scripts: use lib qw(local_perl_dir/lib/perl5/ local_perl_dir/lib/perl5/site_perl/5.005/); This tells perl to also look for the libraries locally. Hope this helps you. Chris... ---------- Forwarded Message ---------- Subject: Ldap without the module? Date: Wed, 13 Feb 2002 07:22:11 -0800 From: "Bergeron, Jared" <jar...@op...> To: per...@li... Anyone here know how to use ldap on a box that doesn't have the LDAP module? Is there a way to do it right from Perl? Office politics wont allow installing of modules on this box :( Thanks -Jared ------------------------------------------------------- |
|
From: Jim H. <ha...@us...> - 2002-02-13 18:15:12
|
On Wed, 13 Feb 2002, Chris Fedde wrote: > I'm guessing that your code is not changing the attribute value if one > already exists. You typicly have to "replace" a value if it exists and > "add" it if it does not. replace will also add if nothing is there |
|
From: Herb K. <her...@ho...> - 2002-02-13 18:03:29
|
I seem to recall that you can install private modules in perl, ie not change the system @INC but still have access to modules stored in a private module hierarchy? Otherwise the make test part of installing a module wouldn't work. --h |
|
From: Chris F. <cf...@vi...> - 2002-02-13 17:44:47
|
On Wed, 13 Feb 2002 10:42:20 -0600 Al Lilianstrom wrote: +------------------ | I am trying to set | | accountExpires 1.2.840.113556.1.4.159 | | The syntax is Integer8 | | Where did these numbers came from? 1016085600 is the number of seconds | from the epoch for the date of March 14, 2003. If I set an account in AD | for a expiration date of March 14, 2003 and then dump the account to | ldif the value of accountExpires is 126606456000000000. | | Now the strange part - I just added a user with the 1016085600 value and | the expiration date was set properly. I'm real confused now. +------------------ IIRC Integer8 is a 8 octet integer with the range -2^63 to 2^63-1. The value you report is in that range. I'm guessing that something broke and stuffed an imposible value into the accountExpires attribute on that entry. The second entry apparently did not have the attribute set so it took yours. I'm guessing that your code is not changing the attribute value if one already exists. You typicly have to "replace" a value if it exists and "add" it if it does not. -- |
|
From: Al L. <al....@fn...> - 2002-02-13 16:42:21
|
Chris Fedde wrote: > > On Wed, 13 Feb 2002 10:12:19 -0600 Al Lilianstrom wrote: > +------------------ > | Chris Winters wrote: > | > > | > From: > | > > | > my $time_sec = get_epoch_seconds(); > | > my ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) > | > = localtime( $time_sec ); > | > > | > To: > | > > | > use Time::Local; > | > my $time_sec = timelocal($sec,$min,$hours,$mday,$mon,$year); > | > | Chris, > | > | Thanks for the snippets - a little simpler than I was using. The problem > | is that perl will output 1016085600 for the date of march 14th, 2003. > | The value AD is looking for is 126606456000000000 for that same date. > | It's this large integer part that had me confused. > +------------------ > > This is confusing. Your initial spec says "number of seconds elapsed > since 00:00:00, January 1, 1970". But your example 126606456000000000 is > much much too large. What is the name and OID of the attribute that you > are trying to set? I am trying to set accountExpires 1.2.840.113556.1.4.159 The syntax is Integer8 Where did these numbers came from? 1016085600 is the number of seconds from the epoch for the date of March 14, 2003. If I set an account in AD for a expiration date of March 14, 2003 and then dump the account to ldif the value of accountExpires is 126606456000000000. Now the strange part - I just added a user with the 1016085600 value and the expiration date was set properly. I'm real confused now. al -- Al Lilianstrom CD/OSS/CSI Al....@fn... |
|
From: Chris R. <chr...@me...> - 2002-02-13 16:33:03
|
Jim Harle <ha...@us...> wrote: > The LDAP protocol doesn't know anything about large integers. I stronly > suspect that what you get back from perl's time() + other manipulations is > exactly what you want. In Novell-land, the equivalent looks like > 20011106120000Z. > --Jim Harle The syntax used by the attribute Jim describes is called GeneralizedTime; RFC 2256 refers you to X.680 for the formal definition of this type. If you break down time into different variables (years, months, etc) then it is pretty easy to construct a GeneralizedTime value. According to X.680 the three formats of GeneralizedTime are: yyyymmddHHMMSS[.s] or: yyyymmddHHMMSS[.s]Z or: yyyymmddHHMMSS[.s][+|-nnnn] where: [...] means optional s is fractional seconds (expire those accounts on the millisecond :-) nnnn is a timezone offset Z is a literal Z and you can probably guess the others. I'm not sure that's the same syntax that Al's accountExpires is using. > On Wed, 13 Feb 2002, Al Lilianstrom wrote: > >> I'm working with Active Directory manipulation from a Unix machine. >> We're going to have a centralized Oracle database feed my code to create >> accounts in AD. One of the items we want to set is the accountExpires >> field - esp for contractors. According to the schema this value is >> stored as a large integer that represents the number of seconds elapsed >> since 00:00:00, January 1, 1970. Cheers, Chris |
|
From: Chris F. <cf...@vi...> - 2002-02-13 16:28:30
|
On Wed, 13 Feb 2002 10:12:19 -0600 Al Lilianstrom wrote: +------------------ | Chris Winters wrote: | > | > From: | > | > my $time_sec = get_epoch_seconds(); | > my ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) | > = localtime( $time_sec ); | > | > To: | > | > use Time::Local; | > my $time_sec = timelocal($sec,$min,$hours,$mday,$mon,$year); | | Chris, | | Thanks for the snippets - a little simpler than I was using. The problem | is that perl will output 1016085600 for the date of march 14th, 2003. | The value AD is looking for is 126606456000000000 for that same date. | It's this large integer part that had me confused. +------------------ This is confusing. Your initial spec says "number of seconds elapsed since 00:00:00, January 1, 1970". But your example 126606456000000000 is much much too large. What is the name and OID of the attribute that you are trying to set? -- |
|
From: Al L. <al....@fn...> - 2002-02-13 16:12:21
|
Chris Winters wrote: > > On Wed, 2002-02-13 at 10:40, Al Lilianstrom wrote: > > I'm working with Active Directory manipulation from a Unix machine. > > We're going to have a centralized Oracle database feed my code to create > > accounts in AD. One of the items we want to set is the accountExpires > > field - esp for contractors. According to the schema this value is > > stored as a large integer that represents the number of seconds elapsed > > since 00:00:00, January 1, 1970. > > > > It's real easy to get the number of seconds since Jan 1, 1970. But I'm > > unsure what this large integer format is and how to convert to it. > > This is a common unix way to identify time. Jan 1, 1970 is known as the > epoch. Being of a unix heritage, Perl can translate to and from epoch > seconds easily: > > From: > > my $time_sec = get_epoch_seconds(); > my ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) > = localtime( $time_sec ); > > To: > > use Time::Local; > my $time_sec = timelocal($sec,$min,$hours,$mday,$mon,$year); > > Note that $mon is a 0 offset value (0..11) in both cases. The $year > value returned from localtime() needs 1900 added to it to be a > human-readable value (e.g., this year localtime returns 102: 102 + 1900 > = 2002). The timelocal() function is a little more flexible and can take > either a 1900-offset value or a four-digit year. > > localtime() is a built-in function (see 'perldoc -f localtime') and > Time::Local is distributed with all modern (5.6+) versions of Perl. > > I recently had to answer this for some of my win32 colleagues, so this > is very much in the front of my mind :-) Chris, Thanks for the snippets - a little simpler than I was using. The problem is that perl will output 1016085600 for the date of march 14th, 2003. The value AD is looking for is 126606456000000000 for that same date. It's this large integer part that had me confused. al -- Al Lilianstrom CD/OSS/CSI Al....@fn... |
|
From: Jim H. <ha...@us...> - 2002-02-13 16:10:48
|
The LDAP protocol doesn't know anything about large integers. I stronly suspect that what you get back from perl's time() + other manipulations is exactly what you want. In Novell-land, the equivalent looks like 20011106120000Z. --Jim Harle On Wed, 13 Feb 2002, Al Lilianstrom wrote: > I'm working with Active Directory manipulation from a Unix machine. > We're going to have a centralized Oracle database feed my code to create > accounts in AD. One of the items we want to set is the accountExpires > field - esp for contractors. According to the schema this value is > stored as a large integer that represents the number of seconds elapsed > since 00:00:00, January 1, 1970. > > It's real easy to get the number of seconds since Jan 1, 1970. But I'm > unsure what this large integer format is and how to convert to it. > > Any help would be much appreciated. > > tia, al > > Yes - I'm not a real programmer. > > -- > > Al Lilianstrom > CD/OSS/CSI > Al....@fn... > |
|
From: Chris W. <ch...@cw...> - 2002-02-13 15:58:45
|
On Wed, 2002-02-13 at 10:40, Al Lilianstrom wrote:
> I'm working with Active Directory manipulation from a Unix machine.
> We're going to have a centralized Oracle database feed my code to create
> accounts in AD. One of the items we want to set is the accountExpires
> field - esp for contractors. According to the schema this value is
> stored as a large integer that represents the number of seconds elapsed
> since 00:00:00, January 1, 1970.
>
> It's real easy to get the number of seconds since Jan 1, 1970. But I'm
> unsure what this large integer format is and how to convert to it.
This is a common unix way to identify time. Jan 1, 1970 is known as the
epoch. Being of a unix heritage, Perl can translate to and from epoch
seconds easily:
From:
my $time_sec = get_epoch_seconds();
my ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst)
= localtime( $time_sec );
To:
use Time::Local;
my $time_sec = timelocal($sec,$min,$hours,$mday,$mon,$year);
Note that $mon is a 0 offset value (0..11) in both cases. The $year
value returned from localtime() needs 1900 added to it to be a
human-readable value (e.g., this year localtime returns 102: 102 + 1900
= 2002). The timelocal() function is a little more flexible and can take
either a 1900-offset value or a four-digit year.
localtime() is a built-in function (see 'perldoc -f localtime') and
Time::Local is distributed with all modern (5.6+) versions of Perl.
I recently had to answer this for some of my win32 colleagues, so this
is very much in the front of my mind :-)
Chris
--
Chris Winters (ch...@cw...)
Building enterprise-capable snack solutions since 1988.
|
|
From: Al L. <al....@fn...> - 2002-02-13 15:40:17
|
I'm working with Active Directory manipulation from a Unix machine. We're going to have a centralized Oracle database feed my code to create accounts in AD. One of the items we want to set is the accountExpires field - esp for contractors. According to the schema this value is stored as a large integer that represents the number of seconds elapsed since 00:00:00, January 1, 1970. It's real easy to get the number of seconds since Jan 1, 1970. But I'm unsure what this large integer format is and how to convert to it. Any help would be much appreciated. tia, al Yes - I'm not a real programmer. -- Al Lilianstrom CD/OSS/CSI Al....@fn... |
7902 messages has been excluded from this view by a project administrator.
![http://my.dreamwiz.com/merzone/6.jpg"](http://my.dreamwiz.com/merzone/6.jpg"){kind=link}
![http://my.dreamwiz.com/merzone/7.jpg"](http://my.dreamwiz.com/merzone/7.jpg"){kind=link}
![http://my.dreamwiz.com/merzone/3.jpg"](http://my.dreamwiz.com/merzone/3.jpg"){kind=link}
![http://my.dreamwiz.com/merzone/4.jpg"](http://my.dreamwiz.com/merzone/4.jpg"){kind=link}
![http://my.dreamwiz.com/merzone/5.jpg"](http://my.dreamwiz.com/merzone/5.jpg"){kind=link}
![http://my.dreamwiz.com/merzone/Btn_opt_out.gif"](http://my.dreamwiz.com/merzone/Btn_opt_out.gif"){kind=link}