| /freebsd/sys/netsmb/ |
| H A D | smb_crypt.c | diff 8d96e455313f137de3023d7c893b4b24975c47bb Sun Mar 05 23:52:17 CET 2006 Yaroslav Tykhiy <ytykhiy@gmail.com> Retire NETSMBCRYPTO as a kernel option and make its functionality
enabled by default in NETSMB and smbfs.ko.
With the most of modern SMB providers requiring encryption by
default, there is little sense left in keeping the crypto part
of NETSMB optional at the build time.
This will also return smbfs.ko to its former properties users
are rather accustomed to.
Discussed with: freebsd-stable, re (scottl)
Not objected by: bp, tjr (silence)
MFC after: 5 days
diff 8d96e455313f137de3023d7c893b4b24975c47bb Sun Mar 05 23:52:17 CET 2006 Yaroslav Tykhiy <ytykhiy@gmail.com> Retire NETSMBCRYPTO as a kernel option and make its functionality
enabled by default in NETSMB and smbfs.ko.
With the most of modern SMB providers requiring encryption by
default, there is little sense left in keeping the crypto part
of NETSMB optional at the build time.
This will also return smbfs.ko to its former properties users
are rather accustomed to.
Discussed with: freebsd-stable, re (scottl)
Not objected by: bp, tjr (silence)
MFC after: 5 days
|
| H A D | smb_smb.c | diff 8d96e455313f137de3023d7c893b4b24975c47bb Sun Mar 05 23:52:17 CET 2006 Yaroslav Tykhiy <ytykhiy@gmail.com> Retire NETSMBCRYPTO as a kernel option and make its functionality
enabled by default in NETSMB and smbfs.ko.
With the most of modern SMB providers requiring encryption by
default, there is little sense left in keeping the crypto part
of NETSMB optional at the build time.
This will also return smbfs.ko to its former properties users
are rather accustomed to.
Discussed with: freebsd-stable, re (scottl)
Not objected by: bp, tjr (silence)
MFC after: 5 days
diff 8d96e455313f137de3023d7c893b4b24975c47bb Sun Mar 05 23:52:17 CET 2006 Yaroslav Tykhiy <ytykhiy@gmail.com> Retire NETSMBCRYPTO as a kernel option and make its functionality
enabled by default in NETSMB and smbfs.ko.
With the most of modern SMB providers requiring encryption by
default, there is little sense left in keeping the crypto part
of NETSMB optional at the build time.
This will also return smbfs.ko to its former properties users
are rather accustomed to.
Discussed with: freebsd-stable, re (scottl)
Not objected by: bp, tjr (silence)
MFC after: 5 days
|
| /freebsd/sys/modules/smbfs/ |
| H A D | Makefile | diff 8d96e455313f137de3023d7c893b4b24975c47bb Sun Mar 05 23:52:17 CET 2006 Yaroslav Tykhiy <ytykhiy@gmail.com> Retire NETSMBCRYPTO as a kernel option and make its functionality
enabled by default in NETSMB and smbfs.ko.
With the most of modern SMB providers requiring encryption by
default, there is little sense left in keeping the crypto part
of NETSMB optional at the build time.
This will also return smbfs.ko to its former properties users
are rather accustomed to.
Discussed with: freebsd-stable, re (scottl)
Not objected by: bp, tjr (silence)
MFC after: 5 days
diff 8d96e455313f137de3023d7c893b4b24975c47bb Sun Mar 05 23:52:17 CET 2006 Yaroslav Tykhiy <ytykhiy@gmail.com> Retire NETSMBCRYPTO as a kernel option and make its functionality
enabled by default in NETSMB and smbfs.ko.
With the most of modern SMB providers requiring encryption by
default, there is little sense left in keeping the crypto part
of NETSMB optional at the build time.
This will also return smbfs.ko to its former properties users
are rather accustomed to.
Discussed with: freebsd-stable, re (scottl)
Not objected by: bp, tjr (silence)
MFC after: 5 days
|
| /freebsd/sys/conf/ |
| H A D | files.powerpc | diff 8d96e455313f137de3023d7c893b4b24975c47bb Sun Mar 05 23:52:17 CET 2006 Yaroslav Tykhiy <ytykhiy@gmail.com> Retire NETSMBCRYPTO as a kernel option and make its functionality
enabled by default in NETSMB and smbfs.ko.
With the most of modern SMB providers requiring encryption by
default, there is little sense left in keeping the crypto part
of NETSMB optional at the build time.
This will also return smbfs.ko to its former properties users
are rather accustomed to.
Discussed with: freebsd-stable, re (scottl)
Not objected by: bp, tjr (silence)
MFC after: 5 days
diff 8d96e455313f137de3023d7c893b4b24975c47bb Sun Mar 05 23:52:17 CET 2006 Yaroslav Tykhiy <ytykhiy@gmail.com> Retire NETSMBCRYPTO as a kernel option and make its functionality
enabled by default in NETSMB and smbfs.ko.
With the most of modern SMB providers requiring encryption by
default, there is little sense left in keeping the crypto part
of NETSMB optional at the build time.
This will also return smbfs.ko to its former properties users
are rather accustomed to.
Discussed with: freebsd-stable, re (scottl)
Not objected by: bp, tjr (silence)
MFC after: 5 days
|
| H A D | files.amd64 | diff 8d96e455313f137de3023d7c893b4b24975c47bb Sun Mar 05 23:52:17 CET 2006 Yaroslav Tykhiy <ytykhiy@gmail.com> Retire NETSMBCRYPTO as a kernel option and make its functionality
enabled by default in NETSMB and smbfs.ko.
With the most of modern SMB providers requiring encryption by
default, there is little sense left in keeping the crypto part
of NETSMB optional at the build time.
This will also return smbfs.ko to its former properties users
are rather accustomed to.
Discussed with: freebsd-stable, re (scottl)
Not objected by: bp, tjr (silence)
MFC after: 5 days
diff 8d96e455313f137de3023d7c893b4b24975c47bb Sun Mar 05 23:52:17 CET 2006 Yaroslav Tykhiy <ytykhiy@gmail.com> Retire NETSMBCRYPTO as a kernel option and make its functionality
enabled by default in NETSMB and smbfs.ko.
With the most of modern SMB providers requiring encryption by
default, there is little sense left in keeping the crypto part
of NETSMB optional at the build time.
This will also return smbfs.ko to its former properties users
are rather accustomed to.
Discussed with: freebsd-stable, re (scottl)
Not objected by: bp, tjr (silence)
MFC after: 5 days
|
| H A D | files.i386 | diff 8d96e455313f137de3023d7c893b4b24975c47bb Sun Mar 05 23:52:17 CET 2006 Yaroslav Tykhiy <ytykhiy@gmail.com> Retire NETSMBCRYPTO as a kernel option and make its functionality
enabled by default in NETSMB and smbfs.ko.
With the most of modern SMB providers requiring encryption by
default, there is little sense left in keeping the crypto part
of NETSMB optional at the build time.
This will also return smbfs.ko to its former properties users
are rather accustomed to.
Discussed with: freebsd-stable, re (scottl)
Not objected by: bp, tjr (silence)
MFC after: 5 days
diff 8d96e455313f137de3023d7c893b4b24975c47bb Sun Mar 05 23:52:17 CET 2006 Yaroslav Tykhiy <ytykhiy@gmail.com> Retire NETSMBCRYPTO as a kernel option and make its functionality
enabled by default in NETSMB and smbfs.ko.
With the most of modern SMB providers requiring encryption by
default, there is little sense left in keeping the crypto part
of NETSMB optional at the build time.
This will also return smbfs.ko to its former properties users
are rather accustomed to.
Discussed with: freebsd-stable, re (scottl)
Not objected by: bp, tjr (silence)
MFC after: 5 days
|
| H A D | options | diff 8d96e455313f137de3023d7c893b4b24975c47bb Sun Mar 05 23:52:17 CET 2006 Yaroslav Tykhiy <ytykhiy@gmail.com> Retire NETSMBCRYPTO as a kernel option and make its functionality
enabled by default in NETSMB and smbfs.ko.
With the most of modern SMB providers requiring encryption by
default, there is little sense left in keeping the crypto part
of NETSMB optional at the build time.
This will also return smbfs.ko to its former properties users
are rather accustomed to.
Discussed with: freebsd-stable, re (scottl)
Not objected by: bp, tjr (silence)
MFC after: 5 days
diff 8d96e455313f137de3023d7c893b4b24975c47bb Sun Mar 05 23:52:17 CET 2006 Yaroslav Tykhiy <ytykhiy@gmail.com> Retire NETSMBCRYPTO as a kernel option and make its functionality
enabled by default in NETSMB and smbfs.ko.
With the most of modern SMB providers requiring encryption by
default, there is little sense left in keeping the crypto part
of NETSMB optional at the build time.
This will also return smbfs.ko to its former properties users
are rather accustomed to.
Discussed with: freebsd-stable, re (scottl)
Not objected by: bp, tjr (silence)
MFC after: 5 days
|
| H A D | NOTES | diff 8d96e455313f137de3023d7c893b4b24975c47bb Sun Mar 05 23:52:17 CET 2006 Yaroslav Tykhiy <ytykhiy@gmail.com> Retire NETSMBCRYPTO as a kernel option and make its functionality
enabled by default in NETSMB and smbfs.ko.
With the most of modern SMB providers requiring encryption by
default, there is little sense left in keeping the crypto part
of NETSMB optional at the build time.
This will also return smbfs.ko to its former properties users
are rather accustomed to.
Discussed with: freebsd-stable, re (scottl)
Not objected by: bp, tjr (silence)
MFC after: 5 days
diff 8d96e455313f137de3023d7c893b4b24975c47bb Sun Mar 05 23:52:17 CET 2006 Yaroslav Tykhiy <ytykhiy@gmail.com> Retire NETSMBCRYPTO as a kernel option and make its functionality
enabled by default in NETSMB and smbfs.ko.
With the most of modern SMB providers requiring encryption by
default, there is little sense left in keeping the crypto part
of NETSMB optional at the build time.
This will also return smbfs.ko to its former properties users
are rather accustomed to.
Discussed with: freebsd-stable, re (scottl)
Not objected by: bp, tjr (silence)
MFC after: 5 days
|
| H A D | files | diff 8d96e455313f137de3023d7c893b4b24975c47bb Sun Mar 05 23:52:17 CET 2006 Yaroslav Tykhiy <ytykhiy@gmail.com> Retire NETSMBCRYPTO as a kernel option and make its functionality
enabled by default in NETSMB and smbfs.ko.
With the most of modern SMB providers requiring encryption by
default, there is little sense left in keeping the crypto part
of NETSMB optional at the build time.
This will also return smbfs.ko to its former properties users
are rather accustomed to.
Discussed with: freebsd-stable, re (scottl)
Not objected by: bp, tjr (silence)
MFC after: 5 days
diff 8d96e455313f137de3023d7c893b4b24975c47bb Sun Mar 05 23:52:17 CET 2006 Yaroslav Tykhiy <ytykhiy@gmail.com> Retire NETSMBCRYPTO as a kernel option and make its functionality
enabled by default in NETSMB and smbfs.ko.
With the most of modern SMB providers requiring encryption by
default, there is little sense left in keeping the crypto part
of NETSMB optional at the build time.
This will also return smbfs.ko to its former properties users
are rather accustomed to.
Discussed with: freebsd-stable, re (scottl)
Not objected by: bp, tjr (silence)
MFC after: 5 days
|
| /freebsd/ |
| H A D | UPDATING | diff 8d96e455313f137de3023d7c893b4b24975c47bb Sun Mar 05 23:52:17 CET 2006 Yaroslav Tykhiy <ytykhiy@gmail.com> Retire NETSMBCRYPTO as a kernel option and make its functionality
enabled by default in NETSMB and smbfs.ko.
With the most of modern SMB providers requiring encryption by
default, there is little sense left in keeping the crypto part
of NETSMB optional at the build time.
This will also return smbfs.ko to its former properties users
are rather accustomed to.
Discussed with: freebsd-stable, re (scottl)
Not objected by: bp, tjr (silence)
MFC after: 5 days
diff 8d96e455313f137de3023d7c893b4b24975c47bb Sun Mar 05 23:52:17 CET 2006 Yaroslav Tykhiy <ytykhiy@gmail.com> Retire NETSMBCRYPTO as a kernel option and make its functionality
enabled by default in NETSMB and smbfs.ko.
With the most of modern SMB providers requiring encryption by
default, there is little sense left in keeping the crypto part
of NETSMB optional at the build time.
This will also return smbfs.ko to its former properties users
are rather accustomed to.
Discussed with: freebsd-stable, re (scottl)
Not objected by: bp, tjr (silence)
MFC after: 5 days
|