osdir.com
mailing list archive F.A.Q. -since 2001!

Subject: تصوير من
داخل
غرفة
غيار
ملابس
حريم +
صور سكس
مثيرة
عربية
نادرة و
أسخن
أفلام
سكس
لأجنبي
حمل سكس
لفترة
محدودة
تحميل
سكس
مجانا - msg#05030

List: general

View MaxCDN's pricing and plans [OSDir Endorsed!]
Web Hosting with cPanel - only $1 / month from GoDaddy
Virtual Dedicated Hosting [OSDir Endorsed!] Professional VPNs [OSDir Endorsed!]

general Navigation:
Date: Prev Next Date Index Thread: Prev Next Thread Index

Website Speed Performance Monitoring

تصوير من داخل غرفة غيار ملابس حريم + صور سكس مثيرة عربية نادرة و أسخن أفلام سكس لأجنبي حمل سكس لفترة محدودة تحميل سكس مجانا

http://bit.ly/hrqVUm

 

 

wacth sex now video hot girls fucken hard sexy girls fuck hot suck ++18

http://bit.ly/ecCX7S

--
You received this message because you are subscribed to the Google Groups "Model Town Real Estate Agent" group.
To post to this group, send email to model-town-real-estate-agent@xxxxxxxxxxxxxxxxx
To unsubscribe from this group, send email to model-town-real-estate-agent+unsubscribe@xxxxxxxxxxxxxxxxx
For more options, visit this group at http://groups.google.com/group/model-town-real-estate-agent?hl=en.

Find out more about MaxCDN [OSDir Endorsed!]
Virtual Dedicated Hosting [OSDir Endorsed!]
Professional VPNs Protect your privacy! [OSDir Endorsed!]

Thread at a glance:

Previous Message by Date:

Re: LPeg support for utf-8

On 04/07/2011 03:15 PM, E. Toernig wrote: A quick survey, for those who care: - should LPeg support utf-8? - If so, what would that mean? I think it would help (not only LPeg) to add unicode escape sequences (\uXXXX) to Lua's strings. Ciao, ET. Lua itself does not have Unicode support. So, if you're suggesting that this would merely generate the proper UTF-8 bytes for the character...hmm, that's actually a pretty good idea. -- Regards, Matthew Frazier

Next Message by Date:

Re: Windows 7 clients MOSXS 10.6.6 SMB

On Apr 5, 2011, at 10:15 AM, Mike Reed wrote: > On Apr 5, 2011, at 8:46 AM, Andrew Tomlinson wrote: > >> >> On Apr 3, 2011, at 11:22 PM, Mike Reed wrote: >> >>> On Apr 3, 2011, at 9:07 PM, Elijah Buck wrote: >>> >>>> You said, "it's likely that AD registered the SPN's as server.ad.foo.com", >>>> which I think I'm saying still think might be the case. Though perhaps the >>>> cifs/whs4.students.bcps.k12.md.us@xxxxxxxxxxxxxxxxxxxxxxx ticket is >>>> evidence to the contrary. >>> >>> Yep. Servername whs4, AD (and DNS) domain students.bcps.k12.md.us - so >>> it's right. Had it been whs4.bcps.k12.md.us in DNS and >>> whs4.students.bcps.k12.md.us, then we'd have the problem you were looking >>> for, and comparing the keytab to the SPN's is the correct route. The early >>> clue here is that WinXP works with Kerberos and gets tickets. >> >> Ah, but there's the rub. Kerbtray did not show tickets for the OSX server in >> WinXP, so I don't see Kerberos working properly there. WinXP must be >> allowing some authentication that Windows 7 refuses (it could be in a local >> Group Policy ITD put on the client image). > > Interesting. I thought you had tickets. See your next question below for my > answer... > >> And looking into it more, I'm gathering I've got a disjoint namespace issue. >> We have 2 domains in the bcps.k12.md.us forest: one for students (STUDENTS) >> and one for staff (ADMIN). The MOSX Server is whs4.students.bcps.k12.md.us, >> joined to STUDENTS domain in forest bcps.12.md.us. > > So far that's not disjointed, that's just multi domain. As long as the DNS > FQHN matches the AD namespace (i.e. server.students.bcps.k12.md.us is the DNS > name and the AD namespace name). Disjointed is strictly when the DNS domain > doesn't reflect the correct Kerberos/AD domain (each AD domain is a Kerberos > REALM) in a 1:1 mapping, i.e. servers named server.bcps.k12.md.us when > they're actually in the AD domain "students", etc. > >> On a WinXP client joined to ADMIN domain, student and staff accounts can >> both log on. However, logons to neither STUDENTS domain nor ADMIN domain get >> CIFS tickets to whs4 server, though they can connect with appropriate >> privileges, so I guess some other authentication scheme is being used. > > Yes. Likely, based on your earlier information, NTLM authentication. I'd > bet that if you set the server to Kerberos only those workstations would > fail. It's definitely worth looking at why Kerberos isn't working... > especially if you want/need it to for Win7 machines (i.e. not falling back to > NTLM and using older security, etc.). > >> On a WinXP client joined to STUDENTS domain, students can log onto STUDENTS >> domain and get CIFS tickets from whs4 server. Staff can log on to ADMIN >> domain on same client and get CIFS tickets to whs4 server. > > That's rather queer. Interesting to know that Kerberos works in the same > domain (and that Kerberos works, period). That might point at some other > access restriction that's in place. The geek in me would love to see a > packet trace of someone bound to ADMIN requesting a ticket from a server in > STUDENTS. I'd love to know if it can't find a KDC to get a TGT, or if it's > getting/asking for bad SPN's in the other domain/realm, but I digress... > >> So, is there a way to enable Kerberos cross-domain like this? Everything's >> on the same physical network, and it seems that user accounts can be in >> either domain and have Kerberos work fine to the OSX server. It's just that >> the machines seem to prevent Kerberos from working with the OSX Server if >> they are joined to a different domain in the same forest. > > Cross-DOMAIN should work fine in the same forest. If they're separate > forests (which, based on your description of machines bound to STUDENTS and > folks with accounts in ADMIN working, it's not), it wouldn't work without > third party software. Just FYI, this is something that should be able to be > troubleshot in 2-3 days of work (likely just one, but two to be safe). Also, > to be clear, my company can't do this work (we don't work with .EDU > customers), but there are others here and available via ACN who can and do, > should you need/want that. Not that you asked, but I could see it coming up. > >> Mike, Elijah, John-I am so grateful for the help you've given me! Thank you >> for taking the time and offering your expertise. > > I love this stuff. So, here's what I'd do. Join a MAC to the ADMIN domain > and log in with an ADMIN user. Bind it to admin.bcps.k12.md.us. Try to > mount a share on whs4 (in the students domain). See what happens and if > you're prompted for credentials, and if they work. Use Keychain Assistant to > look at Kerberos Tickets (Kerberos Ticket Viewer). > > Repeat with a STUDENTS user (on the Mac bound to Admin). > > Now unbind, bind to STUDENTS, and repeat with a user from ADMIN and STUDENTS. > > For the ones that fail, get a packet trace (Wireshark) and filter it for > Kerberos (the simple filter is "KERBEROS", no quotes). Read through and see > if the AS sequence is working. It should give some informative errors. If > that works, then we'll look at the TGS sequence. Same deals. > > For more information on Kerberos, see > <http://technet.microsoft.com/en-us/library/bb742516.aspx>. > > -- Mike Basic test results: 1. On a Mac joined to ADMIN domain, an ADMIN user logs in. On connecting to whs4 via SMB, it prompts for credentials. These work only if the domain is specified ("ADMIN\username"). Nothing in Kerberos Ticket Viewer at all. 2. On a Mac joined to ADMIN domain, a STUDENTS user logs in and is automatically connected via AFP to whs4 (Home is set in AD to a share on whs4, AD plugin on client set to use home path from AD and afp). Nothing shows in Ticket Viewer. Connecting to whs4 via SMB gets credentials prompt; username and pw work, and a Ticket Viewer adds an "LDKC username@whs4" ticket. 3. On a Mac joined to STUDENTS domain, an ADMIN user logs in. On connecting to whs4 via SMB, behavior is exactly as when same user logs into Mac joined to ADMIN domain. 4. On a Mac joined to STUDENTS domain, a STUDENTS user logs in and behavior is exactly as when same user logs onto Mac joined to the ADMIN domain. I've read a lot, including the very helpful link you provided, but there's way more information in the packet traces than I can grasp. I see the following interesting things, though (doing my best to make sense of what's over my head): Pretty much everything sent from the client (AS-REQ and TGS-REQ) reports a bad header checksum in the UDP packet: Header checksum: 0x0000 [incorrect, should be 0xf7cd] [Good: False] [Bad: True] [Expert Info (Error/Checksum): Bad checksum] [Message: Bad checksum] [Severity level: Error] [Group: Checksum] The responses seem polite enough: Kerberos AS-REP Pvno: 5 MSG Type: AS-REP (11) Client Realm: STUDENTS.BCPS.K12.MD.US Client Name (Principal): 96174 Name-type: Principal (1) Name: 96174 Ticket Tkt-vno: 5 Realm: STUDENTS.BCPS.K12.MD.US Server Name (Unknown): krbtgt/STUDENTS.BCPS.K12.MD.US Name-type: Unknown (0) Name: krbtgt Name: STUDENTS.BCPS.K12.MD.US In case #3 above, it looks like a nice afs ticket is issued to mount the Home as configured in AD: Kerberos TGS-REP Pvno: 5 MSG Type: TGS-REP (13) Client Realm: STUDENTS.BCPS.K12.MD.US Client Name (Principal): 96174 Name-type: Principal (1) Name: 96174 Ticket Tkt-vno: 5 Realm: STUDENTS.BCPS.K12.MD.US Server Name (Principal): afpserver/whs4.students.bcps.k12.md.us Name-type: Principal (1) Name: afpserver Name: whs4.students.bcps.k12.md.us In case #1 above, on the attempt to connect via SMB to whs4 (gets a credentials prompt), here is the AS-REQ: Kerberos AS-REQ Pvno: 5 MSG Type: AS-REQ (10) KDC_REQ_BODY Padding: 0 KDCOptions: 50800010 (Forwardable, Proxiable, Renewable, Renewable OK) Client Name (Principal): atomlinson Name-type: Principal (1) Name: atomlinson Realm: STUDENTS.BCPS.K12.MD.US Server Name (Unknown): krbtgt/STUDENTS.BCPS.K12.MD.US Name-type: Unknown (0) Name: krbtgt Name: STUDENTS.BCPS.K12.MD.US Realm: STUDENTS.BCPS.K12.MD.US Server Name (Unknown): krbtgt/STUDENTS.BCPS.K12.MD.US Name-type: Unknown (0) Name: krbtgt Name: STUDENTS.BCPS.K12.MD.US from: 2011-04-06 19:14:42 (UTC) till: 2011-04-07 05:14:42 (UTC) Nonce: 1739435838 Encryption Types: aes256-cts-hmac-sha1-96 aes128-cts-hmac-sha1-96 des3-cbc-sha1 rc4-hmac des-cbc-crc des-cbc-md5 des-cbc-md4 This generates the following error: Kerberos KRB-ERROR Pvno: 5 MSG Type: KRB-ERROR (30) stime: 2011-04-06 19:14:42 (UTC) susec: 627325 error_code: KRB5KDC_ERR_C_PRINCIPAL_UNKNOWN (6) Realm: STUDENTS.BCPS.K12.MD.US Server Name (Unknown): krbtgt/STUDENTS.BCPS.K12.MD.US Name-type: Unknown (0) Name: krbtgt Name: STUDENTS.BCPS.K12.MD.US When the credentials are submitted as "bcpss\atomlinson": Kerberos AS-REQ Pvno: 5 MSG Type: AS-REQ (10) KDC_REQ_BODY Padding: 0 KDCOptions: 50800010 (Forwardable, Proxiable, Renewable, Renewable OK) Client Name (Principal): bcpssatomlinson Name-type: Principal (1) Name: bcpssatomlinson Realm: STUDENTS.BCPS.K12.MD.US Server Name (Unknown): krbtgt/STUDENTS.BCPS.K12.MD.US Name-type: Unknown (0) Name: krbtgt Name: STUDENTS.BCPS.K12.MD.US from: 2011-04-06 19:15:07 (UTC) till: 2011-04-07 05:15:07 (UTC) Nonce: 1933414976 Encryption Types: aes256-cts-hmac-sha1-96 aes128-cts-hmac-sha1-96 des3-cbc-sha1 rc4-hmac des-cbc-crc des-cbc-md5 des-cbc-md4 Kerberos errs again. . . Kerberos KRB-ERROR Pvno: 5 MSG Type: KRB-ERROR (30) stime: 2011-04-06 19:15:07 (UTC) susec: 799510 error_code: KRB5KDC_ERR_C_PRINCIPAL_UNKNOWN (6) Realm: STUDENTS.BCPS.K12.MD.US Server Name (Unknown): krbtgt/STUDENTS.BCPS.K12.MD.US Name-type: Unknown (0) Name: krbtgt Name: STUDENTS.BCPS.K12.MD.US . . . but authentication proceeds via NTLM, with an SMB "Session Setup AndX Request, NTLMSSP_AUTH, User: BCPSS\atomlinson", followed by an SMB response with "NT Status: STATUS_SUCCESS". The share mounts. _______________________________________________ Do not post admin requests to the list. They will be ignored. Macos-x-server mailing list (Macos-x-server@xxxxxxxxxxxxxxx) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/macos-x-server/maillists%40codeha.us This email sent to maillists@xxxxxxxxx

Previous Message by Thread:

[lang] @inheritDoc

Hi, just a reminder. Such a javadoc comment for a method is completely superfluous: ============ %< ============= /** * {@inheritDoc} */ ============ %< ============= This is what the javadoc nowadays does by default ... - JÃrg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxxx For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxx

Next Message by Thread:

Home | News | Sitemap | FAQ | advertise | OSDir is an Inevitable website. GBiz is too!