Sign in

username:

password:



Not a member?

Search basicx



Search tips

Subscribe to basicx



basicx by Keywords

Accelerometer | ADC | ADXL | Adxl20 | AVR | BasicStamp | BX-35 | BX28 | BX35 | COM3 | Compiler | Downloader | EEPROM | Electromagnet | GetADC | GP2D1 | GPS | I2C | IDE | Keypad | LCD | LCD+ | MIDI | Motors | Multitasking | Netmedia | Networking | PCB | PID | PlaySound | PWM | Relays | RTC | Servo | ShiftOut | SitePlayer | SPI | Stack | Timer | USB

Ads

Discussion Groups

Discussion Groups | BasicX | SitePlayer Security

Discussion forum for the BasicX family of microcontroller chips.

SitePlayer Security - Jack Schoof - Sep 16 11:42:00 2000

> SitePlayer
> 1) Is about 1/2 the price (Tini $50/ SitePlayer $29.95 in 100 pieces)
> 2) Is a third to a quarter the size of a TINI
> 3) Requires no programming at all to make a web server.
> 4) Requires no Java Knowledge, although you can use Java Applets
> 5) Serves web pages about 5 to 10 times faster.
> 6) Programs from the BX24 or any processor trivially
> 7) Their socket is $0.50 to $1.00, ours is $0.05
> 8) We can be easily prototyped in 0.1 perf board - Tini not

Is there any provision for security? I'm not really interested
in having the stuff wide open to the world and if I need to put
it behind a firewall for security, well I can do with the just
the firewall+bx24 everything that I can do with the SP+bx24.

----

Yes there are three ways to accomplish security in SitePlayer

1) sub directories within siteplayer can be password protected, so you can choose which pages are surfable by everyone, and which are not. This will generate the browser request for a password.

2) setting variables within siteplayer can be done with a password that you supply on a form. Your device would then decide through its own password system, whether to use the variables or not.

3) to be super secure, you can output a special sequence of characters generated by the device, and the person at the browser needs to type back in those characters in a particular order. Like every 3 characters, or the first followed by the 5th etc. This way the password is constantly changing. Once the password is received, the device decodes it and does the same as 2) above.

In addition, you can choose the port that SitePlayer uses for HTTP, so instead of the standard port 80, you can do it on any of the 65535 ports. This gives some measure of security, because someone would have to find it first.

Jack
[Non-text portions of this message have been removed]




(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )