DOCSLIB.ORG

From OS/2 to Windows to Samba a Journey to Open Source

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
From OS/2 to Windows to Samba a Journey to Open Source IBM Global Services From OS/2 to Windows to Samba A Journey to Open Source John Janosik – [email protected] Bill Marshall - [email protected] samba eXPerience 2005 May 4, 2005 © 2005 IBM Corporation IBM Global Services Agenda Environment Simple file server migration Complex file server migration with Posix ACLs OS/2 to NT Domain migration NT to Samba Domain migration Conclusion samba eXPerience 2005 May 4, 2005 © 2005 IBM Corporation IBM Global Services Environment – March 2002 Seriously started looking for a migration option away from OS/2 4 terabytes of data on 50 servers OS/2 domain with 6000+ users Mostly Windows NT & 2000 clients – Approximately 4000 Windows clients had joined a NT domain for minimal client management – Users sign on to systems with local accounts Knew OS/2 was end of life, but had been waiting for direction on where to go – Windows clients had been causing problems against OS/2 servers (session setup with vc=0 was using resources) – XP service pack 1 broke more things Throughout 2002 we experimented with Samba servers for IT use samba eXPerience 2005 May 4, 2005 © 2005 IBM Corporation IBM Global Services Theory of Migration – January 2003 Realized there were 3 main problems to solve in order to transparently move users from OS/2 to another platform In no particular order: – Operating system transparency • Samba/Linux looks like Windows, but can it function like OS/2? – Location transparency • Ability to move data from \\server01 to \\bigserver02 without users needing to change anything. – Authentication transparency • For a Windows domain you can “net vampire” • Deliver a new NT account, with the same password, without the user having to know or change anything samba eXPerience 2005 May 4, 2005 © 2005 IBM Corporation IBM Global Services Data Migration Tried many options to move the data from OS/2 to Linux Needed an incremental method – Servers up to 280 GB in size – Boot knoppix CD on the OS/2 server, mount OS/2 HPFS partition and rsync • Found bugs in the HPFS driver – Net use to Samba and push from OS/2 server • OS/2 xcopy does not handle large trees • Windows xcopy moved the data across the network twice – Eventually, used rsync and smbfs • However, there were some problems in smbfs against OS/2 servers • Steve French helped with code changes to work around some problems • Added a windows based perl script to do a tree compare and a final copy File ownership and ACLs were another matter samba eXPerience 2005 May 4, 2005 © 2005 IBM Corporation IBM Global Services File Server Migration All users are able to map through a Samba hosted distributed file system (location transparency) – \\rchfs\home\userid or \\rchfs\group\share Migrations took place during the weekly Friday night outage window When a server was replaced: – Server was renamed and kept online – Once comfortable the data had migrated (a couple weeks), reloaded the system with Linux and reused the hardware Administrators had minimal Linux skills, came from Windows background – Created simple perl client/server code to create Samba shares and set initial ACLs from the Windows command prompt samba eXPerience 2005 May 4, 2005 © 2005 IBM Corporation IBM Global Services Automation of Share Migration OS/2 REXX scripts created: – Linux bash scripts to smbmount OS/2 servers under Linux – Bash scripts to rsync the data from OS/2 to Linux – Cutover scripts to add Netbios aliases to smb.conf, etc. – smb.conf entries for shares During the week, the majority of the data was rsync’d On Friday nights – a final sync of the data was done – Linux/Samba system moved into production At the end or our migrations, “at” jobs on Linux were used to do the migrations automatically samba eXPerience 2005 May 4, 2005 © 2005 IBM Corporation IBM Global Services Simple Server Authorization - smb.conf sample No ACL support in JFS & Red Hat kernels in 2002/2003 Initially, used smb.conf parameters to allow & restrict access If needed, created “fake” groups for all shared project space and used force group to put people into the group [vaj30] comment = Temporary VAJ space path = /home/group/vaj30 writeable = yes ; read list = vaj30 write list = vaj30 force group = vaj30 create mask = 0770 force create mode = 0770 force directory mode = 0770 directory mask = 0770 valid users = @vaj30, root samba eXPerience 2005 May 4, 2005 © 2005 IBM Corporation IBM Global Services Simple File Server Authentication No real domain (winbind) integration against OS/2 – Initially, /etc/passwd & /etc/group built from OS/2 information and used security=server for passwords • security=server unreliable in Samba 2.x, OK in 3.x – Then security=user with smbpasswd built from password hashes dumped every 10 minutes from DC • Later realized this meant we could easily stop using our OS/2 DCs once all the OS/2 servers were converted – Passwords changed via web, added hook to push the hashes to Linux Home directory servers migrated & merged first – Used DNS & Netbios aliases to combine servers First server migrated from OS/2 to Linux/Samba in late January 2003 – No one noticed! samba eXPerience 2005 May 4, 2005 © 2005 IBM Corporation IBM Global Services Complex ACL File Server Migration Some servers did not fit the simple access control scheme Samba & kernel improvements allowed us to continue – Built a kernel w/ JFS to allow ACLs and upgraded Samba OS/2 command file was used to export the ACLs from HPFS Linux Perl script read the output from OS/2 and used setfacl on JFS OS/2 ACLs allowed read, write, execute and delete so they map easily to Posix ACLs samba eXPerience 2005 May 4, 2005 © 2005 IBM Corporation IBM Global Services OS/2 to NT Domain Migration & Authentication Transparency Merge of OS/2 and NT domain – All users created in NT domain in a “big bang” – At first, continued running security=user – Documentation changes told people the OS/2 domain was gone – Next, configured winbind and joined Samba servers to the NT domain – Samba servers with security=domain were modified to fail over to smbpasswd file on bad password • Smbpasswd file was correct • Domain passwords were incorrect until a password change • Still running Samba 2.2.X. – Password changes via web interface • Update NT domain passwords • Pushed updated smbpasswd to all systems with rsync until all systems were in the domain and running winbind samba eXPerience 2005 May 4, 2005 © 2005 IBM Corporation IBM Global Services Alternate OS/2 Domain Migration Options Pushing LM hash into NT SAM – Required changing ACLs on registry entries in the SAM on the domain controller – This option rejected because the gain was minimal for the risk If migration occurred now bypass NT migration – Easy to script creation of ldif of Samba attributes via information dumped from OS/2 domain – We didn’t have experience with Samba domains at the time and the performance issues were not yet solved. samba eXPerience 2005 May 4, 2005 © 2005 IBM Corporation IBM Global Services NT to Samba Domain Migration Research started in April 2004 – Samba 3.0.4 was current at the time LDAP passdb backend was our only option – Had multiple NT DCs – Did not want to give up redundancy – Wanted to learn skills that would apply to customer use of Samba samba eXPerience 2005 May 4, 2005 © 2005 IBM Corporation IBM Global Services Initial Assesment Performance issues with our setup – smbldap tools useradd slowed down as number of users grew – Migrating users/groups via vampire took too long • timed out during the group migration – Some RPCs made by winbind were handled inefficiently by Samba domain controllers We thought about moving away from winbind on the member servers Migration was postponed until the end of 2004 and winbind was retained for supplying posix users/groups on member servers samba eXPerience 2005 May 4, 2005 © 2005 IBM Corporation IBM Global Services Migration Improvements The IDEALX smbldap tools were fixed to store the next uid/gid in LDAP instead of iterating through the users or groups Options to reduce migration time – Vampire to tdb with local posix users/groups, then dump to ldif • Fastest but required patch to pdbedit • Would not work for customers who already had users in ldap and just wanted to add Samba attribtues – Vampire to tdb with LDAP posix users/groups, then use pdbedit to switch backends • Slower but the process can be split up • Once posix users/groups were in place subsequent runs to a new passdb.tdb took less than an hour samba eXPerience 2005 May 4, 2005 © 2005 IBM Corporation IBM Global Services Performance Improvements Iteration of all users/groups was affecting us in the following cases – winbind querying the domain sequence number – winbind querying the members of a group Logs showed 50 seconds spent waiting for LDAP query. – An OpenLDAP developer in IBM provided a patch that improved synchronous LDAP searches from 50 seconds to 3 seconds on our 20,000 account test box Even with openLDAP improvements winbind was still timing out samba eXPerience 2005 May 4, 2005 © 2005 IBM Corporation IBM Global Services Workarounds Stopped winbind from querying domain sequence number – Samba DC is returning current time anyway Created “winbind timeout” smb.conf parameter – Even with these workarounds sometimes the default timeout of 10 seconds was not enough Added new LDAP passdb backend function to directly query LDAP for primary group members – The only large group was domain users which all our users had as their primary group The “winbind cache time” was set to 1 day and the cache was primed offshift
Load more

