News:

RAID is not a replacement for a backup! Here's why.

Main Menu

Hidden shares

Started by nivenj, November 22, 2008, 05:55:55 PM

Previous topic - Next topic

nivenj

   

Hi, Linkstation Pro Duo FW 1.08

 

Is it possible to create a hidden share, such that its hidden from net view?

 

I notice that the default "info" folder has a "visible" option and enable and disabling this has the effect I want, but this option is not available in shares that I create. Any suggestions?

Message Edited by nivenj on 11-22-2008 06:36 PM

Paul

At this time buffalos firmware does not offer a hidden share.  Please visit buffalotech.com for future firmware updates.

nivenj

   

Thanks Paul, I actually managed to solve this myself. I must admit I am amazed that this issue isnt that the functionality does not exist, but the fact that Buffalo have actively written the code as to not allow it. I managed to find the offending lines and comment them out from the perl module. I did post a howto but this has been removed for some reason.

 

If anyone wants to know how to do this, PM me and I will give you the details.

 


frank_cheese

   

 I would very much like to know how to do this,anyone have any ideas asi notice the user that worked it out has not been online for a while...


davo

   

frank_cheese wrote:

 I would very much like to know how to do this,anyone have any ideas asi notice the user that worked it out has not been online for a while...


Altering the firmware in this manner is not allowed on this forum. So you will have to use good ol google if you require the info.

PM me for TFTP / Boot Images / Recovery files  LSRecovery.exe file.
Having network issues? Drop me an email: info@interwebsireland.com and we will get it fixed!

Have i helped you? Buy me a coffee as a thanks!
https://buymeacoffee.com/buffalodavo

nivenj

   

Hi Frank,

 

Unfortuneatly...(well actually it turns out fortuneatly)...I dont have nor use Buffalo NAS devices anymore so I cant remember what perl script I had to change but in a nutshell the guys at Buffalo, in their infinite wisdom, decided to identify the $ symbol as an invalid character when checking the share name a user types thats why it doesnt work and thats the bit I had to fix..Very simple if you understand perl. Why they removed, what is basic CIFS functionality, is beyond me..but they did.

 

Thankfully  I had a power issue on the Duo I had and Buffalo refused to cover it under warranty unless I also returned the disks which I couldnt do as I had commercial-in-confidence data stored on the device so I ended up having to go for a different NAS provider. Best move I ever made, I always thought the Buffalo system was very slow for data transfer, moving to another provider gave 4x the transfer speed and hidden shares work a charm. In answer to your question I would say, forget about trying to fix the code and just opt for another providers NAS device, there are many good ones out there who understand that product quality doesnt start and end with the hardware alone.


lefthooked

   

Why would this "basic" option not be accessable?  Is/was there an actual valid reason for this function being "disabled"?


nivenj

   

I asked Tech Support and recieved silence in return. It really looked to me like the people who wrote that part of the code did not realise that the $ symbol was used in CIFS to denote a hidden share as it was included in  a list of special characters that you wouldnt want to have in a path name "/ \ ." etc.


frank_cheese

   

ok then, then, thanks anyway guys.



Browser ID: smf (is_webkit)
Templates: 4: index (default), Display (default), GenericControls (default), GenericControls (default).
Sub templates: 6: init, html_above, body_above, main, body_below, html_below.
Language files: 5: index+Modifications.english (default), Post.english (default), Editor.english (default), Drafts.english (default), StopForumSpam.english (default).
Style sheets: 4: index.css, attachments.css, jquery.sceditor.css, responsive.css.
Hooks called: 292 (show)
Files included: 35 - 1354KB. (show)
Memory used: 1076KB.
Tokens: post-login.
Queries used: 16.

[Show Queries]