Recommended publications
  • CIFS/NFS) Administrator's Guide
    Hitachi Data Ingestor File System Protocols (CIFS/NFS) Administrator's Guide Product Version Getting Help Contents MK-90HDI035-13 © 2013- 2015 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd. Hitachi, Ltd., reserves the right to make changes to this document at any time without notice and assume no responsibility for its use. This document contains the most current information available at the time of publication. When new or revised information becomes available, this entire document will be updated and distributed to all registered users. Some of the features described in this document might not be currently available. Refer to the most recent product announcement for information about feature and product availability, or contact Hitachi Data Systems Corporation at https://portal.hds.com. Notice: Hitachi, Ltd., products and services can be ordered only under the terms and conditions of the applicable Hitachi Data Systems Corporation agreements. he use of Hitachi, Ltd., products is governed by the terms of your agreements with Hitachi Data Systems Corporation. Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States and other countries. Archivas, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage, Tagmaserve, Tagmasoft, Tagmasolve, Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform are registered trademarks of Hitachi Data Systems Corporation.
    [Show full text]
  • Samba-3 by Example
    Samba-3 by Example Practical Exercises in Successful Samba Deployment John H. Terpstra May 27, 2009 ABOUT THE COVER ARTWORK The cover artwork of this book continues the freedom theme of the first edition of \Samba-3 by Example". The history of civilization demonstrates the fragile nature of freedom. It can be lost in a moment, and once lost, the cost of recovering liberty can be incredible. The last edition cover featured Alfred the Great who liberated England from the constant assault of Vikings and Norsemen. Events in England that finally liberated the common people came about in small steps, but the result should not be under-estimated. Today, as always, freedom and liberty are seldom appreciated until they are lost. If we can not quantify what is the value of freedom, we shall be little motivated to protect it. Samba-3 by Example Cover Artwork: The British houses of parliament are a symbol of the Westminster system of government. This form of government permits the people to govern themselves at the lowest level, yet it provides for courts of appeal that are designed to protect freedom and to hold back all forces of tyranny. The clock is a pertinent symbol of the importance of time and place. The information technology industry is being challenged by the imposition of new laws, hostile litigation, and the imposition of significant constraint of practice that threatens to remove the freedom to develop and deploy open source software solutions. Samba is a software solution that epitomizes freedom of choice in network interoperability for Microsoft Windows clients.
    [Show full text]
  • Chapter 2: Installing Samba on a Unix System
    ,ch02.26865 Page 31 Friday, November 19, 1999 3:28 PM Chapter 2 2 Installing Samba on a Unix System Now that you know what Samba can do for you and your users, it’s time to get your own network set up. Let’s start with the installation of Samba itself on a Unix system. When dancing the samba, one learns by taking small steps. It’s just the same when installing Samba; we need to teach it step by step. This chapter will help you to start off on the right foot. For illustrative purposes, we will be installing the 2.0.4 version of the Samba server on a Linux* system running version 2.0.31 of the kernel. However, the installation steps are the same for all of the platforms that Samba supports. A typical installa- tion will take about an hour to complete, including downloading the source files and compiling them, setting up the configuration files, and testing the server. Here is an overview of the steps: 1. Download the source or binary files. 2. Read the installation documentation. 3. Configure a makefile. 4. Compile the server code. 5. Install the server files. 6. Create a Samba configuration file. 7. Test the configuration file. 8. Start the Samba daemons. 9. Test the Samba daemons. * If you haven’t heard of Linux yet, then you’re in for a treat. Linux is a freely distributed Unix-like oper- ating system that runs on the Intel x86, Motorola PowerPC, and Sun Sparc platforms. The operating sys- tem is relatively easy to configure, extremely robust, and is gaining in popularity.
    [Show full text]
  • Samba's AD DC: Samba 4.2 and Beyond
    Samba's AD DC: Samba 4.2 and Beyond Presented by Andrew Bartlett of Catalyst // 2014-09 About me ● Andrew Bartlett ● Samba Team member since 2001 ● Working on the AD DC since 2006 ● These views are my own, but I do with to thank: – My employer: Catalyst – My fellow Samba Team members Open Source Technologies Samba's AD DC ● The combination of many years work – File server – Print server – Active Directory Domain controller – (and many other features) ● First Release Dec 2012 ● Now on the road to Samba 4.2 – Due for RC1 on Monday Sep 22 Re-opening the heart of the network ● Samba's AD DC brings open source to the heart of the network again ● Samba has long provided a Domain Controller – But without support for Group Policy and other AD features like Kerberos ● Organizations again have a practical choice other than Microsoft Windows The flexibility to innovate ● Open Source lets you do more ● Just as Samba is in many NAS devices, including NETGEAR's ReadyNAS ● Samba inside Catalyst's print server – No CALs, multi-device access ● Imagine – What if was also an AD DC? – Instant branch office solution – Perhaps managed from the cloud? Breaking vendor lock in ● Samba can migrate to and from Microsoft Windows based AD domains – Without loss of data – Without password resets or domain joins ● Samba 4.0 can upgrade existing Samba 3.x domains to AD – And you can even migrate that to a Microsoft Windows AD if you want to – We won't hold you against your will! Uses Native Microsoft Admin tools ● Microsoft Management Console snap-ins – In general, fully
    [Show full text]
  • Client Side Samba Linux Clients in Microsoft Windows Environments
    Client Side Samba Linux Clients in Microsoft Windows Environments Ralf Haferkamp OpenLDAP Team Lars Müller Samba Team May 8, 2006 Motivation Operating Systems Market Share (Client and Server) 1,80% 2,70% Microsoft Apple Linux 95,50% 2 © Novell Inc, Confidential & Proprietary Mandatory Requirements Overview • Domain join • Single Sign On Authentication • Name Service Switch (NSS) • X11 Display Manager integration (KDM, GDM) 3 © Novell Inc, Confidential & Proprietary Mandatory Requirement Authentication • Seamless PAM Integration – Let PAM winbind behave like other PAM modules – Mapping Microsoft to PAM error messages and codes • Kerberized PAM Winbind – Automatic ticket refresh and renew • Account Policies – Password – Logon hours – Lockout 4 © Novell Inc, Confidential & Proprietary Architecture Overview 5 © Novell Inc, Confidential & Proprietary Supplementary Requirements • Winbind Offline mode • Kerberized Client Applications – web browsers (konqueror, FireFox) – MUA (KMail) • File Access – libsmbclient using apps (konqueror, nautilus) – CIFS system wide? • Printing 6 © Novell Inc, Confidential & Proprietary YaST Integration (1) 7 © Novell Inc, Confidential & Proprietary YaST Integration (2) 8 © Novell Inc, Confidential & Proprietary Samba Winbind AD Integration Demo To do • Acessing CIFS Home Directory • Machine Account Password Changes • Localisation • GUI integration for Services For UNIX (SFU) • Group Policy Support (GPO) • Roaming Profiles • Logon Scripts 10 © Novell Inc, Confidential & Proprietary Available Resources • SUSE Linux Enterprise Desktop 10 • http://openSUSE.org/Samba • Samba.org samba-docs subversion Questions & Answers ? 11 © Novell Inc, Confidential & Proprietary Unpublished Work of Novell, Inc. All Rights Reserved. This work is an unpublished work and contains confidential, proprietary, and trade secret information of Novell, Inc. Access to this work is restricted to Novell employees who have a need to know to perform tasks within the scope of their assignments.
    [Show full text]
  • SMB Analysis
    NAP-3 Microsoft SMB Troubleshooting Rolf Leutert, Leutert NetServices, Switzerland © Leutert NetServices 2013 www.wireshark.ch Server Message Block (SMB) Protokoll SMB History Server Message Block (SMB) is Microsoft's client-server protocol and is most commonly used in networked environments where Windows® operating systems are in place. Invented by IBM in 1983, SMB has become Microsoft’s core protocol for shared services like files, printers etc. Initially SMB was running on top of non routable NetBIOS/NetBEUI API and was designed to work in small to medium size workgroups. 1996 Microsoft renamed SMB to Common Internet File System (CIFS) and added more features like larger file sizes, Windows RPC, the NT domain service and many more. Samba is the open source SMB/CIFS implementation for Unix and Linux systems 2 © Leutert NetServices 2013 www.wireshark.ch Server Message Block (SMB) Protokoll SMB over TCP/UDP/IP SMB over NetBIOS over UDP/TCP SMB / NetBIOS was made routable by running Application over TCP/IP (NBT) using encapsulation over 137/138 139 TCP/UDP-Ports 137–139 .. Port 137 = NetBIOS Name Service (NS) Port 138 = NetBIOS Datagram Service (DGM) Port 139 = NetBIOS Session Service (SS) Data Link Ethernet, WLAN etc. Since Windows 2000, SMB runs, by default, with a thin layer, the NBT's Session Service, on SMB “naked” over TCP top of TCP-Port 445. Application 445 DNS and LLMNR (Link Local Multicast Name . Resolution) is used for name resolution. Port 445 = Microsoft Directory Services (DS) SMB File Sharing, Windows Shares, Data Link Ethernet, WLAN etc. Printer Sharing, Active Directory 3 © Leutert NetServices 2013 www.wireshark.ch Server Message Block (SMB) Protokoll NetBIOS / SMB History NetBIOS Name Service (UDP Port 137) Application • Using NetBIOS names for clients and services.
    [Show full text]
  • View the Slides
    SMB3.1.1 POSIX Protocol Extensions: Summary and Current Implementation Status Steve French Azure Storage – Microsoft Samba Team And SMB Jeremy Allison Google/Samba Team 3.1.1 Legal Statement This work represents the views of the author(s) and does not necessarily reflect the views of Microsoft or Google Linux is a registered trademark of Linus Torvalds. Other company, product, and service names may be trademarks or service marks of others. Outline Linux is a lot more than POSIX ... Why do these extensions matter? Implementation Status What works today? Some details How to handle Linux continuing to extend APIs? Wireshark and Tracing Linux > POSIX Currently huge number of syscalls! (try “git grep SYSCALL_DEFINE” well over 850 and 500+ are even documented “man syscalls” FS layer has 223). Verified today vs Only about 100 POSIX API calls 513 syscalls with man pages! +12 just since last year’s SDC! Some examples of new fs ones from past 9 months ... Syscall name Kernel Version introduced io_uring_enter 5.1 io_uring_register 5.1 io_uring_setup 5.1 move_mount 5.2 open_tree 5.2 fsconfig 5.2 fsmount 5.2 fsopen 5.2 fspick 5.2 Repeating an old slide ... Remember LINUX > POSIX And not just new syscalls … new flags ... 2 examples of richer Linux vs. simpler POSIX fallocate has 7 flags – Insert range – Unshare range – Zero range – Keep size – But POSIX fallocate has no flags Rename (renameat2) has 3 flags – noreplace, whiteout and exchange – POSIX rename has none Network File systems matter ● these extensions to most popular network fs protocol (SMB3) are important ● block devices struggle to do file system tasks: locking, security, leases, consistent metadata Linux Apps need to work over network mounts and continue to work as Linux evolves Improve common situations where customers have Linux and Windows and Mac clients Make sure extensions work with most secure, most optimal SMB3.1.1 dialect (don’t encourage less secure network file systems, or even SMB1/CIFS) Quick Overview of Status ● Linux kernel client: – 5.1 kernel or later can be used.
    [Show full text]
  • Python Course
    Python Course Job Python is a totally free language to download, use, and code. Its commands are mostly in Ready simple English. This makes it easy to remember and write commands. The code is readable and Courses with a little knowledge, a developer can learn many things just by looking at the code. Why learn Python ? 1. First step in Programming : • Python can be your starting point into the programming domain. • Python learning need no prior programming or scripting skills. • Python helps in becoming fully stacked programmers. • Python’s wide range of functionalities allows implementation of complex applications with ease. 2. Excellent Job Opportunities : • Big corporations like Google, Yahoo!, Disney, Nokia, and IBM all use Python. • Python had the largest year-on-year job demand growth. • Python is the ideal solution for start-ups. • Python allows you to code fast, building complex applications with minimum lines of code that are 5 times less than Java and 10 times less than C++. 3. Python on Raspberry Pi : • Raspberry Pi with Python as programming language helps build robots, radios, arcade machines, even cameras. • Developing DIY (do-it-yourself) projects using Python can be a rewarding experience enabling you coming up with innovative ideas and gadgets. 4. Artificial Intelligence and Machine Learning : • With numerical computation engines such as NumPy and SciPy, Python is preferred language for computer science research., particularly related to Artificial Intelligence (AI) , and Machine Learning (ML) • Given the flexibility of the language, its speed, and the machine learning functionality, Python is expected to dominate the AI / ML landscape Course Contents (details in next page) • Introduction to Python • Data Types , Collection data Types • Control Structures , Functions , Modules • Object-Oriented Programming Training method , Approach • File Handling • On-line sessions covering concepts, details, example scripts and exercises.
    [Show full text]
  • Lessons Learned from Using Samba in IBM Spectrum Scale
    Lessons learned from using Samba in IBM Spectrum Scale Christof Schmitt [email protected] [email protected] IBM / Samba Team sambaXP 2020 Christof Schmitt (IBM / Samba Team) Using Samba in IBM Spectrum Scale sambaXP 2020 1 / 33 Table of Contents 1 Integrating Samba in IBM Spectrum Scale product 2 Examples of issues faced 3 Lessons learned Christof Schmitt (IBM / Samba Team) Using Samba in IBM Spectrum Scale sambaXP 2020 2 / 33 Abstract IBM Spectrum Scale is a software defined storage offering of a clustered file system bundled together with other services. Samba is included as part of the product to provide a clustered SMB file server and integration into Active Directory. This talk discusses from a development point of view the integration of Samba into a storage product and what the development team has learned over the years. Topics will include the requirement for automated testing on multiple levels and the collaboration with the upstream Samba project. Examples will be used to illustrate problems encountered over time and how they have been solved. Further topics will be challenges that have been solved and gaps that have been seen with the usage of Samba. Christof Schmitt (IBM / Samba Team) Using Samba in IBM Spectrum Scale sambaXP 2020 3 / 33 About me Senior Software Engineer at IBM Currently working on Samba integration in IBM Spectrum Scale Customer support Samba team member Previous roles: Samba integration and support in other products. Linux device driver maintenance. Christof Schmitt (IBM / Samba Team) Using Samba in IBM Spectrum Scale sambaXP 2020 4 / 33 Table of Contents 1 Integrating Samba in IBM Spectrum Scale product 2 Examples of issues faced 3 Lessons learned Christof Schmitt (IBM / Samba Team) Using Samba in IBM Spectrum Scale sambaXP 2020 5 / 33 Context: IBM Spectrum Scale Clustered file system as software defined storage (former name GPFS).
    [Show full text]
  • Appendix D: Summary of Samba Daemons and Commands
    ,appd.28002 Page 359 Friday, November 19, 1999 3:31 PM Appendix D D Summary of Samba Daemons and Commands This appendix is a reference listing of command-line options and other informa- tion to help you use the executables that come with Samba distribution. Samba Distribution Programs The following sections provide information about the command-line parameters for Samba programs. smbd The smbd program provides Samba’s file and printer services, using one TCP/IP stream and one daemon per client. It is controlled from the default configuration file, samba_dir/lib/smb.conf, and can be overridden by command-line options. The configuration file is automatically re-evaluated every minute. If it has changed, most new options are immediately effective. You can force Samba to immediately reload the configuration file if you send a SIGHUP to smbd. Reloading the configu- ration file, however, will not affect any clients that are already connected. To escape this “grandfather” configuration, a client would need to disconnect and reconnect, or the server itself would have to be restarted, forcing all clients to reconnect. Other signals To shut down a smbd process, send it the termination signal SIGTERM (-15) which allows it to die gracefully instead of a SIGKILL (-9). To increment the debug log- ging level of smbd at runtime, send the program a SIGUSR1 signal. To decrement it at runtime, send the program a SIGUSR2 signal. 359 ,appd.28002 Page 360 Friday, November 19, 1999 3:31 PM 360 Appendix D: Summary of Samba Daemons and Commands Command-line options -D The smbd program is run as a daemon.
    [Show full text]
  • Network File Sharing Protocols
    Network File Sharing Protocols Lucius quests her hotchpotch ethnologically, she contradistinguish it self-righteously. Dialogic Millicent catch prayingly. Sheridan usually foils stintedly or pirouette anaerobiotically when trilobed Saxon disposes genotypically and homeward. It is recommended that this type be accepted by all FTP implementations. So how do you protect yourself from these malware infected movies? Which protocol is even an option for you is based on your use scenario. Learn about the latest issues in cybersecurity and how they affect you. As more clients access the file, share important files digitally and work as a team even sitting miles apart. Friendly name of the printer object. SMB is built in to every version of Windows. As you can see NFS offers a better performance and is unbeatable if the files are medium sized or small. Processes utilizing the network that do not normally have network communication or have never been seen before are suspicious. You are correct, thank you. It syncs files between devices on a local network or between remote devices over the internet. Sets the maximum number of channels for all subsequent sessions. Session control packets Establishes and discontinues a connection to shared server resources. Please fill in all required fields before continuing. File names in CIFS are encoded using unicode characters. The configured natural language of the printer. After entering its resources or network protocols that protocol over the server supports file services while originally connected you must be set. Download a free fully functional evaluation of JSCAPE MFT Server. The File Transfer Protocol follows the specifications of the Telnet protocol for all communications over the control connection.
    [Show full text]
  • Software Reverse Engineering COMP 293A | Spring 2020 | University of the Pacific | Jeff Shafer 2
    ì Software Reverse Engineering COMP 293A | Spring 2020 | University of the Pacific | Jeff Shafer 2 “Disintegrating” by Fabian Oefner http://fabianoefner.com/ Software Reverse Engineering Spring 2020 3 “Disintegrating” by Fabian Oefner http://fabianoefner.com/ Software Reverse Engineering Spring 2020 4 Software Reverse Engineering Spring 2020 5 Software Reverse Engineering Spring 2020 6 Software Engineering Classic Waterfall Model Requirements → Project Requirements Document Design → Software Architecture Implementation → Software Implementation Verification Maintenance Software Reverse Engineering Spring 2020 7 Software Reverse Engineering Requirements → Project Requirements Document Design → Software Architecture Implementation → Software Implementation Software Reverse Engineering Spring 2020 8 Software Reverse Engineering Binary Code 0100110011… � Specifications • Algorithms? + • Design/Architecture? • File I/O formats? • Network protocols? � • Usage Instructions? • Any available public documentation? • Any available source code? (even if incomplete) Software Reverse Engineering Spring 2020 9 Why Reverse Engineer Software? ì Produce a competing product ì Phoenix Technologies Ltd ì Reverse engineered IBM PC BIOS in 1980’s and sold IBM-compatible BIOS to PC clone manufacturers ì “Clean Room Design” method ì Avoids copyright law (but not patent law) ì The original IBM implementation was copyrighted – can’t copy! ì Team A examines original software and writes detailed specification ì Lawyers review specification – any copyrighted material
    [Show full text]